Se Test — Testing skill for Claude Code
The general red-first rule — design any test so you have seen it fail for the right reason before you trust it green.
How to install Se Test
Installs to ~/.claude/commands/andreassigloch-graphcode-se-test.md
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/andreassigloch/graphcode/HEAD/.claude/commands/se-test.md -o ~/.claude/commands/andreassigloch-graphcode-se-test.md Restart Claude Code, or start a new session, for it to be picked up.
What Se Test does
name: se-test version: 1 description: The general red-first rule — design any test so you have seen it fail for the right reason before you trust it green. Use before writing or reviewing a test, or when a CR is about to close on "tests green". The UI-specific method is se-test-ui.
se-test — red-first, or it isn't coverage
The rule
**Never trust a green test you haven't seen fail for the right reason.** Green only counts as evidence once you have watched the same assertion go red
Alternatives in Testing
- TDD Diagnostics.V1 — Follow strict TDD stages 272 ★
- Test Driven Development.SKILL — Enforces TDD discipline with RED-GREEN-REFACTOR cycle 262 ★
- Green — Execute TDD Green Phase - write minimal implementation to pass the failing test 168 ★
Full documentation available on GitHub
View Source RepositoryRelated Skills
Se Test UI
Design UI tests that verify RENDERED INTENT (the mockup), not DOM presence. Use before writing or reviewing an
TDD Implement
by jerseycheese - Implements Test-Driven Development by analyzing feature requirements, creating tests first (
Test Driven Development
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch
Money Model
Stress-test a money model (Mode 5) against Hormozi's CFA rule — 30-day cash, LTV:CAC, Four Prongs, sequence, d
TDD Cycle
Execute a comprehensive Test-Driven Development (TDD) workflow with strict red-green-refactor discipline:
TDD
by zscott - Guides development using Test-Driven Development principles, enforcing Red-Green-Refactor discipli
Related Agents
Red Quality Gate
Automated quality gate that runs after a failing test is written (RED) and before any implementation (GREEN).
Kevin
Write production code to make Toby's failing tests pass, following the approved plan. Use after tests exist an
Manual Rule Liveness Prober
Probes a manifest manual rule for liveness via with/without-rule fresh-subagent dispatch, capturing a RED→GREE