Test

---
name: test
description: Run behavioral tests (unit, integration, regression) and produce a test report. Tests must pass before PR creation. Invoke automatically after /verify completes.
---
Run tests and write a report to `docs/reports/`.

## Preferred flow

1. Read the active plan and its test plan section.
2. Run `./scripts/run-test.sh` (tests only, changed-language scope by default) unless there is a stronger project-specific test runner.
3. Capture test results, coverage, and failure analysis in a report from [template.md](template.md).
4. Save raw test output to `docs/evidence/test-<date>-<slug>.log`.
5. If no tests exist or test infrastructure is missing, say so explicitly and propose the smallest useful test to add.
6. Distinguish:
   - passing
   - failing (with root cause analysis)
   - skipped (with reason)

## Test categories

- **Normal path**: Expected inputs produce expected outputs
- **Error path**: Invalid inputs, missing dependencies, boundary conditions
- **Regression**: Previously broken behavior stays fixed

## Gate

**Tests must pass before PR creation.** If any test fails:
- Record the failure in the report
- Do NOT proceed to /pr
- Propose a fix or flag the failure for human decision

## What /test does NOT do

- **Static analysis**: That is the responsibility of `/verify`.
- **Diff quality**: That is the responsibility of `/self-review`.
- **Spec compliance**: That is the responsibility of `/verify`.

## Output

- `docs/reports/test-<date>-<slug>.md` — human-readable summary
- `docs/evidence/test-<date>-<slug>.log` — raw test output
- clear pass/fail verdict
- explicit test gaps

## Insight event (best-effort)

After writing the report, append one insight event (errors are non-fatal):
```
./scripts/insights-append.sh --slug <slug> --flow standard --phase test \
  --verdict <pass|fail> --cycle auto --source skill || true
```
`--cycle auto` reads the pipeline cycle from `.harness/state/standard-pipeline/` and falls back to 1.

## CLI execution modes

This skill runs under both Claude Code and Codex. The execution mode follows
the conventions in AGENTS.md and `.codex/AGENTS.override.md`.

| Aspect | Claude Code | Codex |
|--------|-------------|-------|
| Skill invocation | `/skill-name` slash command | `$skill-name` mention or the `/skills` menu (avoid the `/skill-name` form — it collides with built-ins) |
| Skill body path | `.claude/skills/<name>/SKILL.md` | `.agents/skills/<name>/SKILL.md` |
| Subagent mechanism | `Task(subagent_type=...)` when a policy delegates | `.codex/agents/` custom agents when a policy delegates |
| Structured prompts | `AskUserQuestion` | Numbered options printed to stdout, awaiting a digit reply |
| Artifacts | `docs/reports/`, `docs/plans/`, `docs/specs/` (shared) | Same (CLI-agnostic) |

The drift check (`./scripts/check-skill-sync.sh`) cross-checks both bodies and
invocation metadata — editing only one side will fail CI.