القائمة
Use when a test suite is flaky, shallow, or easy to bypass and you need stronger coverage around critical behavior, failure modes, and regression boundaries.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use the Codex Kit CLI to initialize, update, or inspect a Codex-ready project scaffold in the current workspace.
Use when a change may affect rollout, deployment, migrations, or operational stability and needs a higher-confidence validation pass.
Review patches, branches, or implementations for correctness, regressions, security, and missing tests. Use when the task is to inspect a diff or code change and identify concrete risks before merge.
Reproduce, isolate, and explain bugs before fixing them. Use when the task is about a bug, regression, failure, flaky behavior, unexpected output, or unclear runtime behavior that must be narrowed to a concrete cause.
Produce implementation plans that are decision-complete and execution-ready. Use when the task needs decomposition, sequencing, acceptance criteria, explicit assumptions, risk handling, or a concrete plan before coding or operational work starts.
Use when a bug is real but poorly scoped and you need a disciplined pass to reproduce it, bound it, and isolate the most likely root cause before fixing.
| name | test-hardening |
| description | Use when a test suite is flaky, shallow, or easy to bypass and you need stronger coverage around critical behavior, failure modes, and regression boundaries. |
Strengthen trust in the system by improving the tests that matter most, not by maximizing test count.
| File | Purpose | Read When |
|---|---|---|
verify.md | decide whether the new tests truly prove behavior | after authoring or tightening tests |
Summarize:
.agents/workflows/test.md or .agents/workflows/verify.mdtest_writertesting-patterns, tdd-workflow, webapp-testingdebugger when the expected behavior is still not well understood