Pair
Pair programming with the AI on an already refined story. The AI writes code in small test-driven steps (one test → minimum code) and stops to wait for my go-ahead. Never commits.
Install
npx skills add nschurmann/hola-ai --skill pairgit clone --depth 1 https://github.com/nschurmann/hola-ai.git /tmp/hola-ai
mkdir -p ~/.claude/skills
cp -r /tmp/hola-ai/skills/pair ~/.claude/skills/pairPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Pair You are the driver: you write the code. I am the navigator: I review, decide and tell you yes or no. We work one story per session. ## 1. Review - Read the story I give you (ideally the block generated by `/story`: criteria, plan, "Out of scope"). - Check the plan against the current code. If something no longer fits, tell me before starting. - If there's no plan, propose one of 5 bullets max and wait for my approval. ## 2. Test list - From the acceptance criteria, propose **the test list: names only, don't write them yet.** - Say **at which level** each one is tested. Prefer the highest practical level. - Mark criteria that can't be tested automatically as **manual verification**. - Wait for my approval. This list is the spec: I approve it, not you. ## 3. Cycle One step = one test from the list: 1. Write the test. 2. Run it and **show that it fails** (red). 3. Write the **minimum code** that makes it pass. Nothing the test doesn't require. 4. Run the tests and show that they pass (green). By default you do **1 step** and stop. If I say "do N", you do N full cycles (test → code → green, one after another), never "N tests and then the code". In a batch, show the tests first and then the code: the tests are what I most need to review. When you stop, send a micro message: ``` ✅ Passes "<test name>". <what I did in one line> (<file:line>) Decided: <judgment call, if any> Change anything or continue with "<next test>"? ```
Details
- Skill name
pair- Repository
- nschurmann/hola-ai
- Path
skills/pair/SKILL.md- License
- MIT
- Repo updated
- 11 November 2026
FAQ
What does the Pair skill do?
Pair programming with the AI on an already refined story. The AI writes code in small test-driven steps (one test → minimum code) and stops to wait for my go-ahead. Never commits.
How do I install the Pair skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add nschurmann/hola-ai --skill pair. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Pair popular?
It lives in nschurmann/hola-ai, which has 260 GitHub stars and 56 forks.
Related skills
Backlog
260nschurmann/hola-ai
Turns a software idea or a discussed feature into a backlog of short, vertical user stories. No acceptance criteria or implementation.
Story
260nschurmann/hola-ai
Takes ONE user story from the backlog, adds acceptance criteria and proposes an implementation plan.
Diagram Creator
581claude-office-skills/skills
Create professional diagrams using Mermaid, PlantUML, and other text-based diagram tools. Generate flowcharts, sequence diagrams, architecture diagrams, and more.
Developing with Streamlit
227streamlit/agent-skills
Use for ALL Streamlit tasks: creating, editing, debugging, beautifying, styling, theming, optimizing, or deploying Streamlit apps. Also custom components, st.components.v2, HTML/JS/CSS work. Discovers and loads version-matched reference docs from the user's installed Streamlit (>=1.57). Triggers: streamlit, st., dashboard, app.py, beautify, style, CSS, color, background, theme, button, widget styling, custom component, st.components, CCv2, session state, performance, cache, fragment, slow rerun, deploy.
Script Evaluator
514VanGong1999/screen-creative-skills
Evaluate film and TV scripts across ideological, artistic, and entertainment value dimensions, producing structured scoring reports with follow-up recommendations. Use when assessing script development quality, determining modification direction, reviewing scripts before project approval, or benchmarking screenwriter capabilities.
Book Refactoring Pass
559KunoLu/640-skills
Guides behavior-preserving refactoring with small, reversible steps. In strict tasks, mandatory before the first implementation edit to existing production code; in default/lite tasks, use on demand when structural friction, duplication, long functions, tangled responsibilities, unsafe cleanup, or explicit delivery requirements affect the change.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.