Skip to content

chore: add verification hierarchy guidance #238

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
marcusquinn merged 2 commits into from
Jan 27, 2026
Merged

chore: add verification hierarchy guidance #238

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d68855a
chore: add verification hierarchy guidance to system prompt and Build+
marcusquinn Jan 27, 2026
8583b62
chore: align build.txt verification summary with full hierarchy
marcusquinn Jan 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions .agent/build-plus.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -222,6 +222,12 @@ See `tools/opencode/opencode.md` for CLI testing patterns.
- After tests pass, think about the original intent
- Write additional tests to ensure correctness
- Remember there may be hidden tests that must also pass
- **Verification hierarchy** -- always find a way to confirm your work:
1. Run available tools (tests, linters, type checkers, build commands)
2. Use browser tools to visually verify UI changes
3. Check primary sources (official docs, API responses, `git log`)
4. Review the output yourself and provide user experience commentary
5. If none of the above give confidence, ask the user how to verify

## Planning Workflow (Deliberation Mode)

Expand Down
1 change: 1 addition & 0 deletions .agent/prompts/build.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,3 +105,4 @@ These apply to all models but reinforce behaviours some need more than others:
- Do not add code comments unless asked. Focus on why, not what.
- After code changes, run lint/typecheck commands if available (check README or configs).
- When making changes, read surrounding context first to ensure idiomatic integration.
- Always verify your work. Hierarchy: 1. Tools (tests, lint, typecheck, build). 2. Browser for UI. 3. Primary sources (docs, APIs, git log). 4. Self-review with commentary. 5. Ask user how to verify.