HeisenbergI8
UserMechanical evidence and gates for Claude Code — blocks false-green test claims, escalates on stuck failures, enforces agent role separation.
Categories
Indexed Skills (16)
build
Start or steer a supervised task-loop run. Use when the user types /build, or asks to work through a plan autonomously and have the loop keep going until it is done or a cap is hit.
debug-ladder
Escape a repeated-failure loop. Load when the same test, typecheck, build, or runtime error has survived two or more fix attempts, or when you notice you are trying variations of a solution that already failed. Enforces an attempt budget, a written ledger, and escalation to the user.
git-committer
Write and create commits matching this project's established convention. Use when the user asks to commit, or when a unit of work is finished and ready to record.
implement-plan
Execute an architect plan phase by phase with verification gates. Use when implementing a plan from .claude/plans/, or when the user says "implement the plan", "build this", or "go ahead" after a plan exists. Also use for any multi-file change large enough to need ordered phases, even without a formal plan.
lean-code
Discipline for writing the minimum code that solves the problem — search for what already exists before adding anything, and resist premature abstraction. Load BEFORE writing a new file, helper, type, component, or utility, and whenever the task smells like it will produce a lot of code.
lesson-keeper
Record, consolidate, and prune the hard-won lessons in .claude/lessons/. Use when a non-obvious failure has just been resolved, when the lessons audit reports warnings, or when asked what has been learned in this project.
lessons-review
Work through the captured candidate backlog and decide which incidents become lessons, which get encoded as guards, and which are discarded. Use when the harness reports a candidate review is due, or when asked to review what has been learned.
ticket-writer
Draft a well-formed issue or ticket — title and description — ready to paste into your tracker. Use when the user asks to write a ticket, file a bug, create a story, or turn a finding into something trackable.
build
Start or steer a supervised task-loop run. Use when the user types /build, or asks to work through a plan autonomously and have the loop keep going until it is done or a cap is hit.
debug-ladder
Escape a repeated-failure loop. Load when the same test, typecheck, build, or runtime error has survived two or more fix attempts, or when you notice you are trying variations of a solution that already failed. Enforces an attempt budget, a written ledger, and escalation to the user.
git-committer
Write and create commits matching this project's established convention. Use when the user asks to commit, or when a unit of work is finished and ready to record.
implement-plan
Execute an architect plan phase by phase with verification gates. Use when implementing a plan from .claude/plans/, or when the user says "implement the plan", "build this", or "go ahead" after a plan exists. Also use for any multi-file change large enough to need ordered phases, even without a formal plan.
lean-code
Discipline for writing the minimum code that solves the problem — search for what already exists before adding anything, and resist premature abstraction. Load BEFORE writing a new file, helper, type, component, or utility, and whenever the task smells like it will produce a lot of code.
lesson-keeper
Record, consolidate, and prune the hard-won lessons in .claude/lessons/. Use when a non-obvious failure has just been resolved, when the lessons audit reports warnings, or when asked what has been learned in this project.
lessons-review
Work through the captured candidate backlog and decide which incidents become lessons, which get encoded as guards, and which are discarded. Use when the harness reports a candidate review is due, or when asked to review what has been learned.
ticket-writer
Draft a well-formed issue or ticket — title and description — ready to paste into your tracker. Use when the user asks to write a ticket, file a bug, create a story, or turn a finding into something trackable.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.