Menu
Create a pull request with a well-crafted description. Use when the user finished work on a branch and wants to open a PR, or asks to create a pull request.
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
Set up or bootstrap a project with the claude-code-config tooling — setup-project.sh, install-tooling.sh, the layered hooks setup, and the new-repo runbook. Use when installing this config into a repo, running the setup scripts, vendoring the make-check tooling, or bootstrapping a new project.
Create a new "Later" backlog item (Learn / Research / Do / Read) from a configurable template.
Install or update the shared MkDocs Material style layer (Ink & Indigo on warm paper) in the current project.
Prepare technical analysis for backlog refinement meetings.
Capture a quick status update and append it to today's daily log.
Prepare end-of-week review notes summarizing the full week's work activity across all sources (Git, GitHub, Jira).
| name | pr |
| description | Create a pull request with a well-crafted description. Use when the user finished work on a branch and wants to open a PR, or asks to create a pull request. |
| argument-hint | [--draft] [--base <branch>] |
Help me create a pull request with a well-crafted description.
$ARGUMENTS
--draft or -d: Create as draft PR--base <branch>: Specify base branch (default: main)/pr --draft, /pr --base developRead Jira config from the project's CLAUDE.md if present (look for a
## Jira section with Base URL and Ticket Pattern). If absent, prefer
the mcp__claude_ai_Atlassian__* tools (which return canonical URLs from
the API), or ask the user. Do not assume any specific organisation's URL.
[A-Z]+-\d+ (e.g. ABC-123, PROJ-456), #123, GH-123git branch --show-current
git log origin/main..HEAD --oneline
git diff origin/main..HEAD --stat
git diff origin/main..HEADspecs/ directoryExtract ticket ID from branch name patterns:
feature/BIL-123-description → BIL-123fix/BIL-456-bug-fix → BIL-456BIL-789/some-feature → BIL-789If Jira MCP is available (mcp__plugin_atlassian_atlassian__getJiraIssue):
If Jira MCP is NOT available but ticket ID found:
Related: [TICKET-ID](<base_url>/TICKET-ID)Search for PR templates in order:
.github/PULL_REQUEST_TEMPLATE.md.github/PULL_REQUEST_TEMPLATE/default.md.github/pull_request_template.mddocs/pull_request_template.mdIf template found:
If no template found:
Default structure (if no template):
## 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}
gh pr create --title "<title>" --body "<body>"
Present the PR title and description for review, then create when approved. Return the PR URL when complete.