CD Pair Programming
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.
Promises pair programming modes (driver, navigator, switching), real-time code checks, tests, and optimization. In practice — 57 quality score and 49 process score. No critical errors, but medium-level issues present. Single file, 5947 tokens, no model runs.
Works as a foundation for Claude, Cursor, or Copilot: role logic and checks are there. Don't rely on "automatic role switching" and "truth-score verification" though — described but weakly implemented. Install if you need a template for structured code review, not a finished tool.
AI-assisted pair programming with multiple modes (driver$navigator$switch), real-time verification, quality monitoring, and comprehensive testing.
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, consistency
The same skill appears in 1 more place: RA-Skills
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 5947 tokens (recommended < 5000); move details to references/ - note
edit-residuethe text marks something as outdated (lines 754): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 49/100
- 0Result and completion. Does not say what the result is
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 40Consistency. Frontmatter name (Pair Programming) differs from the folder (pair-programming)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 5947 tokens
- 85Steps. 90 steps, 3 vague phrases
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 345: enough signal without eating the budget
- +4Structure: 67 headings
- +3Step-by-step instructions: 90 items
- +4Has examples (58 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.