ask
無料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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Run a full expert code review before merging.
git --no-pager diff main...HEAD | head -500
Or specify a branch: git --no-pager diff <base>...<head> | head -500
claude/templates.md for PR template requirementsclaude/rules.md for project-specific rules"Spawn a reviewer subagent to review this PR. Diff: [paste diff]. Focus on the 10-point protocol."
Point 1 — Ticket re-read: Does every scenario in the ticket/task get addressed?
Point 2 — Cross-layer consistency: Grep every new field name, type, enum across ALL layers:
grep -rn --color=never '<new_field_name>' . | head -50
Point 3 — Enum completeness: Are all enum values handled in every switch/if-chain?
Point 4 — Transaction safety: Are there external calls (HTTP, queue, email) inside DB transactions? → Move them outside.
Point 5 — Race conditions: Is there shared mutable state accessed concurrently without synchronization?
Point 6 — Test coverage: Every new branch/case/error path has a dedicated test?
Point 7 — Pre-existing vs. introduced: Run lint before and after. Distinguish new warnings from pre-existing ones.
Point 8 — Cross-branch merge safety: Will this still apply cleanly after other pending branches merge?
Point 9 — Security: New HTTP calls? Data exposed? New permissions? Unsafe defaults?
Point 10 — Confidence gate: Overall confidence 0-100. Only proceed to PR description if ≥95.
Report format:
Use /mr skill after the review passes.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Use before any new feature, component, or behavioral change — when you need to explore requirements and design before writing code
日本語の概要は準備中です。原文の説明を表示しています。
Activate safety guards for the session. Use /careful before critical operations — blocks rm -rf, DROP TABLE, git push --force, kubectl delete namespace, docker system prune via PreToolUse hook.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a user-facing changelog from git commits — categorize, filter noise, translate to user language. Runs in isolated fork context.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。