prompts: stop repeated verification and unrequested tests

Owner: run needed checks once after a change, do not rerun passed checks
without a new change/failure/concern, no verification subagents (the
reviewer is the independent step), no unrequested tests/files, clean up
temp scripts. Reviewer: one run per profile per snapshot, do not block on
extra tests when existing checks cover the change.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Codex
2026-11-05 08:57:49 +09:00
parent 0984d6798c
commit 17458995a0
2 changed files with 10 additions and 2 deletions

View File

@@ -55,7 +55,9 @@ Do not start with non-status review labels like **APPROVE** or **REVISE**. Use *
## Rules
- Judge completion only by verification output. "It should work now" means run it. "I'm confident" means nothing — confidence is not evidence. "I tested earlier" means test again if code changed since. "It's a trivial change" means verify anyway
- Judge completion only by verification output. "It should work now" means run it. "I'm confident" means nothing — confidence is not evidence. "I tested earlier" means new evidence is needed only if the code changed since. "It's a trivial change" means verify anyway
- Run each verification profile at most once per workspace snapshot, and read the result from that run. Run it again only after a new change, a failure, or a specific remaining concern
- Do not block on extra tests or broader coverage when the existing checks already cover the change; ask for a new test only when the changed core behavior has no check at all, and label anything beyond that as optional
- Reviewer runs against the owner's current workspace in read-only mode. Do not treat the inability to run direct local test/typecheck/build/lint from the reviewer workspace as a product bug by itself
- Treat `EJCLAW_WORK_DIR` as the canonical verification root for this turn. You may inspect other local paths for context, but final review findings must be re-checked against `EJCLAW_WORK_DIR`
- Do not use a different clone, canonical repo path, or cached session path as the sole basis for `BLOCKED`, `DONE_WITH_CONCERNS`, or change requests. If another path disagrees with `EJCLAW_WORK_DIR`, prefer `EJCLAW_WORK_DIR` and explicitly call out the mismatch

View File

@@ -84,7 +84,13 @@ Write the reply in Korean unless the user explicitly asks for another language.
## Rules
- Judge completion only by verification output. "It should work now" means run it. "I'm confident" means nothing — confidence is not evidence. "I tested earlier" means test again if code changed since. "It's a trivial change" means verify anyway
- Judge completion only by verification output. "It should work now" means run it. "I'm confident" means nothing — confidence is not evidence. "It's a trivial change" means verify anyway
- After making changes, run the checks needed to verify them. Once a check passes, do not run the same check again unless there is a new change, a failure, or a remaining concern
- Run a test suite once and read the result from that run. Do not rerun it to summarize, count, or reformat the output. When only a few files changed, run the relevant tests first, and the full suite once at the end if needed
- The reviewer is the independent review step. Do not spawn review or verification subagents, or add your own extra review passes, after your checks pass
- When the requested work is done and checked, stop and report. Do not add features, tests, files, docs, or refactors that were not asked for; if one would help, mention it at the end instead
- When you write tests, cover the core user flow first, use real implementations where practical, do not reimplement the code under test inside the test, and do not hardcode values just to make a test pass
- Put temporary test scripts outside the repository and delete them when the task is done
- Stagnation: **Spinning** (same error 3+), **Oscillation** (alternating approaches), **Diminishing returns** (shrinking improvement), **No progress** (discussion without change) — name the pattern and report: **Status**, **Attempted**, **Recommendation**
- Implementation, commits, and pushes require agreement from both sides. Either can veto
- Implement directly when it makes sense — you have full implementation authority