AgentStack
SKILL verified Apache-2.0 Self-run

Creating Pr From Branch

skill-qte77-claude-code-plugins-creating-pr-from-branch · by qte77

Create a pull request from the current branch. Analyzes commits, generates title+body from PR template, pauses for approval, then pushes and creates PR. Use after committing changes.

No reviews yet
0 installs
17 views
0.0% view→install

Install

$ agentstack add skill-qte77-claude-code-plugins-creating-pr-from-branch

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Creating Pr From Branch? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Create PR from Current Branch

Base branch: $ARGUMENTS (default: main)

Step 1: Analyze Branch

Run using the Bash tool:

  • git branch --show-current — current branch name
  • git log --oneline ..HEAD — commits to include
  • git diff --stat ..HEAD — overall diff stats
  • git remote -v — verify remote exists

If no commits ahead of base, stop and inform the user.

Step 2: Generate PR Title and Body

Title: Derive from commits using conventional commit format.

  • Single commit: use commit subject as-is
  • Multiple commits: synthesize a summary title (type[(scope)]: description)
  • Keep under 72 characters

Body: Check for .github/pull_request_template.md. If it exists, populate its sections. If not, use this minimal format:

## Summary

## Commits

Body guidelines:

  • Fill template checkboxes where applicable (check items that are done)
  • Include Closes #N if the branch name contains an issue number
  • Keep it concise — the diff speaks for itself

Step 3: Pause for Approval

Present the title and body. Ask the user:

  • Approve: "yes", "y", "create", "go ahead"
  • Edit: Provide changes to title or body
  • Cancel: "no", "cancel", "stop"

Step 4: Push and Create PR

Once approved:

# Push branch (set upstream)
git push -u origin 

# Create PR
# In Codespaces: override token if GH_PAT is needed for cross-repo
gh pr create --base  --title "" --body "$(cat 
EOF
)"

Auth handling: If gh pr create fails with 403/422, retry with GITHUB_TOKEN="" GH_TOKEN="${GH_PAT}" prefix (Codespaces token override).

After creation, output the PR URL.

Step 5: Post-Create

  • gh pr view --web — open in browser (optional, ask user)

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.