Documents ad-hoc bug fixes as specs routed through the standard build loop.
npx skills add https://github.com/LeroyAdonis/kitfix-2.0 --skill fix-leroyadonis
Please help me install this Agent Skill. Skill: fix Source: https://github.com/LeroyAdonis/kitfix-2.0/tree/main/.agents/skills/fix Command: npx skills add https://github.com/LeroyAdonis/kitfix-2.0 --skill fix-leroyadonis
blueprint/context/current-feature.md covering the problem, the fix approach, build steps, and verification criteria. - Finding Ledger Integration: Accepts a finding ID from blueprint/context/findings.md (e.g., /fix F-03) so repairs are traceable and findings get marked fixed when the build lands. - Workflow Handoff: Stops after writing the spec so /implement builds it with review gates and /complete logs it to blueprint/history/fixes/ and merges. - Use Case: A user reports "password reset email never sends" mid-project. Run /fix to capture it as a spec, then let the existing implement/complete loop handle the build and merge without touching the build plan. ## Quick Start Ask the AI to run /fix with a description of the bug, such as "/fix password reset email never sends", then review the generated spec.High-intent search queries and answers about installing and using this skill.
Run /fix with a short description of the bug, such as "/fix password reset email never sends". The skill writes a lightweight fix spec to blueprint/context/current-feature.md, then you run /implement to build it and /complete to log and merge it.
Pass the finding ID to the fix command, for example /fix F-03, optionally with extra description. The skill pulls the problem statement from blueprint/context/findings.md and stamps the spec so the finding is marked fixed when the repair lands.
No. The fix skill overwrites current-feature.md, so use it only between work items when that file is the reset stub. While a spec is active, repair its findings through /implement instead.
Use /feature when the change is really new functionality that belongs in build-plan.md. The fix skill is only for bugs and small changes; it never adds items to the build plan and keeps specs lighter than feature specs.
Because the fix spec is marked with Type: Fix, the /complete step logs it to blueprint/history/fixes/ rather than blueprint/history/features/, keeping unplanned repairs traceable separately from planned work.
ulpi-ioRepair Rust crate review findings sequentially with regression tests and Clippy verification.
zts212653Process reviewer feedback through a structured repair workflow with verification gates.
ZaxbyHubResolve pull request feedback with verified source evidence and closure summaries.
mckissingerPlan small software changes into milestone specifications with verification methods.