Skip to content

fix(ce-pr-description): cap description size and add pre-apply preview#605

Merged
tmchow merged 3 commits intomainfrom
tmchow/pr-desc-sizing
Apr 20, 2026
Merged

fix(ce-pr-description): cap description size and add pre-apply preview#605
tmchow merged 3 commits intomainfrom
tmchow/pr-desc-sizing

Conversation

@tmchow
Copy link
Copy Markdown
Collaborator

@tmchow tmchow commented Apr 20, 2026

Summary

Large PRs were producing 145-200 line descriptions with 14+ H3 subsections that re-listed Summary content in more words — reviewers either burned through them or skipped past. This caps the Large tier at ~100-150 lines, adds a compression pass that removes the common inflation patterns, and inserts a preview-and-confirm step before ce-commit-push-pr overwrites an existing PR body.

What changed

  • Step 5 sizing — Large tier now targets ~100 lines / caps at 150 and says to use a Summary-level table when a PR has 10+ mechanisms, instead of spawning an H3 per mechanism.
  • New Step 8b compression pass — cut Summary-duplicating sections, enumerated Commits lists, process-oriented Review sections, and any body running >30% over the sizing target.
  • Value-lead check on the Summary opening — rewrite mechanism-first leads ("This PR introduces...") into outcome-first ones ("X previously failed; now...").
  • New writing principles — no Commits section (GitHub shows commits in its own tab), no Review/process section (process doesn't help the reviewer evaluate code).
  • ce-commit-push-pr Step 6 — 100-word cap on free-text steering passed to ce-pr-description, with guidance that steering is for framing, not an exhaustive scope dump.
  • ce-commit-push-pr Step 7 (existing-PR rewrite) — new preview step shows the new title, the first two Summary sentences, and total line count before gh pr edit is called. User can decline and pass steering back for a regenerate.

Notes

Second commit is a compliance sweep against plugins/compound-engineering/AGENTS.md: exit-code probes in place of 2>/dev/null in ce-pr-description Step 1, a stale git-commit-push-pr prose reference, and objective-voice fixes ("In Claude Code" / "On platforms other than Claude Code") in both ce-commit and ce-commit-push-pr. Same topic, so bundled.


Compound Engineering
Claude_Code

tmchow added 2 commits April 19, 2026 17:21
…mmits/Review sections

Apply six guardrails to prevent verbose, reviewer-unfriendly descriptions on
large PRs (most visible failure mode: 14 H3 subsections re-listing Summary
content):

- Rewrite Step 5 "Large" row to cap at ~100-150 lines, prefer Summary-level
  tables over subsection-per-mechanism, and warn against 10+ subsections.
- Add Step 8b compression pass: cut Summary-duplicating sections, enumerated
  Commits lists, process-oriented Review sections, subsection explosions,
  and any body running 30%+ over the sizing target.
- Add value-lead check: rewrite Summary openings that lead with mechanism.
- Add "No Commits section" and "No Review / process section" writing
  principles so the compression pass has codified rules to cite.

In ce-commit-push-pr:
- Add steering-discipline guidance in Step 6 capping free-text steering at
  ~100 words so ce-pr-description isn't pushed toward exhaustive mode.
- Insert a preview-and-confirm step into Step 7's existing-PR rewrite path
  so the user sees the title, first two Summary sentences, and total line
  count before the new body is applied (matches DU-3's pattern).
Clean up three compliance gaps flagged against plugins/compound-engineering/AGENTS.md:

- ce-pr-description Step 1: replace `2>/dev/null` probes with an exit-code
  elif chain so runtime bash no longer suppresses stderr.
- ce-pr-description Step 9: update stale prose reference from
  `git-commit-push-pr` to `ce-commit-push-pr`.
- ce-commit-push-pr and ce-commit: switch "If you are Claude Code" wording
  to objective voice ("In Claude Code" / "On platforms other than Claude
  Code") to match the writing-style rule against second person.

Stable/beta sync: ce-commit has no `-beta` counterpart; voice fix is
plugin-wide for consistency between the two commit-related skills.
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 79a961da9f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread plugins/compound-engineering/skills/ce-commit-push-pr/SKILL.md Outdated
…ser convention

The preview-and-confirm step in Step 7's existing-PR branch spelled out
"Use the platform's blocking question tool" inline, which bypassed the
skill's top-of-file "Asking the user" umbrella and omitted the
no-question-tool fallback. That left cross-platform runs able to stop
after generating {title, body_file} without ever applying the update.

Replace the inline instruction with "Ask the user (per the 'Asking the
user' convention at the top of this skill): ..." so the umbrella's tool
list and numbered-options fallback apply to the new prompt, matching
every other "ask" in this skill and satisfying the AGENTS.md
Cross-Platform User Interaction rule.
@tmchow tmchow merged commit 409b07f into main Apr 20, 2026
2 checks passed
This was referenced Apr 19, 2026
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