Agent skill
pr-create
Create a pull request with title, body, labels, and template
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/pr-create-daemn256-workspace-repo-templ
SKILL.md
PR Create
The Orchestrator drives this workflow. 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
Steps
- Determine PR title:
<type>(<scope>): <description> - Select template based on work type
- Determine labels (type, topic, area)
- Determine target branch
- Note merge method for reviewer context (default: merge commit; read
project.merge-methodfromworkspace.config.yaml)
Template Selection
| Work Type | Template |
|---|---|
| Features | pr.md |
| Bug fixes | pr.md |
| Documentation | pr.md |
| Maintenance | pr.md |
| Hotfixes | pr-hotfix.md |
| Releases | pr-release.md |
Target Branch
| Scenario | Target |
|---|---|
| Standalone work | main |
| Part of epic/phase | Epic/phase branch |
| Hotfix | main |
Phase 2: Compose PR Body
Steps
- 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>`
## 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 proceed until human approves PR configuration.
Phase 3: Create & Report
Steps
- Write PR body to
.tmp/scratch/pr-body.md - Execute the forge's PR creation operation with:
- Base: target branch
- 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.
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 |
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?