Menu
Create a PR with a well-structured description in your writing style
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
Weekly backlog audit — field completeness, staleness tiers, and duplicate detection. Run during grooming to clean up the backlog.
Creates a JIRA Bug with steps to reproduce, expected/actual behavior, and fix criteria. Activates when users ask to create a bug report, file a bug, or report an issue.
Creates a JIRA Epic with scope, success criteria, and child story breakdown. Activates when users ask to create an epic.
Creates a JIRA Story with user story format, acceptance criteria, and technical notes. Activates when users ask to create a story or user story.
Creates a JIRA Task for tech debt, infrastructure, documentation, or spike work. Activates when users ask to create a task, spike, tech debt ticket, or infrastructure work.
Daily briefing — sprint progress, new tickets, and recent comments in one report. Run this to get oriented at the start of the day.
| name | pr-create |
| description | Create a PR with a well-structured description in your writing style |
| allowed-tools | Bash, mcp__writing-samples__qdrant-find |
| argument-hint | ["base-branch"] |
| disable-model-invocation | true |
Create a pull request with a well-structured description written in your personal style.
$1 (optional): Base branch to merge into (default: auto-detected by gh)# Current branch
git branch --show-current
# Resolve base branch once
BASE=${1:-$(gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name')}
# Changes vs base
git log --oneline $(git merge-base HEAD $BASE)..HEAD
# Diff stats
git diff --stat $BASE...HEAD
# Full diff for understanding
git diff $BASE...HEAD
# Check if a PR already exists for this branch
gh pr view --json number,title,url 2>/dev/null
If a PR already exists, show it to the user and ask whether they want to:
If no PR exists, continue to Step 3.
If the qdrant-find MCP tool is available, query for:
Use retrieved samples to match the user's voice for PR descriptions.
Title rules:
Body structure:
gh pr create \
--title "[generated title]" \
--body "[generated body]" \
${1:+--base $1}
### PR Created: #[number]
**Title**: [title]
**URL**: [url]
**Branch**: [head] → [base]
---
[PR body as written]