| name | brain-dump-review |
| description | Review Brain Dump ticket work using CLI commands only. Use when implementation is finished and findings, fixes, and demo generation need to be tracked without MCP. |
Brain Dump Review
Use this skill after code changes are implemented and validation has run.
Review process
1) Inspect changes
git diff --stat
git diff
brain-dump context --ticket <ticket-id> --pretty
2) Run validation
Discover and run this project's validation commands from docs/config. Do not assume
pnpm, npm, TypeScript, lint, or test scripts exist. If no automated validation
command is discoverable, run a targeted manual smoke check and record that no
project validation command was found.
3) Submit findings through Brain Dump CLI
For each issue found:
brain-dump review submit-finding \
--ticket <ticket-id> \
--agent <code-reviewer|silent-failure-hunter|code-simplifier> \
--severity <critical|major|minor|suggestion> \
--category <category> \
--description "<issue description>" \
[--file <path>] \
[--line <line>] \
[--fix "<suggested fix>"] \
--pretty
Capture the returned findingId.
4) Fix and mark fixed
After fixing an issue:
brain-dump review mark-fixed --finding <finding-id> --status fixed --description "<how it was fixed>" --pretty
5) Check whether review is complete
brain-dump review check-complete --ticket <ticket-id> --pretty
Proceed only when critical and major findings are resolved.
6) Generate demo steps
Write a JSON steps file, then run:
brain-dump review generate-demo --ticket <ticket-id> --steps-file <path-to-json> --pretty
Severity guide
critical: broken feature, crash, data loss, or severe security riskmajor: incorrect behavior, missing validation, serious error handling issueminor: maintainability or clarity issue without user-facing breakagesuggestion: optional improvement
Agent mapping
Use these agent names consistently:
code-reviewersilent-failure-huntercode-simplifier
Goal
Track review work in Brain Dump using CLI commands only, then hand off to human review.
