Push Pr

Push PR

Commit, push, and open a pull request whose body is adapted from the real diff rather than copied from the template.

Migrated from .claude/commands/push-pr.md under ADR-064, which makes skills the single user-invocable surface. The scoped allowed-tools grant, the identity-hardened python3 -I form, and both vendor-portability declarations carry over unchanged: they are the security contract, not formatting.

Triggers

push and open a PR, open a pull request, push this branch, commit and push

Context

• Current git status: !git status
• Current git diff (staged and unstaged changes): !git diff HEAD
• Current branch: !git branch --show-current

Process

Based on the above changes:

1. Create a new branch if on main.

   1. Determine the type of change that maps to a conventional commit type followed by a 3-5 word description (for example, fix/parser-log-enrichment).

2. Push the branch to origin.

3. Read @.github/PULL_REQUEST_TEMPLATE.md

4. Run the secure path allocator:

   python3 -I "${COPILOT_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-.claude}}/skills/github/scripts/pr/new_pr.py" --prepare-body-file
   

   • Copy the returned path exactly. Do not store it in a shell variable because each tool call runs in a fresh shell.
   • Use the Edit tool to replace <!-- replace with PR body --> in that exact file with the adapted template.
   • Fill in all sections with actual change information from git diff
   • Replace placeholder comments with substantive content
   • Check appropriate Type of Change boxes based on actual changes
   • List specific files changed, test coverage added, security impacts
   • Do NOT leave template comments like <!-- Brief description --> unfilled
   • Do NOT copy the template verbatim - adapt every section to your changes
   • Include an ## Acceptance criteria heading with - [ ] or * [ ] bullets. The Validate Spec Coverage job reads these from the PR body, not the linked issue. Any unchecked box makes the signal report FAIL, and that FAIL does not block the merge, so check a box only once the criterion is actually met. Numbered criteria are not recognized.

5. Create a pull request using the new_pr skill script:

   python3 -I "${COPILOT_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-.claude}}/skills/github/scripts/pr/new_pr.py" --title "<conventional commit title>" --body-file ".agents/scratch/pr-body-<returned-uuid>.md"
   

• Title MUST follow conventional commit format (e.g., feat: Add feature, fix(auth): Resolve bug)
• Body SHOULD include GitHub issue linking keywords to auto-close issues:
  • Closes #123: auto-closes issue when PR merges
  • Fixes #456: auto-fixes issue when PR merges
  • Resolves #789: auto-resolves issue when PR merges
• Ensure PR template sections are completed

You have the capability to call multiple tools in a single response. You MUST do all of the above in a single message. Do not use any other tools or do anything else. Do not send any other text or messages besides these tool calls.

Verification

• Branch created off main when the working branch was main, never a push to main
• Title follows conventional commit format
• Body written into the allocator's returned path, copied exactly, never through a shell variable
• Every template section adapted from the real diff, with no placeholder comment left in
• An ## Acceptance criteria heading present with - [ ] bullets, checked only where met
• Issue-linking keyword present, and a closing keyword used only when the diff delivers what the issue asks

Anti-Patterns

Extension Points

• Other forges. Steps 4 and 5 call new_pr.py. A non-GitHub forge swaps that helper; the template-adaptation rules in step 4 are forge-independent.
• Template changes. Step 4's section list follows the repository PR template read in step 3. When that template gains a parsed section, add it to step 4 and to the Verification list together.
• Branch naming. Step 1's conventional-type mapping is the repository convention; a project with a different scheme changes that sub-step alone.