raise-pr

name	raise-pr
description	Generate a detailed, high-depth pull request body and create/update a PR on GitHub. Gathers workspace changes, updates the PR body dynamically, and posts update comments to capture a historical paper trail.

Raise PR Skill

Standardized procedure to generate, submit, and dynamically update a highly detailed, high-depth pull request on GitHub for this project.

When to use this skill

• Use this skill when you have completed work or made additional updates on an issue branch, run all verification checks, and are ready to create or update a GitHub Pull Request for the active branch.

How to use it

Steps for Creating a Pull Request

1. Analyze workspace changes: Review your local git changes, commit history, and test outcomes to collect all context:

   • Identify which files were created, modified, or deleted.
   • Collect the exact names of any new unit tests added (e.g., in tests/test_*.py).
   • Identify the linked GitHub issue number from your branch name (issue-<N>_...).

2. Generate a detailed, high-depth PR body: Construct a pull request body matching the standard project PR template structure. Your description must be rich and thorough (avoiding generic or one-sentence summaries).

   Template Format:

   ## Summary
   
   - **[Brief feature description]**: [Explain the high-level intent].
   - **Key Changes**:
     - Detail the specific classes, functions, or logic flows modified (e.g., in `src/breakfast/`).
     - List any new configuration keys or command-line arguments introduced.
     - List new files, directories, or assets added to the codebase.
   - **Abstractions & Design Decisions**: Explain any architectural or design patterns utilized (e.g., modular directory structures, custom index iterables).
   
   ## Test plan
   
   - [x] `make format && make lint && make test` passes (verify all checks are clean).
   - [x] **[Specific unit tests run or added]**:
     - `test_func_a` — verifies [intent].
     - `test_func_b` — verifies [intent].
   - [x] **Manual Verification / Smoke Test**:
     - Verify CLI execution (e.g., `uv run breakfast --version` runs cleanly).
     - Run any targeted CLI configurations to confirm visual correctness.
   
   Closes #<issue-number>
   
   [Agent signature: e.g., 🤖 Prepared by [Antigravity](https://github.com/google-deepmind), 🤖 Generated with [Claude Code](https://claude.com/claude-code), 🥐 Prepared by [Gemini](https://deepmind.google/technologies/gemini/), etc., matching your own identity]
   

3. Verify the PR Title format: Ensure the Pull Request title matches the mandatory convention: #<issue-number>: <description>

   • Example: #313: Color PR number column with calendar color

4. Create the PR using the GitHub CLI (gh): Execute the gh pr create command using the derived title and generated body:

   gh pr create --title "#<issue-number>: <short-description>" --body "<generated-body-content>"
   

   (If the GitHub CLI is not authenticated or available, output the formatted title and body so the user can easily copy and paste them into the GitHub web interface).

5. Confirm to the user: Report the generated PR URL and a summary of the details submitted.

---

Steps for Updating a Pull Request

If a Pull Request has already been opened for the current branch, follow this procedure when pushing new updates:

1. Regenerate the PR body:

   • Gather all changes made across the entire branch (from the base main branch to your latest commit).
   • Re-run Step 2 of "Steps for Creating a Pull Request" to generate a complete, up-to-date PR body description representing the full set of changes, test plans, and acceptance criteria.
   • Update the existing Pull Request body on GitHub using the GitHub CLI:

     gh pr edit --body "<regenerated-body-content>"
     

2. Add an update comment (for the historical paper trail):

   • Identify the specific changes introduced in this latest update/commit.
   • Write a concise summary of the new additions, bug fixes, or test enhancements.
   • Post this update summary as a comment on the Pull Request using the GitHub CLI:

     gh pr comment --body "### Update Comment: [Brief Description]
     
     - **What's New**: [Detail the latest additions/fixes].
     - **Verification**: [Mention unit tests run or added in this update]."
     

     This ensures a clear historical paper trail of how the PR evolved over time.