tdd-bugfix

Étoiles11

Forks0

Mis à jour29 mai 2026 à 18:59

Reproduce → root-cause → failing test → minimal fix → verify. Trigger: 'fix this bug', 'reproduce and fix', 'TDD fix'. Requires a local test path.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

aryaminus

aryaminus/controlkeel

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

name	tdd-bugfix
description	Reproduce → root-cause → failing test → minimal fix → verify. Trigger: 'fix this bug', 'reproduce and fix', 'TDD fix'. Requires a local test path.
when_to_use	Activate when fixing a bug WITH a cheap local test path. Do NOT use for design tasks, features, or bugs requiring manual browser reproduction.
argument-hint	[bug description or failing test path]
disable-model-invocation	true
license	Apache-2.0
compatibility	["opencode-native","claude-standalone","cursor-native","codex"]
metadata	{"author":"controlkeel","version":"1.1","category":"development","ck_mcp_tools":["ck_validate","ck_finding","ck_git_diff","ck_git_commit","ck_memory_record"],"related_skills":["deep-code-quality-review"]}

TDD Bugfix

Test-first bug fix. Failing test proves the bug, fix makes it pass, runtime evidence confirms.

Do NOT use when

No local test path exists (manual browser testing, production-only bugs)
Building features (use architect-first then plan-slice)
Refactoring (use deep-code-quality-review)

Workflow

Reproduce: Trace the code path to the defect. Write a minimal test that fails. Run it to confirm failure.
Root-cause: Follow root-cause checklist. Record root cause via ck_memory_record (type: finding).
Failing test: Write a test that demonstrates the bug. Must be: minimal, deterministic, clearly named. Confirm it fails.
Validate test: Run ck_validate on the test code. Fix findings.
Minimal fix: Smallest change to make the test pass. No refactoring, no improvements. Record improvement ideas via ck_memory_record for later.
Verify: Failing test passes. Full suite passes (mix test). Zero new failures.
Validate fix: Run ck_validate on the diff. Record findings.
Commit: ck_git_commit with message referencing the bug and test.

Rules

Test first, fix second — no exceptions
Minimal fix only — refactoring is a separate commit
No Process.sleep/1 in tests — use monitors or :sys.get_state/1
Root-cause, not symptom — fix the cause or record deeper issue as ck_finding

Output

Failing test proving the bug
Minimal fix making test pass
Full suite passing
Root cause recorded in memory

Plus depuis ce dépôt

même dépôt

bounded-loop

aryaminus/controlkeel

Run objective, repeatable improvement work under an immutable verifier and hard iteration, cost, time, and no-progress limits. Use for approved experiments with an automated metric and sandboxed worker.

2026-07-1711

communication-style

aryaminus/controlkeel

Write concise, calm technical responses whose structure matches the decision, evidence, or sequence being communicated. Use when drafting substantial plans, reviews, findings, documentation, or completion summaries.

2026-07-1711

controlkeel-governance

aryaminus/controlkeel

Operate inside a ControlKeel-governed session. Use this before code edits, shell execution, delegation, deploy work, or any task that needs CK validation, findings, budget, proof, or routing context.

2026-07-1711

cost-optimization

aryaminus/controlkeel

Keep a governed session within budget. Use this before long-running agent work, bulk processing, or any task where spend pressure could change the plan.

2026-07-1711

end-of-shift

aryaminus/controlkeel

Close a governed work session with validation, proof, findings, budget, digest, learning, and handoff checks. Use when the user asks to wrap up, stop for the day, or leave work ready for another agent.

2026-07-1711

false-confidence-test-audit

aryaminus/controlkeel

Audit tests that may pass without proving the claimed behavior. Use for periodic test-quality reviews or when coverage looks healthy but regressions still escape.

2026-07-1711

TDD Bugfix

Test-first bug fix. Failing test proves the bug, fix makes it pass, runtime evidence confirms.

Do NOT use when

No local test path exists (manual browser testing, production-only bugs)

Building features (use architect-first then plan-slice)

Refactoring (use deep-code-quality-review)

Workflow

Reproduce: Trace the code path to the defect. Write a minimal test that fails. Run it to confirm failure.

Root-cause: Follow root-cause checklist. Record root cause via ck_memory_record (type: finding).

Failing test: Write a test that demonstrates the bug. Must be: minimal, deterministic, clearly named. Confirm it fails.

Validate test: Run ck_validate on the test code. Fix findings.

Minimal fix: Smallest change to make the test pass. No refactoring, no improvements. Record improvement ideas via ck_memory_record for later.

Verify: Failing test passes. Full suite passes (mix test). Zero new failures.

Validate fix: Run ck_validate on the diff. Record findings.

Commit: ck_git_commit with message referencing the bug and test.

Rules

Test first, fix second — no exceptions

Minimal fix only — refactoring is a separate commit

No Process.sleep/1 in tests — use monitors or :sys.get_state/1

Root-cause, not symptom — fix the cause or record deeper issue as ck_finding

Output

Failing test proving the bug

Minimal fix making test pass

Full suite passing

Root cause recorded in memory