Skip to content

feat(publisher): PR descriptions for non-implementors + a legible review trail - #115

Merged
eduralph merged 1 commit into
mainfrom
feat/106-pr-description-accessibility
Jun 22, 2026
Merged

feat(publisher): PR descriptions for non-implementors + a legible review trail#115
eduralph merged 1 commit into
mainfrom
feat/106-pr-description-accessibility

Conversation

@eduralph

Copy link
Copy Markdown
Owner

Summary

Closes #106.

The publisher drafted pr-description.md as Root cause / Fix / Verified against / Test — implementor-dense (opens with internals + path:lines, assumes the reader lives in the file). Reshape the PR body (template + publisher leaf prompt + offline stub) for the PR's actual audience, without leaking internal PDCA jargon:

  • Plain-language Summary first (symptom/impact, then the one-line change), then What to look at (where to focus + how to reproduce). Root cause / Fix follow for the deep reviewer.
  • Verification becomes a skimmable claim→evidence trail (claim, where checked with path:lines on the target branch, regression test fails pre-fix / passes post-fix).

Invariants preserved: the [tracker].issue_trailer blank-separated last line (commit + PR linted independently), one-logical-fix scope, path:lines on the target branch, draft-PR-only / human-marks-ready, provider-agnostic + project-overridable.

Verification

Template-slot test now asserts the Summary-before-Root-cause lead and Verification-before-trailer. Full offline suite: 169 OK.

🤖 Generated with Claude Code

…iew trail (#106)

The publisher drafted pr-description.md as Root cause / Fix / Verified against / Test
— implementor-dense: it opened with internals and `path:lines` and assumed the reader
lives in the file. That serves the author and a deep reviewer but does little for the
PR's other readers (a maintainer triaging, a non-implementor deciding whether to
engage) and doesn't make the review the change already passed legible.

Reshape the PR body (template + publisher leaf prompt + offline stub) to lead for the
PR's actual audience, without leaking internal PDCA jargon:

- Plain-language **Summary** first (user-facing symptom/impact, then the one-line
  change), then **What to look at** (where to focus + how to reproduce). Root cause /
  Fix follow for the deep reviewer.
- **Verification** becomes a skimmable claim→evidence trail: the claim, where it was
  checked (path:lines on the target branch), and the regression test failing pre-fix /
  passing post-fix.

Invariants preserved: the [tracker].issue_trailer as the blank-separated last line
(commit + PR linted independently), one-logical-fix scope, path:lines on the target
branch, draft-PR-only / human-marks-ready, provider-agnostic + project-overridable.

Tests: the template-slot test now asserts the Summary-before-Root-cause lead and the
Verification section precedes the trailer. Full offline suite: 169 OK.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: Eduard Ralph <15236434+eduralph@users.noreply.github.com>
@eduralph
eduralph merged commit 075a45c into main Jun 22, 2026
2 checks passed
@eduralph
eduralph deleted the feat/106-pr-description-accessibility branch June 22, 2026 18:56
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.

publisher leaf: make PR descriptions accessible to non-implementors + a legible review trail

1 participant