The Fable rewrite of webhooker's prose found that REPO_POLICIES.md fails the
sentence rules too: long sentences and comma-chained lists
(sneak/webhooker#558 (comment)). Every repo
carries a copy kept in sync from this repo, so it was left alone there; a
rewrite belongs here, at the source. The rules are on sneak/project-management#39 (comment).
Question. Should Fable rewrite REPO_POLICIES.md here, sentence by
sentence, keeping every rule's meaning?
Recommendation. Yes, as one PR that you read before it merges, since the
wording of policy is yours. It waits for a worker account, after the restart.
Model: opus-5-5
The Fable rewrite of webhooker's prose found that `REPO_POLICIES.md` fails the
sentence rules too: long sentences and comma-chained lists
(https://git.eeqj.de/sneak/webhooker/issues/558#issuecomment-154601). Every repo
carries a copy kept in sync from this repo, so it was left alone there; a
rewrite belongs here, at the source. The rules are on
https://git.eeqj.de/sneak/project-management/issues/39#issuecomment-154280.
**Question.** Should Fable rewrite `REPO_POLICIES.md` here, sentence by
sentence, keeping every rule's meaning?
**Recommendation.** Yes, as one PR that you read before it merges, since the
wording of policy is yours. It waits for a worker account, after the restart.
Model: opus-5-5
sneak
was assigned by clawbot2026-10-25 03:36:24 +01:00
yes. also update the go linter config for 2.x and check its syntax and that its configured items are doing what we intend them to (i understand a few are not)
yes. also update the go linter config for 2.x and check its syntax and that its configured items are doing what we intend them to (i understand a few are not)
Implementer's brief for the rewrite of prompts/REPO_POLICIES.md:
One PR, written on Fable. When its review passes it is labelled merge-ready and assigned to sneak, who reads it before it merges. It does not merge on a passed review.
It keeps every rule's meaning. No rule is added, removed, loosened or tightened, and "must" stays "must" and "should" stays "should".
Sentence by sentence, against sneak/project-management#39 (comment): one idea per sentence, about 30 words at most, a list is a bulleted list, subject and verb early, the common name for a thing, the main rule before any exception.
Rules stay in their present order, so the PR can be read beside the old text. A long item may become a short lead sentence and sub-bullets.
Code blocks, digests, URLs, file names and commands stay byte-identical.
A sentence that is false or contradicts another stays true to what it says now and goes in a list on the PR, for sneak. The rewrite changes no rule to fix it.
Model: opus-5-5
Taken, per sneak's yes at https://git.eeqj.de/sneak/prompts/issues/136#issuecomment-165193. His linter order is at https://git.eeqj.de/sneak/prompts/issues/142.
Implementer's brief for the rewrite of `prompts/REPO_POLICIES.md`:
- One PR, written on Fable. When its review passes it is labelled `merge-ready` and assigned to sneak, who reads it before it merges. It does not merge on a passed review.
- It keeps every rule's meaning. No rule is added, removed, loosened or tightened, and "must" stays "must" and "should" stays "should".
- Sentence by sentence, against https://git.eeqj.de/sneak/project-management/issues/39#issuecomment-154280: one idea per sentence, about 30 words at most, a list is a bulleted list, subject and verb early, the common name for a thing, the main rule before any exception.
- Rules stay in their present order, so the PR can be read beside the old text. A long item may become a short lead sentence and sub-bullets.
- Code blocks, digests, URLs, file names and commands stay byte-identical.
- A sentence that is false or contradicts another stays true to what it says now and goes in a list on the PR, for sneak. The rewrite changes no rule to fix it.
Model: opus-5-5
sneak
was unassigned by clawbot2026-11-04 00:29:17 +01:00
clawbot
self-assigned this 2026-11-04 00:29:17 +01:00
Rewrote prompts/REPO_POLICIES.md sentence by sentence in #147, keeping every rule's meaning and order. The PR body lists, for sneak, the sentences that look false or contradict another rule. Both repo checklists carry the same rewrite of the paragraph they quote word for word.
Model: fable-5-1
Rewrote `prompts/REPO_POLICIES.md` sentence by sentence in https://git.eeqj.de/sneak/prompts/pulls/147, keeping every rule's meaning and order. The PR body lists, for sneak, the sentences that look false or contradict another rule. Both repo checklists carry the same rewrite of the paragraph they quote word for word.
Model: fable-5-1
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.
The Fable rewrite of webhooker's prose found that
REPO_POLICIES.mdfails thesentence rules too: long sentences and comma-chained lists
(sneak/webhooker#558 (comment)). Every repo
carries a copy kept in sync from this repo, so it was left alone there; a
rewrite belongs here, at the source. The rules are on
sneak/project-management#39 (comment).
Question. Should Fable rewrite
REPO_POLICIES.mdhere, sentence bysentence, keeping every rule's meaning?
Recommendation. Yes, as one PR that you read before it merges, since the
wording of policy is yours. It waits for a worker account, after the restart.
Model: opus-5-5
yes. also update the go linter config for 2.x and check its syntax and that its configured items are doing what we intend them to (i understand a few are not)
Taken, per sneak's yes at #136 (comment). His linter order is at #142.
Implementer's brief for the rewrite of
prompts/REPO_POLICIES.md:merge-readyand assigned to sneak, who reads it before it merges. It does not merge on a passed review.Model: opus-5-5
Rewrote
prompts/REPO_POLICIES.mdsentence by sentence in #147, keeping every rule's meaning and order. The PR body lists, for sneak, the sentences that look false or contradict another rule. Both repo checklists carry the same rewrite of the paragraph they quote word for word.Model: fable-5-1