Strict test-driven development for behavior changes. Requires verified RED before production code, minimal GREEN, and refactor only after passing tests.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Requires healthy index_status for CBM_PROJECT (see references/codebase-memory-contract.md with codebase-memory-mcp); if stale/degraded → index_repository before graph calls.
Strict TDD for features, bug fixes, refactors.
Iron Law: NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST
Delete means delete: Production code written before verified failing test → delete and restart from RED.
Full TDD: new features, behavior changes, refactoring. Fast TDD: bug fixes (add regression test → RED verify → minimal fix). Ask to skip: config-only, generated code, throwaway prototype, docs-only.
needs_test → red_verified → green_verified → refactor_allowed → complete
"🔴 /supergraph:tdd — TDD: [full|fast] for [behavior]..."
Behavior: [single externally visible behavior]
Test file: [path] | Test name: [name]
Command: [focused test command]
Expected RED: [why it should fail before implementation]
One behavior per test. Public behavior, not internals. Real code over mocks.
For a falsifiability checklist, read writing-good-tests.md before finalizing a test.
Write one failing test, then run immediately:
<write test> && $TEST_CMD <focused command>
Valid 🔴 RED: fails for the expected missing behavior, not syntax/import/typo.
Record evidence:
## TDD Evidence — 🔴 RED
- 🔴 RED: `[command]` → FAIL ([expected missing behavior])
Serena diagnostics (optional): See serena/SKILL.md:Setup — get_diagnostics_for_file before/after GREEN; use replace_symbol_body/rename_symbol over raw edits. Skip if SERENA_ACTIVE=false or unavailable.
Invalid RED → fix test setup, don't write production code yet.
Write only enough code to pass the test. No abstractions, no cleanup, no extra features.
Delete any production code written before RED.
Run focused test → broader suite:
## TDD Evidence — 🟢 GREEN
- 🟢 GREEN: `[command]` → PASS
- Suite: PASS
Failing test → fix code, not test. Other tests fail → fix now.
Rename, deduplicate, extract. No behavior changes. Re-run tests.
Before marking complete:
## TDD Complete
- Behavior: [behavior]
- Mode: full|fast
- RED verified: yes | GREEN verified: yes | Refactor: yes|none
- Tests: PASS
Per behavior: ✅ /supergraph:tdd — behavior N: [brief]
Final:
✅ /supergraph:tdd complete
- Behaviors: N | Mode: full|fast | Tests: PASS | Lint: PASS
- Next: /supergraph:fix → /supergraph:verify → /supergraph:review
For bugs, skip full TDD ceremony:
Plans must include TDD metadata per behavior task:
TDD:
- Behavior: [single behavior] | Test file: [path] | Test name: [name]
- RED command: `[focused test command]` | Expected RED failure: [missing behavior]
- Minimal GREEN change: [smallest implementation] | Mocking: none | [why unavoidable]
red_verified| Symptom | Fix |
|---|---|
| Production code before failing test | Delete, start RED |
| Tests after implementation | Next behavior test-first, remove untested code |
| "Too small to test" | Write one-liner test |
| Immediate pass accepted as RED | Test is wrong — revise |
| Pre-written implementation kept as reference | Delete, start fresh |
| Over-building before tests need it | YAGNI — remove |
Reject tests that only prove mocks exist or were called.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Risk analysis and approach selection before planning. Use when requirements are ambiguous, approaches vary, or work touches hub/bridge nodes. Skip for typo fixes.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Autonomous human-like browser control and professional QA/QC testing. Powered by agent-browser (Rust native CDP, zero Playwright) with ISTQB test matrix generation, automated testcase execution, console/network error tracing, and defect reporting.
The English summary is being prepared. Showing the original description.
Persistent token-compression mode (~75% reduction) — now always-on by default. Strips filler while keeping code exact.
The English summary is being prepared. Showing the original description.
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).
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.