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
+33 -13
View File
@@ -2,10 +2,11 @@
```prompt
Investigate the reported problem in input.md without editing. Read the relevant
code and logs, reproduce the failure with safe commands where possible, and find
the cause rather than the first symptom. Record the evidence, the smallest
credible fix, and anything you could not verify. Return blocked when the problem
cannot be reproduced or the needed evidence is unavailable.
code and logs (search first, then read file ranges, not whole logs), reproduce the
failure with the narrowest safe command, and find the cause rather than the first
symptom. Record the evidence, the smallest credible fix, and anything you could
not verify. Return blocked when the problem cannot be reproduced or the needed
evidence is unavailable.
```
```tools
@@ -15,6 +16,10 @@ grep
shell
```
```checks
none: read-only diagnosis; shell runs only the reproduction
```
```configs
provider=default
model=default
@@ -33,7 +38,8 @@ error -> #failure
```prompt
Fix the diagnosed cause with the smallest coherent change. Follow the
repository's conventions, preserve unrelated work, and add or update a regression
test that would fail before the fix. Run the relevant checks and report the exact
test that would fail before the fix. Run that test and other focused checks for
the touched code; the committer runs the full checks once. Report the exact
commands and actual results. Do not commit, push or deploy.
```
@@ -45,6 +51,10 @@ edit
shell
```
```checks
none: focused checks only; the committer runs the project's required checks once
```
```configs
provider=default
model=default
@@ -61,10 +71,10 @@ error -> #failure
# stage verify
```prompt
Independently verify the fix. Reproduce the original problem, run the relevant
checks, and inspect the changed files. Do not edit. Return success only when the
original failure is gone and the checks pass; otherwise return rejected with
concrete evidence.
Independently verify the fix. Re-run the original reproduction and the new
regression test, and read the diff (`git diff --stat` first). Do not run the full
suite and do not edit. Return success only when the original failure is gone;
otherwise return rejected with concrete evidence.
```
```tools
@@ -74,6 +84,10 @@ grep
shell
```
```checks
none: read-only verification; runs only the reproduction and regression test
```
```configs
provider=default
model=default
@@ -90,10 +104,12 @@ error -> #failure
# stage committer
```prompt
Commit this run's change locally. Inspect `git status` and the full diff; stage
only this run's work, never secrets or generated files. Run the relevant checks
and report the actual results. If nothing changed, say so rather than creating an
empty commit. Do not push, tag, deploy or rewrite history.
Commit this run's change locally. Inspect `git status` and `git diff --stat`,
then the staged diff; stage only this run's work, never secrets or generated
files. Run the project's required checks once with quiet or summary output and
report the commands and results; return blocked with the failing output when one
fails. If nothing changed, say so rather than creating an empty commit. Do not
push, tag, deploy or rewrite history.
```
```tools
@@ -103,6 +119,10 @@ grep
shell
```
```checks
none: generic starter has no project commands; with delivery=true list them here for the server to run
```
```configs
provider=default
model=default
+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
+28 -12
View File
@@ -33,8 +33,9 @@ error -> #failure
```prompt
Implement the plan from input.md. Follow the repository's conventions, keep the
change focused, and add or update tests where they matter. Preserve unrelated
work. Run the relevant checks and report the exact commands and actual results,
including what you could not test. Do not commit, push or deploy.
work. Run focused checks for the touched code only (quiet or summary output);
the committer runs the full checks once. Report the exact commands and actual
results, including what you could not test. Do not commit, push or deploy.
```
```tools
@@ -45,6 +46,10 @@ edit
shell
```
```checks
none: focused checks only; the committer runs the project's required checks once
```
```configs
provider=default
model=default
@@ -61,12 +66,13 @@ error -> #failure
# stage reviewer
```prompt
Independently review the actual change against the task and plan. Inspect the
diff and related code, and run the relevant checks yourself rather than trusting
an earlier summary. Look for correctness, duplication, unnecessary complexity and
missing tests. Report each blocking finding with a location, evidence and remedy;
keep advisory notes separate. Return success only when the applicable checks pass
and no substantive issue remains. Do not edit or commit.
Independently review the actual change against the task and plan. Start with
`git diff --stat`, then read the changed hunks and only the related code you
need. Do not run test suites; judge the implementer's reported checks and name
any missing coverage. Look for correctness, duplication, unnecessary complexity
and missing tests. Report each blocking finding with a location, evidence and
remedy; keep advisory notes separate. Return success only when no substantive
issue remains. Do not edit or commit.
```
```tools
@@ -78,6 +84,10 @@ websearch
webfetch
```
```checks
none: read-only review; shell is used only for git diff
```
```configs
provider=default
model=default
@@ -94,10 +104,12 @@ error -> #failure
# stage committer
```prompt
Commit this run's change locally. Inspect `git status` and the full diff; stage
only this run's work, never secrets or generated files. Run the relevant checks
and report the actual results. If nothing changed, say so rather than creating an
empty commit. Do not push, tag, deploy or rewrite history.
Commit this run's change locally. Inspect `git status` and `git diff --stat`,
then the staged diff; stage only this run's work, never secrets or generated
files. Run the project's required checks once with quiet or summary output and
report the commands and results; return blocked with the failing output when one
fails. If nothing changed, say so rather than creating an empty commit. Do not
push, tag, deploy or rewrite history.
```
```tools
@@ -107,6 +119,10 @@ grep
shell
```
```checks
none: generic starter has no project commands; with delivery=true list them here for the server to run
```
```configs
provider=default
model=default