From be741cea3a06b80c3f9c877ca3b967d68edbe9e2 Mon Sep 17 00:00:00 2001 From: Joseph Mearman Date: Fri, 13 Feb 2026 18:53:12 +0000 Subject: [PATCH] fix(prompts): avoid redundant PR description updates Instruct Claude to check existing PR description before updating. Only add information if the description is missing or incomplete. Do not duplicate what's already present. --- .github/prompts/shared/02-guidelines.md | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/.github/prompts/shared/02-guidelines.md b/.github/prompts/shared/02-guidelines.md index fe1a83d..36d472a 100644 --- a/.github/prompts/shared/02-guidelines.md +++ b/.github/prompts/shared/02-guidelines.md @@ -29,16 +29,18 @@ click "Apply" on all of them. Keep subsequent comments brief. After submitting a review, do both of the following: -1. **Update the PR description** (the body of the PR itself, NOT a comment) - with a concise summary of what the PR changes and why. Describe the actual - modifications (new files, refactored logic, bug fixes), not the review - status. +1. **Update the PR description** ONLY if it's missing or incomplete. First check + the existing description with `gh pr view $PR_NUMBER`. If it already has a + clear summary of changes, skip this step entirely. + + When updating, add only what's missing. Use headings only when organizing + multiple distinct sections — a single paragraph needs no `## Summary` heading + since the marker block already provides context. ```bash gh pr edit $PR_NUMBER --body "$(cat <<'EOF' - ## Summary - + EOF )" @@ -46,7 +48,7 @@ After submitting a review, do both of the following: The markers `` / `` identify your section. Preserve everything outside the markers. If no marker block exists, - append yours at the end. + append yours at the end. Do NOT repeat information already in the PR body. 2. **Update PR labels** to reflect the outcome: - `gh pr edit {pr} --add-label "needs-changes"` after REQUEST_CHANGES