一键导入
test
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
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
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
用 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 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 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
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 | test |
| description | 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 |
| user-invocable | true |
Generate runnable tests for code with the testgen tool (a coding-specialized model that lists edge cases before writing tests).
files (use path:start-end line ranges for large files). Otherwise take the pasted code.framework. If there are existing tests nearby, paste one via existingTests so the generated tests match your conventions.edge (boundaries + failure modes), happy (main paths), regression (lock current behavior), or all (default).testgen({ code | files, framework?, coverage?, existingTests? }).Requires OPENROUTER_API_KEY. If the tool returns its missing-key error, relay it and suggest /setup.