Menu
Create a GitHub pull request with proper issue linking and conventional commits. Use when user says "create pr", "submit pr", "open pull request", "push and create pr", or after pre-pr review passes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | create-pr |
| description | Create a GitHub pull request with proper issue linking and conventional commits. Use when user says "create pr", "submit pr", "open pull request", "push and create pr", or after pre-pr review passes. |
Create a well-structured GitHub PR with proper issue linking.
Step 1: Commit Changes → Review diff, stage, commit
Step 2: Push → Push to origin
Step 3: Review PR Diff → Verify what goes into PR
Step 4: Draft PR → Generate title + body
Step 5: Confirm with User → AskUserQuestion
Step 6: Create PR → gh pr create
Review and commit any uncommitted changes:
git diff
git status --short
git add -A
git commit -m "type(scope): description"
Conventional commit types:
feat - New featurefix - Bug fixdocs - Documentation onlyrefactor - Code restructuringtest - Adding/updating testschore - Maintenance tasksKeep subject line under 80 characters. If all changes are already committed, skip to Step 2.
git push origin <branch-name>
If push fails (e.g., no upstream), set it:
git push -u origin <branch-name>
git diff origin/main...HEAD --stat
Present summary:
Files to be included in PR:
- file1.ts (+50, -10)
- file2.ts (+20, -5)
Total: X files changed, +Y insertions, -Z deletions
Get issue context:
git branch --show-current # Extract issue number
gh issue view <number> --json title,body
Generate PR title:
Format: type(scope): description
Generate PR body:
## Summary
<1-2 sentences: what does this PR do and why>
## Related Issues
Closes #<issue-number>
## Changes
- Change 1
- Change 2
- Change 3
## Testing
- [ ] Tests pass locally
- [ ] Manual verification done
Present the draft PR:
## Proposed Pull Request
**Title:** feat(auth): add OAuth2 login flow
**Body:**
<generated body>
Ready to create this PR?
Use AskUserQuestion:
If user edits, update and re-confirm.
gh pr create --base main --title "<title>" --body "<body>"
On success, display:
## PR Created ✓
#<pr-number>: <title>
<pr-url>
Issues linked: #<issue-number> (will close on merge)
| Keyword | Effect |
|---|---|
Closes #X | Auto-closes issue on merge |
Fixes #X | Auto-closes issue on merge |
Resolves #X | Auto-closes issue on merge |
Related to #X | Links without auto-close |
Part of #X | Links to parent/epic |
Push failed. Possible causes:
- No upstream branch set
- Remote has new commits
Options: ["Set upstream", "Pull and retry", "Ask user for help"]
PR creation failed: <error>
Options: ["Retry", "Open in browser", "Ask user for help"]
Closes for issue from branch nameComprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.
Review code changes against spec for drift and principle violations before PR submission. Use when user says "pre-pr review", "check against spec", "review my changes", "spec drift", "am I following the spec", or before creating a pull request.
Design robust specs through principle-driven interviews, then create GitHub issues with sub-issue hierarchies. Use when starting a new feature, designing a solution, or when user says "let's spec this out", "design this feature", "create a spec".
Analyze coding agent session transcripts to improve existing skills or create new ones. Use when asked to improve a skill based on a session, or extract a new skill from session history.
Create new Claude Code skills. Use when user wants to create, update, or improve a skill that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Create and manage GitHub issues with duplicate detection and hierarchy support. Use when creating issues, filing bugs, tracking tasks, managing sub-issues, or organizing parent/child relationships. Triggers on "create issue", "file bug", "track this", "sub-issue", "parent issue", "break down", "list sub-issues".