fix
แก้ไขปัญหาตาม context ทั่วไปด้วย root cause analysis และ validate
SKILL.mdfix/SKILL.md
GitHubGoal
Fix problems, errors, or defects in any context through root cause analysis and safe correction
Scope
Use when an error is found or something needs fixing, regardless of domain or technology
Execute
1. Understand Problem
Goal: understand the problem to be fixed
- Take the error, symptom, or issue from the user
- If there is a stack trace or logs → read and summarize them
- If unclear → run
/ask-meto request more information
1.5 Choose Fix Mode
Goal: decide how to fix
- If the user types
fixwithout a scope orfix all→ fix every issue found in the current context - If earlier analysis produced suggestions → run
/follow-your-suggestion - If the user specifies a particular scope → fix only that scope
2. Analyze Context
Goal: find the root cause
- Run
/analyze-root-cause-analysisfor complex problems - Read the related files and config
- Use
/scan-codebaseto find call sites and consumers - Identify the root cause with evidence
3. Plan Fix
Goal: plan the fix
- List the files that need changing
- Choose a minimal, correct fix
- Assess the impact
- If high-risk → ask the user to confirm first
4. Apply Fix
Goal: apply the fix safely
- Create a checkpoint with
git stashor a branch - Change the code or config per the plan
- Check that nothing outside the scope was touched
- If many files change → work in small batches
5. Validate
Goal: confirm the fix is correct
- Run
/run-check(lint, typecheck, scan) - Run tests if available
- Run
/deep-validatefor the project - If it fails → repeat steps 2-4 (max 3 times)
6. Report
Goal: summarize the result
- Report what was fixed
- State the root cause and the fix approach
- Report the validation result
- If still unfinished → list what remains
Rules
Find the root cause before fixing
Use a minimal fix
Never guess causes without evidence
Create a checkpoint before editing
Do not edit outside the agreed scope
If blocked with a TODO → state it clearly in
TODO.mdUse /follow-your-suggestion if needed
Use /resolve-errors if needed
Use /run-test all if needed
Use /run-until-pass if needed
Expected Outcome
- The problem is fixed
- Code passes validation
- Root cause and fix approach are clearly reported