From a03bc7506cb97ed7d637f73efdf8b596a61022e5 Mon Sep 17 00:00:00 2001 From: ajmallesh Date: Tue, 24 Feb 2026 09:31:37 -0800 Subject: [PATCH] chore: improve PR command summary format with rich bullet style --- .claude/commands/pr.md | 19 ++++++++++++++++--- 1 file changed, 16 insertions(+), 3 deletions(-) diff --git a/.claude/commands/pr.md b/.claude/commands/pr.md index ddcee2d..3a2af4d 100644 --- a/.claude/commands/pr.md +++ b/.claude/commands/pr.md @@ -26,14 +26,28 @@ Then generate a PR title that: - Matches the style of recent commits in the repository Generate a PR body with: -- A `## Summary` section with 1-3 bullet points describing the changes +- A `## Summary` section using rich bullets with bold action leads - A `Closes #X` line for each issue number (if any were provided or detected from branch name) +Each Summary bullet must follow this format: +- **Bold action phrase** (imperative verb: "Add X", "Replace Y", "Fix Z") — followed by em dash and a 1-2 sentence conceptual description of what changed and why +- Keep descriptions conceptual — no inline code references (no backticks for function/file names). The diff shows the code +- Use 2-5 bullets, scaling with PR size. Group related changes into single bullets rather than listing every file touched + +Example: +``` +## Summary + +- **Add preflight validation** — validates repo path, config, and credentials before agent execution. Fails fast with actionable errors +- **Replace error strings** — pipe-delimited segments rendered as multi-line blocks with phase context, type, message, and remediation hint +- **Add error classification** — new error codes for repo, auth, and billing failures with proper retry classification +``` + Finally, create the PR using the gh CLI: ``` gh pr create --base main --title "" --body "$(cat <<'EOF' ## Summary - + Closes # Closes # @@ -45,6 +59,5 @@ Note: Omit the "Closes" lines entirely if no issues are associated with this PR. IMPORTANT: - Do NOT include any Claude Code attribution in the PR -- Keep the summary concise (1-3 bullet points maximum) - Use the conventional commit prefix that best matches the changes (fix, feat, chore, refactor, docs, etc.) - The `Closes #X` syntax will automatically close the referenced issues when the PR is merged