← ClaudeAtlas

pr-bodylisted

Write a pull-request body and score it before the PR is opened, or audit an existing PR's body against the same rubric. Use when about to run gh pr create, when a PR body needs writing or rewriting, or when asked whether a PR description is any good. Invoked as /pr-body write <body-file> or /pr-body audit <pr>.
ConnorGriffin/skills · ★ 20 · AI & Automation · score 66
Install: claude install-skill ConnorGriffin/skills
# PR body The body is for whoever merges the change. It carries facts about the change in the system's own terms. The diff already carries the files. ## The gold standard This is the target. Copy its shape, not its subject. The whole thing is what you would say to the team in one sentence, plus the handful of facts a merger cannot get from the title. The decisions, the alternatives, and the operator log are in the diff and the spec, and the body says where they are rather than repeating them. ```markdown ## Motivation and Context ghes-config now sets the memory ceilings and rate-limit posture that production already runs: 17 keys per ring for prd and stg, read off the production primary, rate limiting off. Staging had sandbox-sized ceilings on production-sized hardware. * The 14 rate-limit keys are new to the reconciler's allowlist, on the `ghe-config` transport. dev.yaml is unchanged. * Staging's primary was brought to those values by hand. Three of the four keys written did not exist there before, so the comparison below shows staging carrying production's values, not the appliance honouring the new ceilings. * No reconciler instance exists in any ring, so nothing reads these files today. Decisions and the operator log are in the change folder under `openspec/changes/archive/`. Fixes PROJ-7351 ## How Has This Been Tested? * Production primary against staging primary after the apply: 17 lines per side, diff exit 0. Replication in sync on both replicas. * `parity_t