Skip to content

Tighten changelog and PR body guidance - #160

Merged
wallstop merged 1 commit into
mainfrom
guidance/changelog-pr-brevity
Oct 10, 2026
Merged

wallstop merged 1 commit into
mainfrom
guidance/changelog-pr-brevity

Conversation

@wallstop

@wallstop wallstop commented Oct 10, 2026 •

Copy link
Copy Markdown
Owner

DISCLOSURE: LLM-GENERATED TEXT

Why: Changelog entries grew into multi-sentence narratives and PR bodies drifted away from why the change exists and what it does, so reviewers cannot skim them.

What:

  • Cap CHANGELOG entries at one or two sentences (300 rendered characters), verb-first, user effect first.
  • Keep released sections immutable and fold pre-release fix guarantees into the feature entry.
  • Require an LLM disclosure line, a 50-character title, a one-sentence Why, and short What bullets on PRs.
  • Shorten the two existing Unreleased entries to the new style.

Refs #159

Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Refactor (code change that neither fixes a bug nor adds a feature)

Checklist

  • I have added tests that prove my fix is effective or my feature works
  • I have updated the documentation accordingly
  • I have updated the CHANGELOG for user-facing changes
  • My changes do not introduce breaking changes, or breaking changes are documented

Note

Low Risk
Documentation and changelog copy only; no runtime, packaging, or CI behavior changes.

Overview
Tightens agent and contributor writing rules for changelogs, commits, and pull requests across .llm/context.md, ship-changes, and bump-version-release.

CHANGELOG entries are now capped at one or two sentences (300 rendered characters), verb-first with user-visible effect first, with released sections immutable and pre-release fixes folded into feature entries. PRs require an DISCLOSURE: LLM-GENERATED TEXT line on agent-written bodies, a 50-character imperative title, a one-sentence Why, and two to five What bullets of at most 12 words each; commit subjects stay within 72 characters. The two existing Unreleased items in CHANGELOG.md are shortened to demonstrate the new style.

Reviewed by Cursor Bugbot for commit aaedd8a. Bugbot is set up for automated code reviews on this repo. Configure here.

Changelog entries are capped at one or two sentences (300 rendered
characters, issue links excluded), start with the verb their section
names, lead with the user-visible effect, and never narrate mechanism.
Released sections are immutable; a fix for a defect that never shipped
folds into the feature's entry.

PR bodies start agent-written text with an LLM disclosure line and keep
a 50-character imperative title, a one-sentence Why, and two to five
one-line What bullets of at most 12 words. Root causes, measurements,
run IDs, CI results, validation lists, diffs, and file lists live in
commits, tests, and issues, never in the PR body. Commit subjects are
capped at 72 characters with why-first bodies.

Style adopted from ambiguous-interactive/unity-helpers. The two
existing Unreleased entries are shortened to the new style. The
300-character cap has no lint yet; that is recorded as #159.
@wallstop
wallstop merged commit 10030be into main Oct 10, 2026
3 checks passed
@wallstop
wallstop deleted the guidance/changelog-pr-brevity branch October 10, 2026 04:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant