implement-fix
Skill1 starsChanged 8 months agoMITView on GitHub
Applies the approved fix plan to resolve lint, type, and test errors. Strictly applies only the approved fixes — no additional changes. Step 9 of the dev-workflow.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- PatriotAgenticLLC/better_claude_skillztheir own version, first seen Jul 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- PatriotAgenticLLC/better_claude_skillz★ 3same 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
- fix-planSkill
- 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
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
Do NOT improve, refactor, or clean up anything else
- Distinctive: line 40
If the fix plan includes auto-fixable items:
- Distinctive: line 79
After applying each fix, run the SPECIFIC test or lint check that was failing — not the full suite:
- Distinctive: line 90
If the spot check still fails:
- Distinctive: line 97
Do NOT proceed to the next fix until the current one is confirmed passing.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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: /implement-fix
Usage
/implement-fixInvoke with no arguments. Executes the approved fix plan from /fix-plan.
Prerequisites
/fix-planmust have been approved by the lead in this session- The original implementation from Step 4 must be in place
Rules
Same as /implement-plan but stricter scope:
- Fix ONLY what the approved fix plan lists
- Do NOT improve, refactor, or clean up anything else
- Auto-fixable tools should run FIRST so manual fixes build on clean code
- Report each fix as it's applied
Execution Process
1. Apply Auto-fixes First
If the fix plan includes auto-fixable items:
Laravel (Pint)
./vendor/bin/pint {file1} {file2} ...Confirm each file changed:
✅ [1/{N}] pint auto-fixed: {file} — {N} changes appliedReact / React Native / Frontend (ESLint)
npx eslint {files} --fixConfirm:
✅ [1/{N}] eslint auto-fixed: {file} — {N} rules corrected2. Apply Manual Fixes
For each manually fixed item in the plan:
Before editing: re-read the target file to confirm current state After editing: output a brief diff summary:
✅ [{N}/{total}] FIXED: {file}:{line}
Error was : {error message}
Fix applied: {1-line description}3. Verify Each Fix (spot check)
After applying each fix, run the SPECIFIC test or lint check that was failing — not the full suite:
# Laravel: run single test
php artisan test --filter {TestClassName}
# React/RN: run single test file
pnpm test --run {file_pattern}If the spot check still fails:
❌ Spot check failed for {test/file}.
Error: {message}
This fix is not complete — pausing for lead review.Do NOT proceed to the next fix until the current one is confirmed passing.
4. Completion Report
──────────────────────────────────────────────────────────────
FIX IMPLEMENTATION COMPLETE
──────────────────────────────────────────────────────────────
Auto-fixes applied : {N}
Manual fixes applied: {N}
Spot checks : {N}/{N} passed
Files modified: {list}
Next step: /git-commit (then /test-lint to confirm full suite)
──────────────────────────────────────────────────────────────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.

