Menu
Select the narrowest deterministic validation for a change by its blast radius. Use when choosing tests, checks, CI gates, or manual validation before claiming work is done.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when changing what a running devloop harness serves — pointing it at a different directory or worktree, or making the live harness serve newer or different code (a newer commit, another branch, or in-progress edits) without a wasteful restart.
Use when verifying that a UI change works end to end by driving the running app in a real browser — confirming a fix, reproducing a reported UI symptom, or proving a wizard/form/flow behaves — with Playwright against the exact code under review.
Enforce a Roborev plus Kata development workflow for code changes. Use when Codex is asked to implement, fix, refactor, or review work tracked by Kata and Roborev, especially when branch discipline, non-blocking review jobs, validation gates, SemVer, changelog checks, and final delivery reporting matter.
Use when working on GitHub pull requests that need PR-ready validation, review-thread replies, reviewer mentions, linked external references, or merge readiness checks.
Create or review a standalone repository that publishes a set of Codex or Claude skills with shared validation, linking, eval, and agent metadata conventions.
Prepare small, reviewable local commits with explicit rationale, SemVer impact, task hygiene, branch cleanup expectations, and clear commit commentary. Use when asked to commit work, prepare a PR-ready change, decide version impact, write commit messages, or clean up merged feature branches.
| name | testing |
| description | Select the narrowest deterministic validation for a change by its blast radius. Use when choosing tests, checks, CI gates, or manual validation before claiming work is done. |
Validate the impacted blast radius, not the whole repository by default.
Choose the smallest deterministic check that would fail if the change is wrong:
concentric expansion to parent systems that consume that API.When focused checks have known names, report those exact commands or test names.
If no deterministic check exists, add a focused test when practical. Otherwise report the static or manual check used and the residual risk.
Do not run a broad validation suite merely because it exists. Reject that as over-broad. Report which broader checks were skipped and why they are outside the blast radius.
When reporting validation scope, always use these exact labels as plain text:
Blast radius: name the changed surface and say when it is docs-only.Required checks: name the exact focused checks. For API contracts, include Concentric expansion: direct API contract test -> parent consumer test.Skipped broad checks: name skipped suites and why.For API or contract changes, the Required checks: line must include the exact phrase Concentric expansion: and show the path from the direct contract test to the parent consumer test.