Programming · Writing
pr
/pr
Open a pull request with a well-crafted description. Use when branch work is finished and ready for review.
For whom
- Author
- edjchapman ↗
- Repository
- claude-code-config ↗
- Licence
- MIT
- Last repository change
- 23.10.2026
Assessment and security
100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
Deprecation
No signals detected. Repository changed on 23.10.2026, without references to retired models or APIs.
Licence
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Open a pull request with a well-crafted description. Use when branch work is finished and ready for review.
Arguments
/pr [--draft] [--base <branch>]
Original author description
Open a pull request with a well-crafted description. Use when branch work is finished and ready for review.
How it works
- Arguments
- Jira Configuration
- Steps
- Output
Original SKILL.md headings · 119 lines, 451 words
SKILL.md preview
---
name: pr
description: Open a pull request with a well-crafted description. Use when branch work is finished and ready for review.
argument-hint: "[--draft] [--base <branch>]"
---
Help me create a pull request with a well-crafted description.
## Arguments
`$ARGUMENTS`
- `--draft` or `-d`: Create as draft PR
- `--base <branch>`: Specify base branch (default: main)
- Examples: `/pr --draft`, `/pr --base develop`
## Jira Configuration
Read Jira config from the project's `CLAUDE.md` if present (look for a
`## Jira` section with `Base URL` and `Ticket Pattern`). If absent, ask the
user. Do not assume any specific organisation's URL.
- **Common ticket patterns**: `[A-Z]+-\d+` (e.g. `ABC-123`, `PROJ-456`), `#123`, `GH-123`
## Steps
### Step 1: Understand current state
```bash
git branch --show-current
git log origin/main..HEAD --oneline
git diff origin/main..HEAD --stat
```
### Step 2: Analyze all commits being included
- Read each commit message
- Look at the actual changes with `git diff origin/main..HEAD`
- Identify the main themes and purpose
### Step 3: Check for related context
- Look for ticket/issue numbers in branch name or commits
- Check if there are related specs in `specs/` directory
- Note any breaking changes or migrations
### Step 4: Extract Jira context from branch name
Extract ticket ID from branch name patterns:
- `feature/BIL-123-description` → `BIL-123`
- `fix/BIL-456-bug-fix` → `BIL-456`
- `BIL-789/some-feature` → `BIL-789`
**If a ticket ID is found:**
- Add a Jira link to the PR body using the project CLAUDE.md base URL:
`Related: [TICKET-ID](<base_url>/TICKET-ID)`
- If no base URL is configured, include the ticket ID as plain text and note:
"Jira base URL not configured in project CLAUDE.md - add manually if needed"
### Step 5: Check for PR template
Search for PR templates in order:
1. `.github/PULL_REQUEST_TEMPLATE.md`
2. `.github/PULL_REQUEST_TEMPLATE/default.md`
3. `.github/pull_request_template.md`
4. `docs/pull_request_template.md`
**If template found:**
- Use template as base structure for PR body
- Merge Jira context and commit analysis into template sections
- Fill in template placeholders where possible
**If no template found:**
- Use default structure (see Step 6)
### Step 6: Generate PR description
**Default structure (if no template):**
```markdown
## Summary
<1-3 bullet points explaining what this PR does and why>
## Changes
<Grouped list of significant changes>
## Testing
<How this was tested or how reviewers should test>
## Notes for Reviewers
<Any context that helps review: focus areas, known issues, follow-ups>
## Related Issues
- [TICKET-ID](<base_url>/TICKET-ID) - {summary from Jira if available}
```
### Step 7: Ask for confirmation before creating
- Show the proposed title and description
- Confirm the base branch (usually main)
- If Jira ticket found, confirm linking is correct
- Ask if ready to create
### Step 8: Create the PR (only when confirmed)
```bash
gh pr create --title "<title>" --body "<body>"
```
## Output
Present the PR title and description for review, then create when approved.
Return the PR URL when complete.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · edjchapman/claude-code-config | 100 | MIT |
| harlan-zw/harlan-claude-code | 100 | MIT |
| harlan-zw/harlan-agent-kit | 100 | MIT |
| jongio/skills | 100 | MIT |
| windmill-labs/windmill | 100 | Apache-2.0 |
| opsmill/infrahub | 100 | Apache-2.0 |
| nesquikm/dev-process-toolkit | 100 | MIT |
| tony/skills | 100 | MIT |
| tony/skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version aee8bcbe4362 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100create-pr
Stage, commit, push, and open a pull request following project conventions and the Conventional Commits spec. Accepts an optional skip-checks argument to bypass validation when called from /build. Use when the user says "create a PR", "open a PR", "submit a pull request", or… - 100kit-create-pr
Commit changes and create a pull request with proper formatting. Use when ready to publish work for review. - 100pr-create
Use when work is complete and ready to create a PR for review. Triggers include "/pr-create", "create a PR", "commit and push", "open a PR". - 100park
Park a feature on its branch without merging to main. Use when work is done but you're not ready to ship yet. - 86lemonlime-open-pr
Open a pull request for the thread's branch. Use when the user asks for a pull request, a PR, or to send the work for review. - 100pr-description
Write a pull request title and description for the current branch, and open the PR if asked. Use when the user says "open a PR", "create a pull request", "write the PR description", "describe my changes for review".