Always use this skill before claiming any work is done, fixed, passing, or complete — even if it seems obvious. Also use when receiving code review feedback from any source (human or automated), when finishing a task or major feature, before committing or creating a PR, or when about to express satisfaction with work. Covers three practices: receiving feedback with technical rigor (no performative agreement), triggering code review via /code-review command or cook/fix pipelines, and verification gates (run the command, read the output, then make the claim). Never skip — the cost of false completion claims is higher than the cost of verifying. References: code-review-reception.md, requesting-code-review.md, verification-before-completion.md.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Apply code review practices with technical rigor, evidence-based claims, and verification over performative responses.
| Practice | When to load | File |
|---|---|---|
| Receiving feedback | Unclear/questionable feedback, conflict with reviewer | references/code-review-reception.md |
| Requesting review | After each task, before merge — use /code-review | references/requesting-code-review.md |
| Verification gates | Before any completion/success claim | references/verification-before-completion.md |
Code review requires three distinct practices:
Technical correctness over social comfort. Verify before implementing. Ask before assuming. Evidence before claims.
Trigger when:
Trigger when:
Use /code-review (local) or /code-review <PR> (PR mode). ck:cook, ck:quality, and ck:test remain separate gates; run final code review after their required artifacts are current.
Trigger when:
SITUATION?
│
├─ Received feedback
│ ├─ Unclear items? → STOP, ask for clarification first
│ ├─ From human partner? → Understand, then implement
│ └─ From external reviewer? → Verify technically before implementing
│
├─ Completed work
│ ├─ Major feature/task? → Run /code-review (or it's automatic in cook/fix)
│ └─ Before merge? → Run /code-review <PR-number>
│
└─ About to claim status
├─ Have fresh verification? → State claim WITH evidence
└─ No fresh verification? → RUN verification command first
READ → UNDERSTAND → VERIFY → EVALUATE → RESPOND → IMPLEMENT
Full protocol: references/code-review-reception.md
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
IDENTIFY command → RUN full command → READ output → VERIFY confirms claim → THEN claim
Using "should"/"probably"/"seems to", expressing satisfaction before verification, committing without verification, trusting agent reports.
Full protocol: references/verification-before-completion.md
Verify. Question. Then implement. Evidence. Then claim.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Build robust backend systems — APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), databases, performance optimization, security (OWASP Top 10), scalability patterns (microservices, caching, sharding), and testing. Use when designing APIs, implementing auth, optimizing queries, handling security vulnerabilities, building microservices, or developing production-ready backend systems.
日本語の概要は準備中です。原文の説明を表示しています。
Terse output mode — strips filler/articles/hedging, ~75% token reduction. Activate whenever: context is filling up, user says be brief/terse/caveman/less tokens, or CAVEMAN_TRIGGERED appears in context. Persists every response until CAVEMAN_RELEASED or user says stop/normal mode.
日本語の概要は準備中です。原文の説明を表示しています。
Explore and debate solutions before writing code. Use when the user poses a design question, asks "how should I approach X", wants to think through options before committing, or says anything like "let's brainstorm", "what's the best way to...", "I'm not sure how to tackle this", or "should I use X or Y". Always runs before /ck:plan for novel or ambiguous features. No code is written — only: explore → clarify → spec → report.
日本語の概要は準備中です。原文の説明を表示しています。
Implement a feature phase by phase from a phased JSON master or Markdown plan. Before each phase, confirm whether to create/run unit tests and whether to run ck:quality, unless explicit flags supply those choices. Supports token-budgeted execution, resumable state, and TDD handoff to ck:test.
日本語の概要は準備中です。原文の説明を表示しています。
Fix a bug using Scout → Diagnose → Fix → Review → Finalize. Use when the user pastes an error message, stack trace, or test failure, or says "fix this bug", "something's broken", "tests are failing", "I'm getting an error". Also accepts `--from-quality <report>` or `--from-test <report>` to fix exactly the findings/failures a report lists. Modes (pick one): --fast (trivial errors — lint, type, build — skip scout and review), --hard (mandatory review, no auto-approve).
日本語の概要は準備中です。原文の説明を表示しています。
Plan a feature or system before implementation. Use when the user says "plan this", "I want to build X", "how do I implement Y", or when /ck:brainstorm produces a spec.md. Always run before /ck:cook. Modes (pick one): --fast (simple, single-file), --hard (research + red-team + validate). Composable flag (combine with any mode): --tdd — propagates into the cook pipeline. Every phase gets Design Constraints and Quality/Testing State; ck:cook confirms optional test and quality checks per phase.
日本語の概要は準備中です。原文の説明を表示しています。