skill-improvementlisted

Detects when a Claude Code session reveals a gap, bug, or improvement in an existing skill, then proposes a targeted patch and (with user approval) creates a local git branch and commit in the skills repo. Trigger this skill whenever you notice during a session that: a skill gave wrong or incomplete guidance, you had to correct or supplement a skill's instructions, a workaround was needed that should be documented, or the user says something like "the skill missed this", "add this to the skill", or "we should update the skill". Also trigger proactively at the end of any session that used a skill and produced fixes or new knowledge. Never wait for the user to ask.
mouchegmouradian/claude-code-skills · ★ 2 · AI & Automation · score 73

Install: claude install-skill mouchegmouradian/claude-code-skills

# Skill Improvement This skill captures knowledge gained during a working session and feeds it back into the relevant skill — keeping skills accurate and up to date without manual maintenance. ## When to trigger Trigger this skill whenever, during a session, you observe any of the following: - A skill's instructions were incomplete or wrong and you had to correct course - You discovered an edge case the skill didn't cover - The user corrected you in a way that implies a skill gap - A fix, workaround, or pattern emerged that should be documented for next time - The user explicitly says "update the skill", "add this to the skill", etc. - At **natural session wrap-up points** when a skill was actively used — proactively check if anything is worth capturing, even if the user didn't mention it Don't wait to be asked. If you notice something, surface it. ## Skill repo location The skills git repo is at: `~/Projects/claude-code-skills/` Skills source lives at: `~/Projects/claude-code-skills/skills/` The `~/.claude/skills/` directory contains symlinks into the above. ## The improvement flow ### Step 1 — Identify and summarize the gap When you detect an improvement opportunity, pause and tell the user: > "I noticed something worth capturing in the **[skill-name]** skill: [one-sentence description of the gap or fix]. > Want me to propose a patch?" Keep it brief. Don't write the patch yet. ### Step 2 — Draft the patch If the user says yes (or "go ahead", "sure", etc.), d