pair-programming
/pair-programming
Prowadzi programowanie w parach z AI w trybach driver, navigator i switch, z weryfikacją na bieżąco, monitorowaniem jakości i testami, w tym TDD, debugowanie, refaktoryzacja i sesje nauki.
- Autor
- frankxai ↗
- Repozytorium
- claude-skills-library ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 26.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 3
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 26.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Prowadzi programowanie w parach z AI w trybach driver, navigator i switch, z weryfikacją na bieżąco, monitorowaniem jakości i testami, w tym TDD, debugowanie, refaktoryzacja i sesje nauki.
Oryginalny opis (EN)
AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with truth-score verification. Use when pairing on code with driver/navigator roles, doing TDD, or wanting real-time review while building.
Jak działa
- What This Skill Does
- Prerequisites
- Quick Start
- Reference
- Operations reference
Podgląd SKILL.md
---
name: pair-programming
description: AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with truth-score verification. Use when pairing on code with driver/navigator roles, doing TDD, or wanting real-time review while building.
---
# Pair Programming
Collaborative AI pair programming with intelligent role management, real-time quality monitoring, and comprehensive development workflows.
## What This Skill Does
This skill provides professional pair programming capabilities with AI assistance, supporting multiple collaboration modes, continuous verification, and integrated testing. It manages driver/navigator roles, performs real-time code review, tracks quality metrics, and ensures high standards through truth-score verification.
**Key Capabilities:**
- **Multiple Modes**: Driver, Navigator, Switch, TDD, Review, Mentor, Debug
- **Real-Time Verification**: Automatic quality scoring with rollback on failures
- **Role Management**: Seamless switching between driver/navigator roles
- **Testing Integration**: Auto-generate tests, track coverage, continuous testing
- **Code Review**: Security scanning, performance analysis, best practice enforcement
- **Session Persistence**: Auto-save, recovery, export, and sharing
## Prerequisites
**Required:**
- Claude Flow CLI installed (`npm install -g claude-flow@alpha`)
- Git repository (optional but recommended)
**Recommended:**
- Testing framework (Jest, pytest, etc.)
- Linter configured (ESLint, pylint, etc.)
- Code formatter (Prettier, Black, etc.)
## Quick Start
### Basic Session
```bash
# Start simple pair programming
claude-flow pair --start
```
### TDD Session
```bash
# Test-driven development
claude-flow pair --start \
--mode tdd \
--test-first \
--coverage 90
```
---
## Reference
The full detail lives in `references/` and loads only when needed:
- [`references/usage.md`](references/usage.md) — session control, modes, in-session commands & configuration.
- [`references/examples.md`](references/examples.md) — real-world examples, templates, session management & advanced features.
---
## Operations reference
### Best Practices
#### Session Practices
1. **Clear Goals** - Define session objectives upfront
2. **Appropriate Mode** - Choose based on task type
3. **Enable Verification** - For critical code paths
4. **Regular Testing** - Maintain quality continuously
5. **Session Notes** - Document important decisions
6. **Regular Breaks** - Take breaks every 45-60 minutes
#### Code Practices
1. **Test Early** - Run tests after each change
2. **Verify Before Commit** - Check truth scores
3. **Review Security** - Always for sensitive code
4. **Profile Performance** - Use `/perf` for optimization
5. **Save Sessions** - For complex work
6. **Learn from AI** - Ask questions frequently
#### Mode Selection
- **Driver Mode**: When learning, controlling implementation
- **Navigator Mode**: For rapid prototyping, generation
- **Switch Mode**: Long sessions, balanced collaboration
- **TDD Mode**: Building with tests
- **Review Mode**: Quality focus
- **Mentor Mode**: Learning priority
- **Debug Mode**: Fixing issues
### Troubleshooting
#### Session Won't Start
- Check agent availability
- Verify configuration file syntax
- Ensure clean workspace
- Review log files
#### Session Disconnected
- Use `--recover` to restore
- Check network connection
- Verify background processes
- Review auto-save files
#### Poor Performance
- Reduce verification threshold
- Disable continuous testing
- Check system resources
- Use lighter AI model
#### Configuration Issues
- Validate JSON syntax
- Check file permissions
- Review priority order (CLI > env > project > user > global)
- Run `claude-flow pair config validate`
### Quality Metrics
#### Truth Score Thresholds
```
Error: < 0.90 ❌
Warning: 0.90 - 0.95 ⚠️
Good: 0.95 - 0.98 ✅
Excellent: > 0.98 🌟
```
#### Coverage Thresholds
```
Error: < 70% ❌
Warning: 70% - 80% ⚠️
Good: 80% - 90% ✅
Excellent: > 90% 🌟
```
#### Complexity Thresholds
```
Error: > 15 ❌
Warning: 10 - 15 ⚠️
Good: 5 - 10 ✅
Excellent: < 5 🌟
```
### Environment Variables
Override configuration via environment:
```bash
export CLAUDE_PAIR_MODE=driver
export CLAUDE_PAIR_VERIFY=true
export CLAUDE_PAIR_THRESHOLD=0.98
export CLAUDE_PAIR_AGENT=senior-dev
export CLAUDE_PAIR_AUTO_TEST=true
```
### Command History
Navigate history:
- `↑/↓` - Navigate through command history
- `Ctrl+R` - Search command history
- `!!` - Repeat last command
- `!<n>` - Run command n from history
### Keyboard Shortcuts (Configurable)
Default shortcuts:
```json
{
"shortcuts": {
"switch": "ctrl+shift+s",
"suggest": "ctrl+space",
"review": "ctrl+r",
"test": "ctrl+t"
}
}
```
### Related Commands
- `claude-flow pair --help` - Show help
- `claude-flow pair config` - Manage configuration
- `claude-flow pair profile` - Manage profiles
- `claude-flow pair templates` - List templates
- `claude-flow pair agents` - List available agents
Pliki w paczce (3)
- SKILL.md 5 KB
- references/examples.md 9 KB
- references/usage.md 11 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · frankxai/claude-skills-library | 100 | MIT |
| flurdy/agent-skills | 95 | MIT |
| staruhub/claudeskills | 95 | MIT |
| ctoforaday/special-circumstances | 86 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 3f72c0375497 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90rseng-pair-programming
Wspiera programowanie w parze i przegląd pull requestów dla oprogramowania badawczego: współpracę driver-navigator, TDD ping-pong i wstępny przegląd zmian przed recenzją człowieka. - 100technical-mentoring-pair-programming-craft
Prowadzi młodszych inżynierów przez wspólne programowanie w parach i odkrywanie z przewodnikiem. - 100superpowers-zh
Prowadzi pracę AI nad kodem według metodyki: TDD, systematyczne debugowanie, przegląd kodu i weryfikację wyników. - 90programming
Wspiera programowanie i debugowanie: Bash, jakość Pythona i Jupytera, workflow pakietów Nix, Terraform z Checkov, Markdown, TDD z Tidy First i izolowanie przyczyny źródłowej. - 100build-with-quality
Implementuje funkcje z testami i bramkami jakości, debuguje trudne błędy i testuje projekty pod obciążeniem: TDD i EDD, uparte błędy w wielu funkcjach, przesłuchanie projektu przed kodowaniem i przegląd pokrycia, bezpieczeństwa oraz dostępności. - 96tdd-workflows-tdd-cycle
Prawdopodobnie pomaga przy cyklu TDD w przepływach pracy z testami, w tym przy pisaniu testów przed kodem.