Stats
Actions
Tags
From git
Open a pull request against the main branch with a conventional commit title and structured body. Use when the user wants to open a PR, create a pull request, submit changes for review, or share a branch with their team. Triggers on phrases like "open a PR", "create a pull request", "submit this for review", "PR this", "send a PR", or any request to open a pull request on GitHub. Also triggers when the user invokes /git:commits or asks to push and open a PR after committing.
How this skill is triggered — by the user, by Claude, or both
Slash command
/git:git-prThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Open a well-structured pull request with a conventional commit title, clear change summary, and verification steps — then generate a short announcement the user can share with their team.
Open a well-structured pull request with a conventional commit title, clear change summary, and verification steps — then generate a short announcement the user can share with their team.
A pull request is a communication tool. The title tells reviewers what kind of change this is at a glance. The body tells them why it matters, what moved, and how to verify it works. Keep it honest and scannable — no filler, no marketing. Reviewers are busy.
Understand the current state before drafting anything.
git branch --show-current
git log --oneline -10
git diff main...HEAD --stat
gh issue list --limit 5 --state open
Determine:
main or master, ask the user to create or name a branch firstmain (not just the latest)Compose the PR title and body before creating anything.
Title follows conventional commit format:
type(scope): concise description
Use the same type/scope conventions as git:commits:
| Type | When to use |
|---|---|
feat | New functionality |
fix | Bug correction |
refactor | Code improvement, no behavior change |
docs | README, comments, documentation |
style | Formatting, whitespace |
test | Adding or updating tests |
chore | Build config, dependencies, tooling |
If commits span multiple types, use the most significant one for the title. The body will capture the full picture.
Body uses this template:
[Two sentence description of change]
Closes: #[ISSUE_ID]
## Why
[Two sentence description of benefit(s)]
## What changed
- [ ] Added: [file] - [description of addition]
- [ ] Removed: [file] - [description of removal]
- [ ] Changed: [file] - [description of change]
- [ ] Formatted: [file] - [description of formatting]
## Verification
- [ ] Proposed verification step
- [ ] This could be running a certain command
- [ ] Opening a page in a web browser and observing a behavior
- [ ] Whatever is needed to gain assurance that the code works
Rules for the body:
Present the draft title and body to the user. Wait for confirmation before creating the PR.
If there's ambiguity about an issue reference, ask now:
"This looks like it might relate to #42 — should I include
Closes: #42in the PR body, or is this unrelated?"
Ensure the branch is pushed to the remote:
git push -u origin $(git branch --show-current)
Create the PR:
gh pr create --title "type(scope): description" --body "$(cat <<'EOF'
[the body from step 2]
EOF
)"
After the PR is created, return two things:
Example announcement:
Opened #47 — we now validate session tokens on every API request instead of only at login. This closes a gap where expired sessions could keep making calls until the next page refresh. Give it a look when you get a chance.
--no-verify.env, credentials, tokensnpx claudepluginhub kellymears/agents --plugin gitCreates GitHub pull requests from branch changes using git analysis and gh CLI, with conventional commit titles and standardized templated descriptions including summary, changes, testing, and checklists.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.