メニュー
This skill should be used when the user asks to "test this feature", "verify this works", "run tests", "check if this is working", "test thoroughly", or mentions testing a specific feature or fix.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
One iteration of hypothesis-driven bug discovery — audit the codebase against project invariants and risk patterns via parallel agents, adversarially verify each candidate, and file a groomed bug-issue (red-test sketch + verification evidence + proposed root-cause fix) for every finding that clears the gate. Does NOT implement or ship — specialized dev processes pick up the filed issues. Use when invoked as `/bughunt` (runs one iteration); use `/loop bughunt` to run it as an autonomous loop. Project-agnostic; reads risk dimensions from CLAUDE.md key-invariants and project memory.
Reference document used by the build-iteration skill /shovel-ready for its single-iteration machinery — branch, sync-with-master, /ship handoff, /retro pass, merge, and declaring the loop outcome. NOT user-invokable, and NOT the loop. The loop lives in `/loop`; this is one iteration's build cycle. The find-and-file siblings (/kaizen, /bughunt, /kaikaku) use `file-cycle` instead. Only load when a build-iteration skill directs you here.
Reference document shared by the find-and-file iteration skills (/kaizen, /bughunt, /kaikaku) for their common single-iteration machinery — author groomed issue(s), label by validation, file autonomously (multi-output), and declare the loop outcome. NOT user-invokable, and NOT the loop. The loop lives in `/loop`; this is one iteration's file cycle. The file-type sibling of `build-cycle`. Only load when a find-and-file skill directs you here.
Continuous architectural simplification and correctness-by-construction — whole-system recon via parallel agents to find high-leverage opportunities to simplify-and-beautify a structure OR foreclose a whole defect-class by making an illegal state unrepresentable, at the module/layer/concept altitude; steelman each candidate against Chesterton's Fence, then file groomed design-issue(s) for every candidate that clears the gate — autonomously, labeled by validation (no build, no in-session approval gate). Use when invoked as `/kaikaku` (runs one iteration); use `/loop kaikaku` to run it as an autonomous loop. The architectural-altitude sibling of `/kaizen`. Project-agnostic; reads simplicity + beauty + correctness stance from CLAUDE.md and project memory.
One iteration of accidental-complexity reduction — audit the codebase against craftsmanship principles via parallel agents, and file a groomed cleanup-issue for every candidate that clears the gate. Does NOT implement or ship — specialized dev processes pick up the filed issues. Use when invoked as `/kaizen` (runs one iteration); use `/loop kaizen` to run it as an autonomous loop. The instance/tidy-altitude sibling of `/kaikaku`. Project-agnostic; reads simplicity heuristics from CLAUDE.md and project memory.
Drive any single-iteration development skill as an autonomous loop — invoke one iteration, read its declared outcome, then pace, escalate, or stop. Use when invoked as `/loop <skill> [flags]` (e.g. `/loop kaizen --auto`, `/loop bughunt`, `/loop kaikaku`, `/loop shovel-ready --auto`). Owns cadence, idle escalation, and re-arming so the iteration skills stay pure. Pass `--once` to run exactly one iteration.
| name | test |
| description | This skill should be used when the user asks to "test this feature", "verify this works", "run tests", "check if this is working", "test thoroughly", or mentions testing a specific feature or fix. |
Verify functionality through automated and manual testing. Clean up all artifacts before reporting.
Verify functionality works correctly across happy paths, edge cases, and error scenarios. Think carefully about what could go wrong. Think like a user trying to break the system.
Test Target: [Feature/component name] Results: X/Y scenarios passed Critical Issues: [Blocking problems, if any] Recommendation: [Go/No-go with reasoning]
Notable findings:
"test file upload with large files" → Test various file sizes, concurrent uploads, network interruptions, file type validation
After implementing auth: → Test login/logout, invalid credentials, session expiry, concurrent sessions, permission checks
Test destructively but clean up completely. The goal is finding issues, not fixing them.
