Skip to content

Carry the coding-agents shared rules in AGENTS.md - #87

Merged
slominskir merged 1 commit into
mainfrom
shared-rules-6.1.0
Oct 18, 2026
Merged

slominskir merged 1 commit into
mainfrom
shared-rules-6.1.0

Conversation

@slominskir-coding-agent

Copy link
Copy Markdown
Contributor

What changed

AGENTS.md now carries the coding-agents shared rules block, version 6.1.0, between its BEGIN/END markers, as epics2web does since JeffersonLab/epics2web#62. This is the one-time catch-up from the hand-made copy of the starter's generic rules to the versioned block, so later releases can replace the block as a whole. It brings in the rules this file lacked: task authorization, the Prepared-by: footer on agent-filed issues, the review conventions, rewording the first message, and commit trailers.

  • Development: unchanged, except for four lines the block now covers: the intro about reporting what you ran, "add or update tests with each change … never skip or weaken a test", "never use production data", and "never commit secrets". The characterization-test rule stays: when you change behavior on purpose, change the test that records it and say so.
  • Commit identity, Commits, Branches and pull requests: replaced by the block.
  • Project rules (after the block): the VERSION release rule, the organization project note, and the gh 2.46 note, as before. A GitHub note says that where the shared rules say merge request, read pull request, and for its pipeline, its checks (build, integration and CodeQL).

No deployment steps.

Checks

  • The text between the markers is identical to the block in coding-agents' v6.1.0 starter, and the sync script's marker check (block() in scripts/sync-shared-rules.py) parses the file: one block, version 6.1.0.
  • No Gradle checks run: Spotless covers only Java, and only AGENTS.md changed.

Decisions

  • 6.1.0, not 6.2.0: coding-agents' main has an unreleased 6.2.0 block; the projects get the latest release's.
  • Same layout as epics2web#62, which you merged: the stricter "add or update tests with each change" gives way to the shared rule, which asks for tests in proportion to the change's risk and for a fix's regression test to fail without it.

Part of acc/iac/docs/coding-agents#27 (https://code.jlab.org/acc/iac/docs/coding-agents/-/issues/27).

🤖 Generated with Claude Code

AGENTS.md held a hand-made copy of the starter's generic rules, from
before the starter had a versioned shared block, so it lacked the
rules added since: task authorization, the Prepared-by footer on
issues, the review conventions, and rewording the first message.
Replace those generic rules with the shared rules block of
coding-agents 6.1.0, between its markers, so later releases can
replace it as a whole.

Keep the project's own rules after it, under Project rules: the
VERSION release rule, the organization project note, which checks a
pull request waits for, and the gh 2.46 note. Add a line saying the
shared rules' merge requests and pipelines are pull requests and their
checks here. The Development section is unchanged except for the lines
the block now covers (report what you ran, add tests with each change,
never use production data, never commit secrets).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@slominskir
slominskir merged commit 2d9a9d9 into main Oct 18, 2026
7 checks passed
@slominskir
slominskir deleted the shared-rules-6.1.0 branch October 18, 2026 00:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

source::ai Work done by an AI agent

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant