analyze
無料Risk analysis and approach selection before planning. Use when requirements are ambiguous, approaches vary, or work touches hub/bridge nodes. Skip for typo fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Fresh verification gate before claiming done, fixed, passing, ready, or before commit/PR. Evidence before claims, always.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Requires healthy index_status for CBM_PROJECT (see references/codebase-memory-contract.md); then codebase-memory-mcp detect_changes, trace_path, recipes cycles/hubs/bridges/test-gaps. Block on degraded/new cycle/unapproved hub/missing tests.
Fresh verification gate before completion claims.
Iron Law: NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
Before saying/implying: done, fixed, passing, clean, ready, complete, works, verified, successful.
Also: before marking Status: completed, committing, PR'ing, accepting agent reports, moving to next phase.
/supergraph:verify | tests | lint | build | plan auth-login task 2 | claim "login fixed"
| Claim | Required fresh evidence |
|---|---|
| Tests pass | $TEST_CMD exits 0, zero failures |
| Lint clean | $LINT_CMD exits 0, zero errors |
| Build succeeds | $BUILD_CMD exits 0 |
| Bug fixed | Original failing symptom/test now passes |
| Regression covered | RED failed before fix, GREEN passes after |
| TDD complete | RED failure valid, GREEN passes, refactor verified |
| Task completed | Acceptance criteria met + verification commands pass |
| Agent completed | Diff inspected + independent tests/lint |
| Review passed | Reviewer + graph review + tests/lint pass |
| Ready to merge | Tests + lint + build + review PASS |
"✅ /supergraph:verify — verifying [claim] with fresh evidence..."
Map claim to required proofs from evidence mapping.
0 plans → skip | 1 → use | >1 → ask | plan <slug> → match.
Read from plan ## Environment Context or .supergraph-env (set by /supergraph:scan). Missing → STOP, run scan first.
No command can prove claim → STOP: "Required check is unknown."
serena/SKILL.md:Setup — get_diagnostics_for_file per touched file; STOP on type errors before test suite. Skip if SERENA_ACTIVE=false or unavailable.For agent output: git diff --stat && git diff --name-only.
Then run relevant tests/lint/build locally.
Freshness guard (dedup suite, preserves Iron Law): Reuse of immediately prior evidence is allowed only if HEAD_SHA unchanged and git diff --name-only HEAD unchanged and last PASS timestamp <120s ago (same commit). Otherwise must rerun $TEST_CMD/$LINT_CMD fresh NOW. Guard respects CBM_INDEXED_AT TTL from /supergraph:scan but never skips verification before merge/PR — if HEAD_SHA changed, reuse is invalid.
Check: exit code, failure count, error count, warnings. Don't confuse lint ≠ build, targeted ≠ suite.
Pass:
## Verification Evidence
- Claim: [claim] | Command: `[command]` → exit 0 → PASS
- Evidence: [output summary] | Timestamp: [now]
Fail:
## Verification Failed
- Claim: [claim] | Command: `[command]` → exit [N] → FAIL
- Failure: [summary] | Next: /supergraph:fix
Cannot verify → say so explicitly. No completion language.
Only after evidence passes: in_progress → completed.
If failed → keep status or mark stuck if retries exhausted.
For user-facing confirmation: Announce task/plan completion in the user's language. If plan context exists, show: "Task N completed — [user-facing summary]"
✅ /supergraph:verify complete
- Claim: [claim] | Evidence: [command] → PASS|FAIL
- Next: [recommendation]
Evidence before claims, always. Fresh only — old runs don't count. Read output before reporting. No positive language without proof. Agent output requires independent verification.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Risk analysis and approach selection before planning. Use when requirements are ambiguous, approaches vary, or work touches hub/bridge nodes. Skip for typo fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Proactive architecture review — explore codebase structure, generate a self-contained HTML report with Mermaid diagrams and candidate improvements, then grill the findings. Use when planning a large refactor, onboarding to an unfamiliar codebase, or before a major architectural change.
日本語の概要は準備中です。原文の説明を表示しています。
Persistent token-compression mode (~75% reduction) — now always-on by default. Strips filler while keeping code exact.
日本語の概要は準備中です。原文の説明を表示しています。
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).
日本語の概要は準備中です。原文の説明を表示しています。
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
日本語の概要は準備中です。原文の説明を表示しています。
Structured 6-phase debugging. Build feedback loop first, reproduce deterministically, hypothesize with ranked falsifiable theories, instrument one variable at a time, fix with regression test, cleanup. Use when a bug exists, tests fail unexpectedly, or behavior is wrong and cause is unknown.
日本語の概要は準備中です。原文の説明を表示しています。