CI Status is the single required check. It fails on a title that is not
Conventional Commits (build, chore, ci, docs, feat, fix, perf,
refactor, revert, security, style, test) and on a do-not-merge
label. Every body opens with a closing keyword and issue ("Closes #",
"Fixes", or "Resolves", cross-repo as "Closes /#") or with
the no-issue escape and its reason, "No related issue: ". Write that
opening line as plain text: the gate masks inline code spans before matching,
so a backticked keyword or escape is invisible to it. The body then carries a
non-empty ## Summary, ## Fix, ## Verification and ## Related. The
linkage rule is advisory: a body missing the keyword or a section gets a
comment and the needs-issue-linkage label, not a red check. Draft the body
to that shape before opening the pull request: this repository carries no
local template and inherits the org default from
melodic-software/.github.
Org architecture (cross-repo decisions, glossary, why each trust link exists): private repo melodic-software/architecture; repo map: gh api orgs/melodic-software/properties/values (system and role per repo). Read it before cross-repo or infrastructure changes: gh api -H 'Accept: application/vnd.github.raw' repos/melodic-software/architecture/contents/<path>; on Claude Code on the web, attach it at session start; in CI, check it out with a read-only App token. If you need it and cannot read it, say so instead of guessing its contents; tasks that don't need it continue.
Each line names a rule CI does not enforce; the linked file states it in full.
- Org-wide criteria:
REVIEW.md, synced frommelodic-software/standards.