القائمة
Use before writing or changing any production code — features, bug fixes, refactors — and whenever the router announces the tdd-fast-path. Invoke via route or explicit command.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | tdd |
| description | Use before writing or changing any production code — features, bug fixes, refactors — and whenever the router announces the tdd-fast-path. Invoke via route or explicit command. |
NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST.
This is a hard rule, not a preference. If you are about to write or edit production code and no failing test exists for that change yet, stop and write the test first.
EV [<task> RED] <test cmd> → FAIL (<expected failure>).EV [<task> GREEN] <test cmd> → PASS.feat/fix/refactor/test), never mixed. Refactor commits
made at the wave gate are separate commits, never folded into this one.Refactoring is not a loop step. It happens once, at the wave gate, as a pass across the whole task's tests — not inside this loop.
A seam is a declared boundary where a test may substitute a fake or mock for a real dependency. Seams come from the plan. If the plan does not declare a seam for what you're testing, stop and ask — don't invent one.
If production code was written before a test for it exists: delete it. Don't keep it as reference, don't adapt it — delete means delete. Then restart the loop with a failing test first.
| Tell | Why it's empty |
|---|---|
| Asserting the mock | Checks that a mock was called, not that real behavior occurred — passes even if the real logic is deleted |
| Asserting the implementation | Restates the code's internals instead of checking an observable outcome |
| Snapshot without intent | Records that something changed, not whether the change is correct |
A mock is allowed only at a named seam, with a stated reason (why the real dependency can't run here — for example, a network call, a non-deterministic clock, cost). No named seam, no mock: use the real dependency, or the test double the plan provides.
In the loop: run the type checker and the one focused test for the file you're changing. Do not run the full suite here. Run the full suite at wave gates and before any completion claim.
When route dispatches straight into this skill (announced as tdd-fast-path), the
loop and the Iron Law above still apply in full. Fast path skips routing ceremony, not
test-first discipline.
| Thought | Reality |
|---|---|
| "Too simple to test" | Simple things break; the test is fast — write it |
| "I'll verify at the end" | Stale evidence is not evidence; verify now |
| "The fix is obvious, skip root cause" | Symptom fixes recur; find the cause |
| "The test is hard to write" | Hard test = design feedback; check the seam |
Go, table-driven with testify:
func TestParseAmount(t *testing.T) {
tests := []struct {
name string
input string
want int64
wantErr bool
}{
{"valid rupiah", "Rp10.000", 10000, false},
{"empty string", "", 0, true},
}
for _, tt := range tests {
t.Run(tt.name, func(t *testing.T) {
got, err := ParseAmount(tt.input)
if tt.wantErr {
require.Error(t, err)
return
}
require.NoError(t, err)
assert.Equal(t, tt.want, got)
})
}
}
TypeScript, vitest:
import { describe, it, expect } from "vitest";
describe("parseAmount", () => {
it("parses a rupiah string", () => {
expect(parseAmount("Rp10.000")).toBe(10000);
});
it("rejects an empty string", () => {
expect(() => parseAmount("")).toThrow();
});
});
For TypeScript work, load references/ts-conventions.md before writing test doubles or
parsing at a boundary.
Use once a spec is approved and ready to become an executable task list — turns spec requirements into a wave-based plan of write-scoped, testable tasks that waves can dispatch. Invoke via route or explicit command.
Use when a plan already exists and is ready to run — dispatches each wave's tasks, reviews every return before trusting it, and gates advancement on evidence. Invoke via route or explicit command.
Use when writing a new galdr skill, editing an existing one, or running the pack's quarterly prune review.
Continuation protocol for resuming work after a break, handing off to another session, a subagent, or Codex, and parking fast under a usage limit. Invoke via route or explicit command.
Use once per repo to create or refresh docs/agents/galdr.md — the config verify, waves, review, branches, and route read for gate commands, invariants, models, and smoke details. Slash-command only, not router- or model-invoked.
Use when the user runs /galdr:core to install, uninstall, or check galdr's core rules block on this machine for Claude, Codex, or Antigravity. Run install once per agent to write the marked block into that agent's rules file (or the Claude enabled flag); uninstall to remove it; status to report state without writing.