create-pr
Creates comprehensive GitHub pull requests with automated quality validation and security scanning. This skill should be used when the user asks to "create a PR", "submit a pull request", or needs to merge completed work with full compliance checks.
Best use case
create-pr is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Creates comprehensive GitHub pull requests with automated quality validation and security scanning. This skill should be used when the user asks to "create a PR", "submit a pull request", or needs to merge completed work with full compliance checks.
Teams using create-pr should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/create-pr/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How create-pr Compares
| Feature / Agent | create-pr | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Creates comprehensive GitHub pull requests with automated quality validation and security scanning. This skill should be used when the user asks to "create a PR", "submit a pull request", or needs to merge completed work with full compliance checks.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Create GitHub Pull Request Execute automated PR creation workflow with comprehensive quality validation and security scanning. ## Context - Current git status: !`git status` - Current branch: !`git branch --show-current` - Unpushed commits: !`git log --oneline -5` - GitHub authentication: !`gh auth status` - Repository changes: !`git diff --stat HEAD~1..HEAD` ## Requirements Summary Ensure repository readiness with clean state and authentication. Complete all quality checks (lint, test, build, security) before PR creation. Link related issues with auto-closing keywords and apply accurate labels. See `references/requirements.md` for complete checklist. ## Phase 1: Validation and Analysis **Goal**: Validate repository state, analyze changes, detect templates, and identify blockers. **Actions**: 1. Verify GitHub authentication from context 2. Check branch status and unpushed commits 3. Analyze commit history for conventional commit compliance 4. Identify changed files and determine PR scope 5. Check for contributing guidelines (`CONTRIBUTING.md`) and follow its requirements 6. Detect PR templates (`.github/PULL_REQUEST_TEMPLATE.md` or root/docs locations) 7. Detect potential blockers (merge conflicts, missing tests, etc.) See `references/repository-templates.md` for template detection and compliance details. ## Phase 2: Quality and Security Checks **Goal**: Execute comprehensive quality validation and security scanning. **Actions**: 1. Run project-specific quality checks (see `references/quality-validation.md` for commands) 2. Execute security scanning for sensitive files and hardcoded secrets 3. Validate commit message format against standards 4. If checks fail: follow failure resolution process in `references/failure-resolution.md` 5. Re-run all checks until passing ## Phase 3: PR Assembly and Creation **Goal**: Create pull request with proper structure, metadata, and links. **Actions**: 1. Identify and link related issues using GitHub CLI 2. Generate PR title (≤70 chars, imperative, no emojis) 3. Assemble PR body following template in `references/pr-structure.md` 4. Apply automated labels based on file changes 5. Create PR using `gh pr create` with all metadata 6. Report final PR URL and status to user ## References - **Requirements**: `references/requirements.md` - Pre-creation checklist and commit standards - **Repository Templates**: `references/repository-templates.md` - Contributing guidelines and PR templates - **Quality Validation**: `references/quality-validation.md` - Node.js/Python validation commands - **PR Structure**: `references/pr-structure.md` - Title guidelines, body template, labels - **Failure Resolution**: `references/failure-resolution.md` - Agent collaboration for fixing failures - **Examples**: `references/examples.md` - Commit message examples
Related Skills
create-prd
This skill should be used when the user asks to "create PRD", "write product requirements document", or mentions "PRD", "产品需求文档", "创建PRD", "写PRD", "生成PRD".
create-feishu-doc
Automates creating new documents in the Feishu workspace. This skill should be used when the user asks to "create a Feishu doc", "create a new doc in Feishu", "open Feishu and create document", "create document in leiniao-ibg", or mentions creating documents in Feishu or Lark workspace.
create-issues
Creates GitHub issues following test-driven development principles and proper labeling conventions. This skill should be used when the user asks to "create an issue", "file a bug", or needs to document new requirements, epics, or PR-scoped tasks.
update-readme
Updates README.md and README.zh-CN.md to reflect the project's current state. Use this skill whenever the user asks to "update the README", "sync the docs", "update documentation", "reflect latest changes in README", or wants both the English and Chinese READMEs to match the current project. Always triggers when the user mentions updating or regenerating README files, especially for bilingual (EN/ZH) projects.
swiftui-review
Reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. This skill should be used when the user asks to review SwiftUI code, check for deprecated iOS/macOS APIs, validate data flow patterns, or audit accessibility compliance in Swift projects.
writing-plans
Creates executable implementation plans that break down designs into detailed tasks. This skill should be used when the user has completed a brainstorming design and asks to "write an implementation plan" or "create step-by-step tasks" for execution.
systematic-debugging
Provides a systematic debugging methodology with a 4-phase root cause analysis process. This skill should be used when the user reports a bug, error, test failure, or unexpected behavior, ensuring thorough investigation precedes any code changes.
need-vet
This skill should be used when the user invokes /need-vet to enable work verification for the current task. Claude must verify completion and append the verified tag before the session can end.
executing-plans
Executes written implementation plans efficiently using agent teams or subagents. This skill should be used when the user has a completed plan.md, asks to "execute the plan", or is ready to run batches of independent tasks in parallel following BDD principles.
build-like-iphone-team
Applies Apple's Project Purple design philosophy for radical innovation. This skill should be used when the user wants to challenge industry conventions, approach open-ended problems requiring disruptive thinking, or when standard brainstorming needs a breakthrough approach.
brainstorming
Structures collaborative dialogue to turn rough ideas into implementation-ready designs. This skill should be used when the user has a new idea, feature request, ambiguous requirement, or asks to "brainstorm a solution" before implementation begins.
behavior-driven-development
Applies behavior-driven development principles including Gherkin scenarios and test-driven development. This skill should be used when the user asks to implement features, fix bugs, or when writing executable specifications and tests before writing production code.