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.
日本語の概要は準備中です。原文の説明を表示しています。
Run integration and e2e tests after unit tests pass. Use after /supergraph:fix when unit tests are green.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Integration + e2e tests. Validates modules work together. Run AFTER unit tests pass.
/supergraph:integration | plan auth-login | plan auth-login task 3
$TEST_CMD green)/supergraph:fix completed"🔗 /supergraph:integration — running integration and e2e tests..."
Read from plan ## Environment Context or .supergraph-env. Missing → STOP, run /supergraph:scan first.
$TEST_CMD
If unit tests FAIL → STOP: "Unit tests must pass before integration. Run /supergraph:fix first."
Check for integration configuration:
| Config | Command |
|---|---|
jest.integration.config.js | npx jest --config jest.integration.config.js |
vitest.integration.config.ts | npx vitest --config vitest.integration.config.ts |
pytest.ini with [integration] or -m integration | pytest -m integration |
cypress.config.js / cypress.config.ts | npx cypress run |
playwright.config.js / playwright.config.ts | npx playwright test |
docker-compose.test.yml | docker compose -f docker-compose.test.yml up --abort-on-container-exit |
*.integration.test.ts / *.integration.spec.ts pattern | npx jest --testPathPattern="integration" |
If none found → skip: "No integration/e2e config found — skipping."
Max 3 retries. On failure:
4b. Serena (optional): See serena/SKILL.md:Setup — find_referencing_symbols/get_diagnostics_for_file per failing module to surface mismatches. Skip if unavailable.
Trace failure to source module, fix, re-run.
/supergraph:playwright-tester to generate or verify QA matrix coverage (Happy path, Sad path, Boundary, Network 500 error injection, Auth/RBAC) before proceeding.npx playwright test. Max 2 retries (e2e is inherently flaky). Flaky tests: annotate with @flaky / test.slow() / @pytest.mark.flaky per framework — do not block merge on known-flaky tests.For CBM_PROJECT via codebase-memory-mcp (see references/codebase-memory-contract.md) — search_graph/trace_path + recipes dependencies/cross-boundary/test-gaps; fall back to Serena/filesystem if empty.
Pass → mark in-progress tasks Status: completed.
Fail after 3 retries → mark stuck, append failure log.
✅ /supergraph:integration complete
- Unit: PASS | Integration: PASS|FAIL|SKIP | E2E: PASS|FAIL|SKIP
- Cross-module flows: N/M covered | Surprising connections: [list/none]
- Plan status: updated|none
- Next: /supergraph:verify → /supergraph:review
@flaky-annotated e2e tests/supergraph:verify → /supergraph:reviewまだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。