Authoring lint: required checks, undeclared outcomes, delivery claims, loop limits, silent guards, boilerplate

This commit is contained in:
2026-11-04 13:04:11 +00:00
parent fa6c0864db
commit 37e941bbba
16 changed files with 745 additions and 44 deletions
+19 -11
View File
@@ -1,13 +1,13 @@
# stage worker
```prompt
Make the small code change requested in input.md. Inspect the project first and follow its
conventions. Keep the change focused, preserve unrelated work, and run the
relevant checks. Report what changed, the exact checks you ran, and anything you
could not verify. Do not commit, push or deploy.
Make the small code change requested in input.md. Inspect only the files the
change needs and follow the project's conventions. Keep the change focused and
preserve unrelated work. Run focused checks for the touched code (one package or
test file, quiet or summary output), not the whole suite. Report what changed, the
exact checks you ran, and anything you could not verify. Do not commit, push or deploy.
Do not run destructive commands, install dependencies or change external services.
If the scope or required access is missing, return blocked with the missing input.
Return a concise Markdown change summary with paths and verification evidence.
```
```tools
@@ -18,6 +18,10 @@ edit
shell
```
```checks
none: starter leaves the change uncommitted; the worker runs focused checks and the user runs the project suite
```
```configs
provider=default
model=default
@@ -35,12 +39,12 @@ error -> #failure
```prompt
Independently review the actual changed files and full diff against the request
and project conventions, not just the worker's summary. Check correctness,
regressions, test coverage and unrelated changes. Inspect status and diffs and
run relevant existing project checks when safe; never install dependencies or
modify source, commit, push or deploy. Return a concise Markdown review with
findings, paths, verification evidence and any unverified behavior. Return blocked
if there are material findings or insufficient evidence to approve the change.
and project conventions, not just the worker's summary. Start with `git status`
and `git diff --stat`, then read the changed hunks and only the surrounding code
you need. Check correctness, regressions, test coverage and unrelated changes. Do
not run test suites or modify files; rely on the worker's reported checks and name
any gap. Report findings with paths and evidence. Return blocked if there are
material findings or insufficient evidence to approve the change.
```
```tools
@@ -50,6 +54,10 @@ grep
shell
```
```checks
none: read-only review; shell is used only for git status and diff
```
```configs
provider=default
model=default