Name deferral as a register class
references/prose-register.md names the classes that mark machine-written
prose, and binds PR bodies and review replies alongside source comments and
docs/. One class was missing: text about the writer rather than about the
work.
#350 carried an instance. A reply closed a decision that had already been
measured by offering to reverse it on request, and the answer was "Let's
concentrate on real discussions!". The same shape reaches review text as an
apology for a correction, and as an announcement of candor in front of a
caveat that stands on its own.
Two commits, one per surface, following the split the register states in its
own opening: the register defines a class, and a SKILL.md section names
that class's instance on one surface.
- The register gains the class, next to "Effort and flattery", which is the
neighbouring case of writing about the writer. - The Pull requests section gains the reply form, quoting the rejected
sentence and citing #350 the way the rules around it cite PR#21, PR#41 and
PR#209.
Why it costs a reviewer something: an offer to redo the work another way asks
them to choose between two shapes the writer has already measured, when the
decision and the reason that settles it were what they needed. A reviewer who
disagrees says so without being invited.
Verification
scripts/check-skill-refs.py resolves every path, target, section and
cross-reference across the 12 files under .claude/, and
scripts/check-commit-log.sh accepts both commits. Documentation only: no
build or test target reads these files.
Summary by cubic
Names deferral and self-report as a prose-register class so guidance can flag text about the writer instead of the work. Pull request replies should state a measured decision and its reason rather than hand the choice back to the reviewer.
- Covers offers to redo work, apologies for corrections, and candor announcements before independent caveats.
- Names the reply form in the Pull requests section and adds PR#350 as a concrete example.
- Documentation-only; no runtime behavior changes.