Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →kdlbs/fix
Diagnose a bug, update its behavioral spec, create reviewable fix plan and task files, then hand off for explicit implementation with TDD.
Passed 8 of 14 test cases with the skill, and 6 of 14 without it.
and 8 more in the full report
9 fixed5 passed either way4 still failing6 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
While fixing authorization bypass issue #509, we established a new durable security invariant and public contract boundary between services. Which slash command should be used to document this durable boundary rule?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies using /record to document the durable boundary rule. | Missed | Passed |
The instructions your model reads when the skill loads.
Use the same durable workflow as feature work. Diagnose the defect first. Then reconcile specifications and create the fix plan and work orders before you change production code.
Evidence -> Root cause -> Requirement conformance -> System-design check -> Fix plan + work orders -> Handoff -> Explicit implementation request -> TDD -> PR review
Do not patch production code before the planning checkpoint unless the user explicitly opts out.
When a bug comes from an issue tracker, read the canonical issue and each image attachment. Reproduce the behavior with existing tests, a read-only trace, or a minimal temporary reproduction.
State:
If the cause remains uncertain, stop and ask the user.
Run the /interview-me assumption check for intended behavior and repair scope.
Reuse active acceptance criteria for clear regressions. Ask only about material
choices that evidence and prior instructions do not settle.
Read docs/specs/README.md, the owning system index, and the relevant
requirement and system-design documents. Use the legacy catalog only when the
system has not migrated.
Read the owning system README.md and use this command for discovery:
test cases passed, vs 6 / 14 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.