メニュー
Use when code changes are ready for review — a diff exists, the user says "review my changes/PR", or a commit is about to happen. Multi-model diff review (Kimi, DeepSeek, GPT-5.5 panel + Gemini judge) with a MERGEABLE verdict
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the user wants a security review of code or a diff — OWASP/CWE findings with severity, taint/data-flow analysis, and concrete fixes via security_review
Use when the user wants tests generated for code or a diff — enumerates edge cases and failure modes first, then emits runnable test code via testgen
Use when a task would benefit from a structured thinking technique but you're not sure which — recommends the right prompt technique for the intent (debug, spec, refactor, decision, design) and applies it
Use for decisions or judgments worth multiple independent perspectives — multi-model council with parallel analysis, search grounding, and synthesis (30-60s); for a quick single-call verdict use the jury tool directly
Use when the user shares or finishes a plan and wants it stress-tested before execution — adversarial multi-model pre-mortem with ranked risks, mitigations, and concrete plan edits
Use when TachiBot tools seem missing, a provider isn't working, or the user asks to set up/configure TachiBot or its API keys — runs doctor and walks through fixing the gaps
| name | review |
| description | Use when code changes are ready for review — a diff exists, the user says "review my changes/PR", or a commit is about to happen. Multi-model diff review (Kimi, DeepSeek, GPT-5.5 panel + Gemini judge) with a MERGEABLE verdict |
| user-invocable | true |
Review the user's current change with the diff_review tool.
git diff (unstaged), falling back to git diff HEAD (all uncommitted) — if both are empty, use git diff main...HEAD (branch changes). If still empty, tell the user there is nothing to review and stop.git log --oneline -5).diff_review with: diff (the collected diff), intent, focus if the user named one (security | perf | correctness | style), and files for any file the diff touches heavily (use path:start-end ranges around the hunks).major and above; mention how many minor/nit findings were omitted.Needs GEMINI (judge) plus OPENROUTER and/or OPENAI keys (reviewers self-drop). If the tool returns a "no reviewers available" error, show the user its message — it names the missing keys.