claude-code-brain-bootstrap

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.

Load all relevant claude/ knowledge files for a domain area. Use at session start or when switching to a new topic. Accepts a domain keyword like api, database, auth, build, security.

Query the database — list schemas, tables, describe a table, or run SQL. Accepts arguments like schemas, tables, describe <table>, or raw SQL.

Root cause analysis for bugs and errors. Use when something is broken and the cause is not obvious. Applies the 5-step investigation method — observe, hypothesize, trace backwards, binary search, prove.

Manage dependencies and fix CVEs — check outdated packages, update a specific package, run security audit, explain why a package is installed, or deduplicate. Read claude/cve-policy.md for the decision tree.

Analyze branch diff against merge-base — stat overview, full diff, file list, commit list, or branch overlap check. Always uses merge-base to exclude main's forward progress.

Docker workflow helpers — list containers, build, run, logs, compose up/down, prune. Non-interactive only.

Git workflow helpers — status, rebase, commit, amend, log, stash, branch management. Includes pre-push checklist. NEVER git push autonomously.

Verify Claude configuration health — CLAUDE.md, settings.json, hooks, agents, skills, secrets scan, and MCP reachability. Reports ✅/⚠️/❌ for each check.

Run the linter and formatter check. Use before opening a PR to ensure code style compliance. Reads lint command from claude/build.md.

Detect and fix stale claude/*.md knowledge docs. Use when claude/architecture.md or build.md references missing files, wrong commands, or outdated patterns. Keeps the knowledge base accurate.

Manage MCP (Model Context Protocol) servers — list configured tools, check status, show invocation format, or add a new server to .claude/settings.json.

Run database or schema migrations — up, down, rollback, status, or create a new migration. Reads claude/build.md for migration commands.

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.

Plan a non-trivial task before implementing. Use when the task requires 3+ steps, multiple files, or an architectural decision. Writes a checkable plan to claude/tasks/todo.md.

Isolated codebase exploration that preserves your main context. Use when you need to understand code structure, trace call paths, or gather evidence before making changes. Spawns an explorer subagent.

Resume a previous session from claude/tasks/todo.md. Use at the start of a new session to restore context and continue where you left off.

Full 10-point expert code review. Use before any PR or MR. Checks correctness, cross-layer consistency, transaction safety, test coverage, and security. Spawns reviewer subagent for isolation.

Start service(s) locally for development. Accepts a service name, all, frontend, or backend. Reads claude/build.md for the actual start commands.

Generate a parallel workstream plan for multi-agent Claude Code work. Decomposes a feature into independent workstreams, each ownable by a separate Claude Code instance. Saves to claude/tasks/ACTION_PLAN.md.

Project status dashboard — CLAUDE.md budget, unfilled placeholders, lessons file size, hooks executability, jq availability, plugin states. One-glance health report.

Run the test suite and report results. Use after making changes to verify nothing is broken. Reads the test command from claude/build.md.

Create a ticket/issue description with evidence-backed proof sections. Reads claude/templates.md for the template format. Saves to claude/tasks/ticket-<slug>.md.

Scan codebase exports and generate CODE_INDEX.md organized by capability. Check this index before writing new functions to prevent duplication (no more formatDate2 when formatDate exists).

Manage git worktrees for parallel work on multiple branches simultaneously. Use when you need to work on two features at once without stashing or branch-switching.

Show all active git worktrees with branch name, dirty/clean status, and last commit. Use after /worktree to check state across all parallel branches.

Use before any new feature, component, or behavioral change — when you need to explore requirements and design before writing code

Use when you want to see token consumption by task type, model, one-shot rate, or USD cost — observability dashboard for Claude Code sessions

Issue triage — audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis, issue numbers to focus (e.g. "42 57"), "fr" for French, no arg = audit only in English.

Browser automation — navigate, click, fill, snapshot web pages. Use for UI testing, documentation scraping, OAuth flows, web research.

PR triage — audit open PRs, deep review selected ones, draft and post review comments. Args: "all" to review all, PR numbers to focus (e.g. "42 57"), "fr" for French output, no arg = audit only in English.

Use when receiving code review feedback — before implementing suggestions, especially if feedback seems unclear or technically questionable

Use when renaming symbols across files, finding all references to a function/class, moving code between files, or inlining variables — LSP-backed atomic multi-file refactoring

Use when executing implementation plans with independent tasks — dispatches fresh subagents per task with two-stage review (spec compliance, then code quality)

Use when creating new skill files, editing existing SKILL.md files, or reviewing skills before deployment — covers structure, CSO (discoverability), and quality standards