00 What claude-toolbox caught while AI was building capy
"I took the shortcut."
— your LLM
Three /kk:review-code runs on the same capy diff. Each time, the agent read the code first and got to the review checklists late or not at all. In the third run it was told to "follow the review process exactly". It loaded 28 files and still read the diff first. The skill itself said to start with the diff, so the fix was to change the order, not to write a sterner prompt.
capy is a local MCP server, written in Go, that keeps large outputs out of a coding agent's context window. It was built from start to finish with claude-toolbox: skills, sub-agents and config for Claude Code and Codex, run as /kk: commands from design through review, tests and docs. Below is what they caught along the way, quoted from capy's own records. Nothing is staged.
Left behind All 16 skills now load their method before they touch your code. From review-code/SKILL.md: "The standard workflow below is strictly sequential."
From the same record: "Enforcement is convention, not mechanism."
$ /kk:review-code # three runs, same diff
docs/adr/0004-skill-workflow-ordering.md
- 15 - **Run 1.** … When pressed, the agent admitted: "I had the full diff visible, recognized the changes as a clean source-kind refactor, and decided I could pattern-match a review from the diff alone. I took the shortcut."
- 17 - **Run 3.** User explicitly asked the agent to "follow the review process exactly." Agent loaded 28 files but still diffed first, then circled back to read checklists after findings were already forming.
- 21 This is a workflow-ordering bug, not an agent-discipline bug.
# where the three runs happened
docs/feat/done/kubernetes-support/design.md
- 483 **Flagged by:** Task 7 P0 verification dry-run (2026-04-19) — user-led `/kk:review-code` runs in a sibling Go project (`capy`) reproduced the same process-bypass behavior across three consecutive invocations.