pr-create
Creates pull requests by automatically selecting the correct template, title format, and labels based on branch type and project configuration.
Install
mkdir -p .claude/skills/pr-create && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15070" && unzip -o skill.zip -d .claude/skills/pr-create && rm skill.zipInstalls to .claude/skills/pr-create
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Create a pull request with title, body, labels, and templateKey capabilities
- →Determine PR title from branch type
- →Select appropriate PR template based on work type
- →Determine and assign labels (type, topic, area)
- →Determine target branch based on scenario
- →Write a summary for the PR body
- →Document validation and add links in the PR body
How it works
The skill orchestrates the PR creation process by determining configuration details like title, template, labels, and target branch, then composes the PR body with summary, scope, validation, and links.
Inputs & outputs
When to use pr-create
- →Open a pull request for a new feature branch
- →Generate a hotfix PR with a specific emergency template
- →Standardize PR titles and labels across a team repository
- →Attach issue references and validation summaries to PR descriptions
About this skill
PR Create
Uses Orchestrator. Create a pull request with appropriate title, template, labels, and description.
Prerequisites: Branch exists with commits, changes pushed to remote, verification passed (build, tests)
Phase 1: Determine Configuration
PR Setup
- Determine PR title from branch type:
<type>(<scope>): <description> - Select template based on work type:
| Work Type | Template |
|---|---|
| Features | pr.md |
| Bug fixes | pr.md |
| Documentation | pr.md |
| Maintenance | pr.md |
| Hotfixes | pr-hotfix.md |
| Releases | pr-release.md |
- Determine labels (type, topic, area)
- Determine target branch:
| Scenario | Target |
|---|---|
| Standalone work | main |
| Part of epic/phase | Epic/phase branch |
| Hotfix | main |
- Note merge method for reviewer context (default: merge commit; read
project.merge-methodfromworkspace.config.yaml)
Phase 2: Compose PR Body
Write Description
- Write summary (what and why)
- List scope (files changed, areas affected)
- Document validation (build passes, tests pass)
- Add links (closes issue, related ADRs)
- Fill in the selected template
Output
## Context Anchors
- **Issue:** #<number> - <title>
- **Branch:** `<branch>` → `<target>`
- **Phase:** 2 — Compose PR Body
## PR Configuration
| Property | Value |
| ------------ | -------------------------------- |
| Title | `<type>(<scope>): <description>` |
| Template | `<template>.md` |
| Target | `<target-branch>` |
| Merge method | <method from config> |
| Labels | `type:...`, `topic:...` |
## PR Body Preview
<full body content>
## Next Step
Awaiting approval to create PR.
**Approval Required:** Yes
⛔ CHECKPOINT
STOP. Do not create PR until human explicitly approves:
- PR title and labels
- Target branch
- PR body content
Phase 3: Create and Report
Execute PR Creation
- Write PR body to
.tmp/scratch/pr-body.md - Execute the forge's PR creation operation with:
- Base: target branch (from Phase 1)
- Head: feature branch
- Title:
<type>(<scope>): <description> - Body: from
.tmp/scratch/pr-body.md - Labels: from Phase 1
- Update board status to In Review for the linked issue
- Report PR number and URL
Board Integration
Read workspace.config.yaml for board field IDs.
Set issue status to In Review (board.status_options.in-review.option_id).
Output
## Context Anchors
- **PR:** #<pr-number> - <title>
- **Issue:** #<issue-number>
- **Status:** Open, awaiting review
## Next Step
PR created. Awaiting review.
**Approval Required:** No
Error Handling
| Error | Recovery |
|---|---|
| Branch not pushed | Push first, then retry |
| Build/tests not passing | Fix issues before PR |
| Missing issue link | Confirm issue number |
| Forge not authenticated | Check authentication status |
When not to use it
- →When the branch does not exist with commits
- →When changes have not been pushed to remote
- →When verification (build, tests) has not passed
Limitations
- →Requires branch to exist with commits.
- →Requires changes to be pushed to remote.
- →Requires verification (build, tests) to have passed.
How it compares
This skill automates the structured creation of a pull request by analyzing branch type, selecting templates, and generating a detailed body, providing a standardized and efficient process compared to manual PR creation.
Compared to similar skills
pr-create side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| pr-create (this skill) | 0 | 5mo | No flags | Beginner |
| resolve-conflicts | 81 | 8mo | Review | Intermediate |
| git-advanced-workflows | 11 | 2mo | Review | Advanced |
| nx-workspace | 4 | 6mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by daemn256
View all by daemn256 →You might also like
resolve-conflicts
antinomyhq
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.
git-advanced-workflows
wshobson
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
nx-workspace
nrwl
Explore and understand Nx workspaces. USE WHEN answering any questions about the nx workspace, the projects in it or tasks to run. EXAMPLES: 'What projects are in this workspace?', 'How is project X configured?', 'What targets can I run?', 'What's affected by my changes?', 'Which projects depend on library Y?', or any questions about Nx workspace structure, project configuration, or available tasks.
fix-github-issue
AgnosticUI
Fix a GitHub issue by number. Use when asked to fix GitHub issues.
rebase-pr
AztecProtocol
Rebase a PR on its base branch, fix conflicts, and verify build
resolve-pr-parallel
EveryInc
Resolve all PR comments using parallel processing. Use when addressing PR review feedback, resolving review threads, or batch-fixing PR comments.