debug
Investigation-first debugging — gather evidence, form confirmed root-cause hypothesis, hand off to fix mode with diagnosis file.…
Run a bounded adversarial convergence loop with independent challengers and a strict-decrease stop rule.
$ npx -y skills add Borda/AI-Rig --skill rig-challenge --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/rig-challengeContext preview
The summary Claude sees to decide when to auto-load this skill.
Run a bounded adversarial convergence loop with independent challengers and a strict-decrease stop rule.
name: Rig Challenge description: Run a bounded adversarial convergence loop with independent challengers and a strict-decrease stop rule.
> Read [Evidence rules](../../references/evidence.md) and [Convergence](../../references/convergence.md).
1. **Freeze the baseline.** Start a run with `rig_evidence` (`skill: "rig-challenge"`) and record the exact source and acceptance criteria. 2. **Round 1 — independent challenge.** Dispatch `rig-challenger` with the complete source and criteria. The challenger returns structured findings: invariant, counterexample, severity, and file reference. The parent does not challenge its own work. Ensure correctness is covered (the challenger must examine logic/control flow). 3. **Validate.** Check each finding against the source. Record a stable signature: file plus normalized invariant. Use `rig_loop` with `action: "start"` and `reviewer` naming the independent challenger; the baseline round's weighted total is `W0`. 4. **Fix.** Address validated findings only. One writer per path. Refresh the run scope with `rig_evidence` (`action: "refresh"`) after the last fix, then run configured gates. 5. **Re-assess.** A fresh challenger receives the prior findings, the complete required source, and the changed paths. It marks each signature `verified-fixed` or `rejected` and may report new signatures. 6. **Score and decide.** Append the round with `rig_loop` (`action: "append"`, `reviewer`, and every prior signature assessed). Compute the open weighted total using security 20, critical 10, high 6, medium 4, low 2, nit 1.
7. **Print progress.** After each validated round, print the cumulative table: `Iteration | Security | Critical | High | Medium | Low | Nits | Weighted score`, with every numeric cell as `old + new`. 8. **Finalize.** Record the terminal stop reason with `rig_loop` (`action: "finalize"`, `reviewer`, `stop_reason`, and a `note` for authority, drift, or unavailable-reviewer stops) and finalize the run. Security or critical residue blocks finalization; any stop other than convergence leaves the run blocked.
Report the run ID, weighted series, stop reason, unresolved signatures, gate receipts, and remaining risks.
Practical agent workflows for Python, ML, and open-source maintenance. AI-Rig turns recurring work—scoping a change, reproducing a bug, reviewing a pull request, running an experiment, or checking release readiness—into explicit workflows with specialist
Investigation-first debugging — gather evidence, form confirmed root-cause hypothesis, hand off to fix mode with diagnosis file.…
TDD-first feature development — crystallise API as a demo test, drive implementation to pass it, run quality stack and…
Reproduce-first bug resolution — capture bug in failing regression test, apply minimal fix, run quality stack and review loop.…
Analysis-only planning — classify and scope a task without writing code; outputs a structured plan to .plans/active/. TRIGGER…
Test-first refactoring — audit coverage, add characterization tests, apply changes with safety net, run quality stack and review…
Multi-agent code review of local Python files, directories, or the current git diff covering architecture, tests, performance,…