thevibeworks/ccx/ccx-retro
Claude Code and agent skill by thevibeworks/ccx
- community
Checking that the SKILL.md file is still in the repository.
Where did the agent go wrong, what fixed it, and what should change so it doesn't happen again? Mine a coding-agent session for mistakes, corrections, and wasted loops, then propose durable rule changes (CLAUDE.md / AGENTS.md / skills / memory) with evidence. Use after a frustrating session, when the human asks "what went wrong", "why did it do that", "retro", or "turn this into a rule". Routing: this skill answers "what should change"; for a plain "what happened" account, use ccx-recap.
Install
npx vskill@latest install thevibeworks/ccx/ccx-retroSKILL.md
The same SKILL.md was published earlier as thevibeworks/ccx/ccx-retro.
ccx-retro
Recap tells you what happened. Retro makes the next run better. The real output is not a report — it is a proposed patch to the instructions the agent already reads (CLAUDE.md, AGENTS.md, a skill, memory), each line justified by evidence from the session.
This skill describes ccx >= 0.8. If a command or flag here is missing, upgrade ccx and run ccx skills install — the binary embeds skills matching its own CLI surface.
Process
- Outline.
ccx trace --json. Failure signals are factual and
already in it:
- steps with
errors(tool failures, attributed to the step that
issued the call)
- error streaks: consecutive steps failing at the same thing
- turns where the user pushed back — read the actual
user_text
and judge with your own comprehension; there is no correction flag, because keyword matching lies
interruptsanddenials(turn/step/stats): the human pressed
stop or refused a tool call — the sharpest correction signal in the log; the denied call's evidence is marked denied
- cost spikes without matching edits (spinning)
warnings(evidence gaps are findings too)
- Drill.
ccx trace --turn Non each suspect; `ccx view
<session> --at <message_id> for the exact exchange. Reconstruct: what did the agent believe, what was actually true, what evidence was available at the time, what finally corrected it (user, test, self-check)? If the mistake was inherited from an earlier session (a stale handoff, a fork), ccx related <session>` finds it.
- Classify each finding.
mistake— agent had the evidence and got it wrongfriction— environment/tooling failed the agentdrift— agent misread intent; user had to steersave— something caught the problem (name what: a test, a
verification habit, a user correction). Saves become rules too.
- Propose changes. For each finding worth keeping, draft the
exact edit: file, section, wording. A rule earns its place only if:
- it would have prevented or shortened the observed failure, AND
- the next agent cannot derive it from code, docs, or common sense
Fewer, sharper rules beat a rulebook. One-off accidents are reported, not legislated.
- Human gate. Present findings + proposed patches and STOP.
Never write to CLAUDE.md / AGENTS.md / skills / memory without explicit approval. Rejected proposals are dropped, not stashed.
- Land approved patches with provenance. When the human
approves, apply the patch and carry the citation with the rule — a trailing (ccx:<session-id> #turn.step) reference — so the next reader can re-open the receipt with ccx trace instead of trusting the rule on faith. The session id is the audit trail; the rule text travels inline. Findings the human read but did not turn into rules may still be worth a devlog/memory entry — offer once, cite the same way.
Output shape
Every finding cites #turn.step. If nothing is worth changing, say so — "no durable lessons this session" is a valid retro.
Hard rules
- Findings without receipts don't ship.
- Judge corrections by reading the exchange, not by keywords.
- Propose the smallest rule that prevents the failure class.
- Do not create new knowledge stores; patch the ones the agent
already loads.
- Preserve the user's exact wording when their correction becomes a
rule — their phrasing carries the intent.
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/ccx-retro/SKILL.md
Popularity
- Repository stars
- 11
- Repository forks
- 3
- 7-day trend score
- 12
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/thevibeworks/ccx/ccx-retro)