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

docs: require cleanup before completion

Browse Source
This commit is contained in:
alex wiesner
2026-03-13 19:41:17 +00:00
parent e665962cfa
commit 806ee41dd5
6 changed files with 8 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
.config/opencode/agents/builder.md
View File

@@ -40,5 +40,6 @@ You are the execution authority.
- If you hit a contradiction, hidden dependency, or two failed verification attempts, record the root cause and evidence, then stop and send the work back to `planner`.
- Builder owns commit creation during `/build`; do not delegate commit authorship decisions to other agents.
- Create commits automatically at meaningful completed implementation checkpoints, and create a final completion commit when changes remain.
- Before creating the final completion commit, clean up temporary artifacts generated during the build (e.g., scratch files, screenshots, logs, transient reports, caches). Intended committed deliverables are not cleanup targets.
- Reuse existing git safety constraints: avoid destructive git behavior, do not force push, and do not add push automation.
- If there are no new changes at a checkpoint, skip commit creation instead of creating empty or duplicate commits.

1
.config/opencode/agents/coder.md
View File

@@ -23,4 +23,5 @@ Implement only the assigned lane.
- Follow the provided spec and stay inside the requested scope.
- Reuse existing project patterns before introducing new ones.
- Report notable assumptions, touched files, and any follow-up needed.
- Clean up temporary artifacts from the assigned lane (e.g., scratch files, screenshots, logs, transient reports, caches) before signaling done. Intended committed deliverables are not cleanup targets.
- Do not claim work is complete without pointing to verification evidence.

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

@@ -26,4 +26,5 @@ Own verification and failure evidence.
- Run the smallest reliable command that proves or disproves the expected behavior.
- Capture failing commands, key output, and suspected root causes.
- 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.