ref(pr-writer): Rebuild the guidance around the cover note - #164
Draft
sergical wants to merge 1 commit into
Draft
Conversation
The skill named its leading concept once, in a negation ("a cover note, not
a changelog, template, validation log, or file-by-file summary"), then never
used it again — and Boundaries went on to prohibit those same four things a
second time. Leaning on the word instead retires the restatements.
Also fixes a bug the examples were teaching: both sample bodies were
hard-wrapped at ~76 columns, and GitHub renders an intra-paragraph newline as
a line break, so following them produced PR bodies that broke raggedly at the
source column instead of the reader's window width.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
sergical
force-pushed
the
ref/pr-writer-cover-note
branch
from
July 27, 2026 23:23
bb2b5ed to
c2783e8
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.
PR bodies written with this skill now wrap to the reader's window instead of breaking raggedly mid-paragraph. Both examples were hard-wrapped at ~76 columns and the agent reproduced that wrap, but GitHub renders an intra-paragraph newline as a line break. The examples are unwrapped and a Core Rule states the constraint.
The rest is a duplication pass. The skill named its leading concept once, inside a negation — a cover note, "not a changelog, template, validation log, or file-by-file summary" — then never used the word again, while Boundaries prohibited those same four things a second time. Leaning on the word retires the restatement, and the refresh rule, previously in both Core Rules and Body Shape, collapses to one. The only rule with no antecedent in the old text is the one ignoring repository PR templates, which SPEC had required all along.