stevenmburns/create-pr
skills/create-pr/SKILL.md
Push the current branch and open a PR to merge it into main, with a title derived from the branch name and commit changes
data-ai
Updated Apr 20, 2026
$ install --global
skillsauthnpx skillsauth add stevenmburns/dot-claude-files create-prInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 20, 2026, 4:34 AM24.6s1 file scanned
SKILL.md
- name:
- create-pr
- description:
- Push the current branch and open a PR to merge it into main, with a title derived from the branch name and commit changes
- user-invocable:
- true
- allowed-tools:
- Bash
Open a PR to Merge Current Branch into Main
Push the current branch and create a pull request targeting main.
Steps
- Run
git statusto check for any uncommitted changes (staged or unstaged). If any exist, stage and commit them before proceeding — do not create the PR with a dirty working tree. Use a descriptive commit message and include theCo-Authored-Bytrailer. - If the project contains Python files, run
ruff checkandruff format --checkin the repo root. Fix any errors before proceeding. If ruff is not installed, skip this step. - Run
git branch --show-currentto get the branch name - Run
git log main..HEAD --onelineandgit diff main...HEADto understand what changed - Derive a clear, human-readable PR title from both the branch name and the actual changes — do not just restate the branch name verbatim; synthesize a title that captures the intent
- Push the branch with
git push -u origin <branch>if not already pushed - Open the PR with
gh pr create --base main --title "..." --body "..."using the standard body format below
PR Body Format
## Summary
<2-4 bullet points describing what changed and why>
## Test plan
- [ ] <relevant test steps>
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Do not ask for confirmation. Push and open the PR, then return the PR URL.
Related Skills
stevenmburns/triage-issues
tools
VerifiedTrustedCommunity
Scan open GitHub issues, flag duplicates, and summarize with suggested priorities
SKILL.mdUpdated Apr 20, 2026
stevenmburns/tidy-branch
testing
VerifiedTrustedCommunity
Interactively clean up the current branch's commits (squash fixups, reword sloppy messages, reorder, drop) before merging — especially important on repos using rebase-merge where every branch commit lands on main verbatim
SKILL.mdUpdated Apr 20, 2026
stevenmburns/rename-pr
tools
VerifiedTrustedCommunity
Analyze the changes in the current PR and suggest a more accurate title if the current one no longer fits
SKILL.mdUpdated Apr 20, 2026
stevenmburns/merge-pr
data-ai
VerifiedTrustedCommunity
Merge the open PR for the current branch into main, delete the branch, and pull main
SKILL.mdUpdated Apr 20, 2026