An agent whose work is confined to one package may now run go test directly on that package's suite, or on individual tests in it, while iterating. go build, go vet and the linter still go through make targets. The full make check is still required before every push. The Makefile and its templates gain nothing.
The root REPO_POLICIES.md is a symlink to prompts/REPO_POLICIES.md, so one edit keeps the two identical.
Disclosures
Judgement call: "Linting and testing run in Docker" read as false beside the new paragraph, so it now says "The lint and test gates run in Docker". What the rule requires of the gates is unchanged.
Judgement call: the new paragraph adds that a run while iterating is not a gate, so a newcomer can tell the two apart. The brief did not list that clause.
Not covered: the global conventions and the worker instructions, both kept outside this repository, still forbid a direct go test. Agents that follow them will not use this exception until they change.
Model: opus-5-5
Builds sneak's ruling at https://git.eeqj.de/sneak/prompts/issues/51#issuecomment-167600, for https://git.eeqj.de/sneak/prompts/issues/51.
An agent whose work is confined to one package may now run `go test` directly on that package's suite, or on individual tests in it, while iterating. `go build`, `go vet` and the linter still go through make targets. The full `make check` is still required before every push. The `Makefile` and its templates gain nothing.
The root `REPO_POLICIES.md` is a symlink to `prompts/REPO_POLICIES.md`, so one edit keeps the two identical.
## Disclosures
- Judgement call: "Linting and testing run in Docker" read as false beside the new paragraph, so it now says "The lint and test gates run in Docker". What the rule requires of the gates is unchanged.
- Judgement call: the new paragraph adds that a run while iterating is not a gate, so a newcomer can tell the two apart. The brief did not list that clause.
- Not covered: the global conventions and the worker instructions, both kept outside this repository, still forbid a direct `go test`. Agents that follow them will not use this exception until they change.
Model: opus-5-5
Follows sneak's ruling at
#51 (comment). An agent
whose work is confined to one package may run `go test` directly on that
package's suite, or on individual tests in it, while iterating. `go build`,
`go vet` and the linter still go through make targets. The full `make check`
is still required before every push. The `Makefile` gains nothing.
The rule on Docker now says the lint and test gates run there, because a run
while iterating is not a gate.
Model: opus-5-5
PASS: this change says what the ruling at #51 (comment) says and no more, and its changed sentences hold against the rest of the policy.
Judgement call: I read "the only exception to this rule" as covering whoever runs a repo's operations, not a Dockerfile phase, which is what a make target itself runs.
Model: opus-5-5
PASS: this change says what the ruling at https://git.eeqj.de/sneak/prompts/issues/51#issuecomment-167600 says and no more, and its changed sentences hold against the rest of the policy.
Judgement call: I read "the only exception to this rule" as covering whoever runs a repo's operations, not a `Dockerfile` phase, which is what a make target itself runs.
Model: opus-5-5
clawbot
merged commit 3066aae835 into next2026-11-04 19:32:38 +01:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Builds sneak's ruling at #51 (comment), for #51.
An agent whose work is confined to one package may now run
go testdirectly on that package's suite, or on individual tests in it, while iterating.go build,go vetand the linter still go through make targets. The fullmake checkis still required before every push. TheMakefileand its templates gain nothing.The root
REPO_POLICIES.mdis a symlink toprompts/REPO_POLICIES.md, so one edit keeps the two identical.Disclosures
go test. Agents that follow them will not use this exception until they change.Model: opus-5-5
PASS: this change says what the ruling at #51 (comment) says and no more, and its changed sentences hold against the rest of the policy.
Judgement call: I read "the only exception to this rule" as covering whoever runs a repo's operations, not a
Dockerfilephase, which is what a make target itself runs.Model: opus-5-5