← ClaudeAtlas

presslisted

Harden the test surface after `/cook` — map changed behavior to tests, find weak assertions and missing boundaries, and add focused hardening tests. Use when the user wants the tests strengthened before review or shipping — phrases like "press the changes", "harden this", "check coverage", "strengthen the tests", "are the tests good enough", "press before /age", "/press". Use even when the user wants to "tighten things up" before review. Do NOT use to add broad new behavior — only corrective fixes that hardening tests force.
paulnsorensen/easy-cheese · ★ 12 · Code & Development · score 75
Install: claude install-skill paulnsorensen/easy-cheese
# /press Press may add or strengthen tests and make tiny corrective fixes only when a test exposes a clear defect in the cooked scope. ## --hard propagation `/press --hard` (propagated from `/cook --hard`) is pass-through only. Press runs no gate. Hand `--hard` forward to `/age` at the handoff so it eventually reaches `/cure`, which is the only pipeline skill that fires the metacognitive vibecheck. See `skills/hard-cheese/SKILL.md`. ## Baseline-aware gates When the cooked diff's handoff slug carries a recorded `baseline:` block, press re-runs the project's gates but does not re-flag or re-halt on failures identical to that baseline (same test, same signature) — only new or changed failures affect readiness. See [`../cook/references/quality-gates.md`](../cook/references/quality-gates.md) for the classification and policy. ## Flow 1. **Read** — load the spec or acceptance criteria and the cooked diff. If `.cheese/glossary/<slug>.md` exists, read it for naming consistency when hardening tests. 2. **Map** — for each changed behaviour, find the test(s) that cover it through semantic caller search. 3. **Gap analysis** — identify weak assertions, missing boundaries, and uncovered integration seams. See `references/gap-analysis.md` for what counts as a gap and the priority order. 4. **Add focused tests** — observe red first when behaviour changes. Apply precise stale-safe edits. 5. **Corrective fixes** — only for defects the hardening tests expose. No new behaviour. 6. **Run c