pr-release-agent

PR Release Agent

Automates the full PR lifecycle: analyze changes, draft a description that fills the project PR template, push, create the PR, and clean up.

Prerequisites

• gh CLI installed and authenticated (gh auth status)

Workflow

Track progress with this checklist:

PR Release Progress:
- [ ] Step 1: Gather context
- [ ] Step 2: Draft PR description & generate title
- [ ] Step 3: Save draft to pr_draft.md
- [ ] Step 4: Stage and commit changes
- [ ] Step 5: Push branch to origin
- [ ] Step 6: Create or update PR via gh CLI
- [ ] Step 7: Clean up pr_draft.md

Step 1 — Gather context

Author scope — required

The PR title, Description, Focus Areas, and checkbox inferences must reflect only work authored by the person running the workflow (plus any unstaged/staged edits still on disk). Do not summarize, quote, or paraphrase commit messages from other contributors—even if those commits sit on main..HEAD.

1. Resolve the author identity (read-only):

   AUTHOR_EMAIL="$(git config user.email)"
   

   If AUTHOR_EMAIL is empty, stop and tell the user to set user.email (or run the workflow after configuring it). Do not change git config — see Important notes.

2. Compute the merge base with the integration branch (assume main unless the user specifies otherwise):

   MB="$(git merge-base main HEAD)"
   

Run these commands in parallel with the usual housekeeping (branch, status):

git branch --show-current
git status --short
git diff
git diff --cached

Commits and patches authored by AUTHOR_EMAIL only — use these for narrative scope (titles, bullets, Focus Areas):

git log "${MB}"..HEAD --author="${AUTHOR_EMAIL}" --oneline
git log "${MB}"..HEAD --author="${AUTHOR_EMAIL}" --stat

For finer detail when summarizing behaviour, restrict to authored commits:

git log "${MB}"..HEAD --author="${AUTHOR_EMAIL}" -p

(Optional) For awareness only — do not copy summaries from these into the PR unless the user asked to describe the entire branch: