Creating pr from branch

Skill qte77/claude-code-plugins/plugins/commit-helper/skills/creating-pr-from-branch

A Claude Code plugin marketplace providing skills, rules, and scripts extracted from a production development workflow.

Install

npx -y skills add qte77/claude-code-plugins --skill creating-pr-from-branch

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

2.2 KB, as published. Nobody here has run it

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 <base>..HEAD — commits to include
git diff --stat <base>..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

<1-3 bullet points describing what and why>

## Commits

<list commits from git log>

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 <branch-name>

# Create PR
# In Codespaces: override token if GH_PAT is needed for cross-repo
gh pr create --base <base> --title "<title>" --body "$(cat <<'EOF'
<body>
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)