fix-plan
Skill1 starsChanged 8 months agoMITView on GitHub
Analyzes errors from the test-lint quality gate and produces a targeted fix plan grouped by root cause. Operates in read-only mode until approved. Requires lead approval before implementation. Step 8 of the dev-workflow.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- ratomirjovanovic/pandawardtheir own version, first seen Nov 1, 2026
- es6kr/skillstheir own version, first seen Oct 13, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- ratomirjovanovic/pandaward★ 50same name
- es6kr/skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- create-prSkill
- delete-branchSkill
- dev-workflowSkill
- implement-fixSkill
- implement-planSkill
- init-referencesSkill
- merge-mainSkill
- plan-featureSkill
- read-referencesSkill
- test-lintSkill
- update-referencesSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
If the error report is not in context, run /test-lint again first
- Distinctive: line 108
Scope creep warning: If fixing an error would require changes to files NOT touched in the original implementation, flag it:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: /fix-plan
Usage
/fix-planInvoke with no arguments. Uses the error report from the most recent
/test-lint run as input.
Prerequisites
/test-lintmust have produced a FAIL result in this session- If the error report is not in context, run
/test-lintagain first
Mode: READ-ONLY
Same constraints as /plan-feature — no files written until approved.
Analysis Process
1. Categorize All Errors
Group every error from the quality gate into categories:
ERROR CATEGORIZATION:
──────────────────────────────────────────────────────────────
A. Code Style (auto-fixable) : {N} errors
→ Files: {list}
B. Type Errors : {N} errors
→ Files: {list}
C. Logic / Architecture Errors : {N} errors
→ Files: {list}
D. Failing Tests — Implementation : {N} failures
(test expectation was wrong)
→ Tests: {list}
E. Failing Tests — Test Quality : {N} failures
(test itself has a bug)
→ Tests: {list}
──────────────────────────────────────────────────────────────
Total errors: {N}2. Root Cause Analysis
For each non-trivial category (B, C, D), identify the ROOT CAUSE:
ROOT CAUSE ANALYSIS:
──────────────────────────────────────────────────────────────
[Category B — Type Error in ProductFilterService.php:42]
Root cause: Method signature uses array but caller passes Collection.
Origin : Mismatch between planning assumption and actual model type.
Fix scope : Narrow — change parameter type or add ->toArray()
[Category D — Test: ProductFilterTest::it_filters_by_category]
Root cause: Test uses hardcoded ID=1, but seeder creates ID=2.
Origin : Fragile test setup, not a logic error.
Fix scope : Update test factory to use the created model's ID.
──────────────────────────────────────────────────────────────3. Fix Plan
List every change needed, minimal and targeted:
FIX PLAN:
──────────────────────────────────────────────────────────────
[A — Auto-fix]
✏️ Run pint --fix on all style errors (automated, no logic change)
Files: {list}
[B — Type fix]
✏️ MODIFY app/Services/ProductFilterService.php:42
→ Change parameter type from array to Collection|array (union type)
[D — Test fix]
✏️ MODIFY tests/Feature/ProductFilterTest.php:38
→ Replace hardcoded ID with $product->id from factory result
──────────────────────────────────────────────────────────────
Total changes: {N} filesScope creep warning: If fixing an error would require changes to files NOT touched in the original implementation, flag it:
⚠️ SCOPE ALERT: Fixing {error} requires modifying {file} which was
NOT part of the original plan. This may indicate a deeper issue.
Options:
A) Narrow fix: adjust only the interface/call site
B) Proper fix: update {file} (requires plan approval)
Recommend: {A or B with justification}4. Approval Request
──────────────────────────────────────────────────────────────
FIX PLAN READY — AWAITING APPROVAL
──────────────────────────────────────────────────────────────
Errors found : {N}
Files to fix : {N}
Auto-fixable : {N} (pint / eslint --fix)
Manual fixes : {N}
Scope creep risk : yes / no
Respond with:
✅ approve — proceed to /implement-fix
✏️ revise {N} — clarify or change item N in the fix plan
❌ reject — cancel and explain (may need to re-plan the feature)
──────────────────────────────────────────────────────────────Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

