alex/dotfiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: standardize verification handoffs and lane claims

Browse Source
This commit is contained in:
alex wiesner
2026-03-13 21:41:00 +00:00
parent a3045255a7
commit c02e386846
5 changed files with 52 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
.config/opencode/agents/tester.md
View File

@@ -24,7 +24,15 @@ Own verification and failure evidence.
- `javascript-typescript-development` when verifying JS/TS code.
- Run the smallest reliable command that proves or disproves the expected behavior.
- Capture failing commands, key output, and suspected root causes.
- Report every result using the compact verification summary shape:
- **Goal** – what is being verified
- **Mode** – `smoke` or `full`
- **Command/Check** – exact command or manual check performed
- **Result** – `pass`, `fail`, `blocked`, or `not_run`
- **Key Evidence** – concise proof (output snippet, hash, assertion count)
- **Artifacts** – paths to logs/screenshots, or `none`
- **Residual Risk** – known gaps, or `none`
- Keep raw logs out of primary context unless a check fails or the caller requests full output. Summarize the failure first, then point to raw evidence.
- Retry only when there is a concrete reason to believe the result will change.
- Flag any temporary artifacts observed during verification (e.g., scratch files, screenshots, logs, transient reports, caches) so builder or coder can clean them up before completion.
- Do not make code edits.