ahmedelgabri/pr-create
config/claude/skills/pr-create/SKILL.md
Create a GitHub pull request as a draft, auto-generating title and body from commits
$ install --global
skillsauthnpx skillsauth add ahmedelgabri/dotfiles pr-createInstall 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: May 10, 2026, 3:37 AM135.3s1 file scanned
SKILL.md
- name:
- pr-create
Create a GitHub pull request for the current branch using the gh CLI.
Steps
-
Determine the default branch by running:
gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'Use this as the base branch unless the user has specified a different base.
-
Gather context by running these in parallel:
git log <base>..HEAD --onelineto see all commits being proposedgit diff <base>...HEAD --statto see a summary of changed filesgit diff <base>...HEADto see the full diff
-
Check for a PR template by looking for files in these locations (in order of priority):
.github/PULL_REQUEST_TEMPLATE.md.github/PULL_REQUEST_TEMPLATE/directory (if multiple templates exist, pick the default one, or ask the user which to use)PULL_REQUEST_TEMPLATE.md(repo root)
If a template is found, read it and use its structure for the PR body. Fill in the template sections based on the commits and diff.
-
Draft the PR title and body:
- Auto-generate a concise title (under 72 characters) from the commits and diff
- Generate the body using the template structure if one was found, otherwise write a clear summary of the changes
- The body should explain what changed and why, based on commit messages and the diff
-
Present the draft to the user:
- Show the proposed title and body.
- Ask if they want to make any changes before creating the PR.
- If the user provides revisions, incorporate them.
-
Create the PR by running:
gh pr create --draft --title "<title>" --body "<body>" --base <base-branch>Use a HEREDOC for the body to preserve formatting.
-
Report the PR URL back to the user.
Notes
- Always create PRs as drafts.
- If the user specifies a base branch (e.g., "base this on the feature-x branch"), use that instead of the default branch.
- If there are unpushed commits, push the branch first with
git push -u origin HEAD(after checking thatoriginis the correct remote for GitHub by inspecting the output ofgit remote -v). - If the current branch has no commits ahead of the base, inform the user and do not create a PR.
Related Skills
ahmedelgabri/shannon
development
VerifiedTrustedCommunity
Interact with Neovim via RPC to annotate code, navigate files, and do walkthroughs
287SKILL.mdUpdated May 10, 2026
ahmedelgabri/jj-version-control
tools
VerifiedTrustedCommunity
How to use `jj`, the Jujutsu version control system
287SKILL.mdUpdated May 10, 2026
ahmedelgabri/jj-commit
tools
VerifiedTrustedCommunity
Create a commit (or draft a commit message) in a Jujutsu repository
287SKILL.mdUpdated May 10, 2026
ahmedelgabri/git-commit
tools
VerifiedTrustedCommunity
Create a commit (or draft a commit message) in a Git repository
287SKILL.mdUpdated May 10, 2026