majiayu000 Analyze the conversation to detect which skill is running, reflect on what went wrong, propose specific fixes, get user approval, then apply changes with optional commit.
- Look for skill invocation messages
- Check which SKILL.md was recently referenced
- Examine current task context
Set: SKILL_NAME=[skill-name] and SKILL_DIR=./skills/$SKILL_NAME
If unclear, ask the user.
Determine:
- What was wrong: Quote specific sections from SKILL.md that are incorrect
- Discovery method: Context7, error messages, trial and error, documentation lookup
- Root cause: Outdated API, incorrect parameters, wrong endpoint, missing context
- Scope of impact: Single section or multiple? Related files affected?
- Proposed fix: Which files, which sections, before/after for each
**Skill being healed:** [skill-name]
**Issue discovered:** [1-2 sentence summary]
**Root cause:** [brief explanation]
**Files to be modified:**
- [ ] SKILL.md
- [ ] references/[file].md
- [ ] scripts/[file].py
**Proposed changes:**
### Change 1: SKILL.md - [Section name]
**Location:** Line [X] in SKILL.md
**Current (incorrect):**
[exact text from current file]
**Corrected:**
[new text]
**Reason:** [why this fixes the issue]
[repeat for each change across all files]
**Impact assessment:**
- Affects: [authentication/API endpoints/parameters/examples/etc.]
**Verification:**
These changes will prevent: [specific error that prompted this]
- Yes, apply and commit all changes
- Apply but don't commit (let me review first)
- Revise the changes (I'll provide feedback)
- Cancel (don't make changes)
Choose (1-4):
**Wait for user response. Do not proceed without approval.**
</step_5>
<step_6 name="apply_changes">
Only after approval (option 1 or 2):
1. Use Edit tool for each correction across all files
2. Read back modified sections to verify
3. If option 1, commit with structured message showing what was healed
4. Confirm completion with file list
</step_6>
</process>
<success_criteria>
- Skill correctly detected from conversation context
- All incorrect sections identified with before/after
- User approved changes before application
- All edits applied across SKILL.md and related files
- Changes verified by reading back
- Commit created if user chose option 1
- Completion confirmed with file list
</success_criteria>
<verification>
Before completing:
- Read back each modified section to confirm changes applied
- Ensure cross-file consistency (SKILL.md examples match references/)
- Verify git commit created if option 1 was selected
- Check no unintended files were modified
</verification>