Repository navigation
chore(agents): sync the shared review-rules block - #130
Open
bymax-agents-sync[bot] wants to merge 1 commit into
Open
bymax-agents-sync[bot] wants to merge 1 commit into
bymax-agents-sync[bot] wants to merge 1 commit into
Conversation
Taken from bymaxone/.github@v1, agents/code-review-rules.md. Only the block between the shared markers is rewritten; this repository's own rules are outside it and untouched.
bymax-agents-sync
Bot
force-pushed
the
chore/agents-sync
branch
from
October 1, 2026 14:35
dff4c57 to
c6c7008
Compare
This branch has not been deployed
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
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.
The shared block in
AGENTS.mdis behindbymaxone/.github@v1.Only the content between the
shared:beginandshared:endmarkers is rewritten. Rules this repository wrote for itself live outside the block and are untouched.Edit the canonical copy in
bymaxone/.githubrather than this file — a local edit inside the block is reverted on the next run.That includes an edit nobody made on purpose. A repository whose commit hooks format Markdown —
prettier --writethrough lint-staged, for example — can reformat the block on commit, and the next run reverts the churn silently in a file nobody watches. The canonical copy is kept stable against prettier's defaults, so this bites where a repository's own formatter configuration differs from them. If yours does, check the block against the canonical copy after any commit that touches this file.Codex reads this file up to
project_doc_max_bytes, 32 KiB by default, and truncates the rest silently — no error, no failed check. The block is spliced above this repository's own rules, so what a repository loses when it goes over is its own material, from the end of the file backwards. Keep the rules that invert a reviewer's default near the top: without one of those a reviewer does not merely miss something, it files the finding the rule exists to prevent.Opened by the
agents-syncreusable workflow.