Generate executable bug-fix plans with an Input Audit gate.
npx skills add https://github.com/denis-pingin/fixme --skill fixme-write-plan
Please help me install this Agent Skill. Skill: fixme-write-plan Source: https://github.com/denis-pingin/fixme/tree/main/.claude/skills/fixme-write-plan Command: npx skills add https://github.com/denis-pingin/fixme --skill fixme-write-plan
Write implementation plans that are unambiguous, complete, correct, and efficient. Plans are written for an engineer with zero codebase context. Guards against any source code modifications - only the plan document is produced. Reads the codebase thoroughly before writing. Runs a mandatory Input Audit gate before any planning work to surface ambiguities and locked decision conflicts. Supports four modes - fresh (full exploration), plan revision (incorporate plan review FIX items), code revision (incorporate code review FIX items after execution), and rewrite (improve existing plan without structured FIX items).
Provide a clear task description and constraints to generate a complete, executable plan.
High-intent search queries and answers about installing and using this skill.
To create a bug fix plan without modifying source code, provide a clear task description and constraints. The system reads the codebase thoroughly, runs an Input Audit gate to surface ambiguities, and generates a comprehensive, executable plan document for an engineer with zero context.
An Input Audit gate is a mandatory front-end check executed before any planning work begins. It surfaces ambiguities and locked decision conflicts in the task description, ensuring the final bug fix plan is unambiguous, complete, and correct before execution.
To update an implementation plan after a code review, use the Code Revision mode. This mode incorporates structured FIX items identified during execution and code review, ensuring traceability and maintaining a single, authoritative decision log.
Yes, you can generate a multi-phased bug fix plan for complex tasks. The system supports fresh exploration mode to handle tasks ranging from single-ticket fixes to multi-phased sessions, producing a complete plan written for an engineer with zero codebase context.
The best way to improve an existing bug fix plan without structured FIX items is to use the Rewrite mode. This mode enhances the existing plan document directly, ensuring it remains unambiguous, complete, and efficient without requiring a formal review cycle.
Yes, the planning workflow enforces traceability by satisfying requirements for explicit task descriptions, plan revisions, code revisions, and a single authoritative decision log. This ensures all changes and decisions are tracked throughout the bug fix lifecycle.
meta-pytorchParse GitHub issues into goals, acceptance criteria, and constraints.
pipecrew-aiApply fix recipes to modify code in memory across affected repositories.
martinemdeCreate pull requests from code revisions using gh CLI and jj.
hainamchungExecute coding tasks immediately by bypassing the planning phase.
