Take the shared instruction blocks - #97
Merged
Merged
Conversation
sehkone
force-pushed
the
sehkone/instructions-onboarding
branch
from
August 11, 2026 09:59
1e3cba1 to
42ca547
Compare
This repository kept its own copy of rules that ten others also kept, in wording that had already drifted from theirs, and a CLAUDE.md that was a second copy of the same text again. Both are now generated: the marked regions in AGENTS.md come from aicers/agent-instructions at the release the pin file names, and CLAUDE.md imports AGENTS.md rather than restating it. Which blocks this repository takes is decided upstream in repos.json. Everything they cover is gone from the hand-written text; what stays below them is what only this repository knows. Two workflow jobs come with it. The drift check fails if a generated region here stops matching the release the pin names, and the weekly apply proposes the next release as a pull request. Neither takes an input or a secret; both read `.agents/instructions.toml`.
sehkone
force-pushed
the
sehkone/instructions-onboarding
branch
from
August 11, 2026 11:07
42ca547 to
377e24b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Onboards this repository to
aicers/agent-instructions, at release 0.2.1.Blocks it takes, decided upstream in
repos.json: workflow, agentcoop, rust, changelog.What moved
AGENTS.mdkept hand-written copies of rules ten other repositories also kept, in wording that had already drifted from theirs. Those sections are now generated regions between markers.CLAUDE.mdwas a second copy of the same text; it becomes the two-line import, so both tools read one file instead of two that can disagree.What stays hand-written is the CI requirements. The shared Rust rules require the repository-specific section to name the exact clippy and rustfmt invocations, so that section now names the ones this CI actually runs.
What comes with it
.agents/instructions.toml— the release this copy came from and the blocks it carries. The drift check and the apply both read it; neither takes an input.ci.ymlgains anInstructionsjob that fails if a generated region here stops matching that release.update-instructions.ymlproposes each new release as a pull request, weekly. It runs on the defaultGITHUB_TOKENand needs no secret.Do not edit the marked regions
Change the wording upstream in
aicers/agent-instructionsand cut a release; the apply job then brings it here. Editing a region in this repository turns the drift check red.