How do I install the Creating Pr From Branch skill?

Run npx skillmds@latest add qte77/creating-pr-from-branch in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Creating Pr From Branch safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Creating Pr From Branch?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Creating Pr From Branch free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Creating Pr From Branch?

qte77 (@qte77) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Creating Pr From Branch by qte77 — Agent Skill

Name: Creating Pr From Branch
Rating: 4.2 (5 reviews)
Author: qte77

File contents

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)

---name: creating-pr-from-branchdescription: 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.---# Create PR from Current Branch**Base branch**: $ARGUMENTS (default: `main`)## Step 1: Analyze BranchRun 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 existsIf 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, populateits sections. If not, use this minimal format:```markdown## 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 ApprovalPresent 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 PROnce approved:```bash# Push branch (set upstream)git push -u origin <branch-name># Create PR# In Codespaces: override token if GH_PAT is needed for cross-repogh 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)

Frequently asked questions

Creating Pr From Branch