Menu
Generate a PR/MR description after the review passes. Use after /review confirms the code is ready to merge. Reads claude/templates.md for the required format.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Route a codebase question to the right tool — structural graph, semantic search, or risk analysis. Use when you need to find or understand code without knowing exact file names.
Auto-configure CLAUDE.md and claude/ knowledge docs for a new project. Use when setting up Brain Bootstrap in a new repository. Discovers the codebase, fills in templates, and writes project-specific configuration.
Build the project and verify it compiles cleanly. Use after making changes to confirm nothing is broken before running tests. Reads the build command from claude/build.md.
Save session state before context gets full or before ending. Writes current task state, branch, and loaded docs to claude/tasks/todo.md so the next session can resume cleanly.
Remove all git worktrees for merged branches. Accepts --dry-run to preview. Use after merging PRs or for weekly maintenance.
Clean workspace — build artifacts, dependencies, caches, Docker volumes, or temp files. Accepts arguments like build, deps, all, cache, docker, tasks, reinstall.
| name | mr |
| description | Generate a PR/MR description after the review passes. Use after /review confirms the code is ready to merge. Reads claude/templates.md for the required format. |
Generate a structured pull request description.
/review MUST pass (verdict: PASS, confidence ≥ 95) before generating a PR description# Confirm tests pass
# (use the test command from claude/build.md)
If tests fail: STOP. Fix before generating the PR description.
Read claude/templates.md — the required PR/MR format for this project.
git --no-pager diff main...HEAD --stat | head -50
git --no-pager log main...HEAD --oneline | head -20
If a ticket number is referenced, extract the requirements from it.
Use the template from claude/templates.md. If no template exists, use this default:
## What
<One paragraph: what does this change do and why?>
## Why
<One paragraph: what problem does this solve? Link to ticket.>
## How
<Bullet list: key implementation decisions and approach>
## Testing
<What was tested? How? Test commands run + results>
## Checklist
- [ ] Tests pass
- [ ] No new warnings
- [ ] Documentation updated (if applicable)
- [ ] Breaking changes documented (if applicable)
Show the PR description and proposed git push command. Wait for confirmation before pushing.