ccc-compound

/ccc-compound — persist what this task taught

CC Commander · /ccc-compound · post-task learning capture so the next task starts cheaper. Pattern credit: Compound Engineering.

Arguments

$ARGUMENTS:

• empty — capture learnings from the current session (default flow below)
• review — show accumulated lessons; change nothing
• prune — propose outdated lessons for removal; delete only after confirmation

If review

1. Read tasks/lessons.md and list ~/.claude/learned-skills/ (either may be absent; say so).

2. Print:

   COMPOUND REVIEW
   Lessons:        <n> entries across <m> dates
   Learned skills: <k> files
   <lessons grouped by date, most recent first>
   

3. Stop. Do not extract or write anything.

If prune

1. Read tasks/lessons.md, the project CLAUDE.md and the files each lesson names.
2. For each entry, decide whether it still applies to the current code. List the stale ones with a one-line reason each.
3. Ask with AskUserQuestion (Codex: a plain-text question):
   • 🟢 Remove the listed entries — edits tasks/lessons.md
   • Pick entries one by one — confirm each before removing
   • Keep everything — no change
4. After editing, run git diff --stat -- tasks/lessons.md and report the removed line count. Stop.

Default: capture learnings

1. Review what just happened. Run in parallel:

   git log --oneline -10
   git diff --stat HEAD~3
   

   If HEAD~3 does not exist (new repo), use git diff --stat against the first commit or the working tree. Then scan the conversation for decisions made, corrections received and patterns discovered.

2. Extract learnings into three groups; skip any group with nothing meaningful:

   • Patterns: code patterns that worked (architecture, data flow, API design), tool or library usage worth repeating, efficient workflow sequences.
   • Corrections: what went wrong and its root cause, the fix, and how to prevent the class of error.
   • Decisions: what was decided and why, alternatives rejected, constraints that drove it.