Menu
Create a GitHub pull request from the current feature branch. Use when the user says "create pr", "open pr", "merge request", "create mr", "open mr".
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
| name | create-pr |
| description | Create a GitHub pull request from the current feature branch. Use when the user says "create pr", "open pr", "merge request", "create mr", "open mr". |
Create a GitHub pull request from the current feature branch.
git branch --show-current
git status --short
gh auth status 2>&1
Hard stops:
main or master - ABORT ("Switch to a feature branch first.")gh not authenticated - ABORT ("Run gh auth login first.")Check if PR already exists:
gh pr list --head "$(git branch --show-current)" --json number,url --jq '.[0]'
If PR exists, show URL and stop.
Collect all available context for the PR body:
feature/<name>git log main..HEAD --onelinedocs/specs/ for a directory whose name contains keywords from the branch name. If found, read the spec's Purpose and Scope sections.Build the PR title and body:
Title: Use the most recent commit's conventional commit message. If multiple specs/features, use a summary title.
Body structure (use all available context):
## Summary
<One paragraph from spec Purpose section if found, otherwise summarize from commits.>
## Changes
<Bullet list from commit log, grouped by conventional commit type (feat, fix, refactor, docs, chore). Each bullet is the commit subject.>
## Spec
<If spec found: link to spec file path. If not: omit this section entirely.>
Show the full PR preview (title + body) and ask for confirmation.
On confirmation:
gh pr create \
--title "<title>" \
--body "<body>" \
--base "$(gh repo view --json defaultBranchRef -q .defaultBranchRef.name)" \
--draft
PR created:
URL: <url>
Title: <title>
Status: Draft
Base: main
Audits agents, prompts, skills, knowledge, and documentation for gaps, inconsistencies, and improvement opportunities. Proposes changes for user approval. Triggers on "agent-audit", "audit agents", "review config", "what can we improve".
Use before any creative work or spec creation. Explores intent, challenges assumptions, and produces specs. Triggers on "brainstorm", "let's design", "spec out", "define requirements", "write a spec", "challenge this", "poke holes", "what am I missing".
Detects documentation drift after structural changes. Dispatches parallel specialist reviewers and auto-fixes. Triggers on "check my docs", "audit docs", "doc drift", "check doc drift", or auto from post-implementation when tracked categories change.
Automated post-implementation workflow. Triggers when the orchestrator receives DONE from an implementation subagent. Runs quality gate, doc staleness check, auto-review, and improvement capture.
Periodic codebase health check. Use when the user says "health check", "technical debt", "what needs attention", "codebase audit", "codebase health".
Takes a spec phase and generates an execution plan with parallel stages, agent routing, review gates, and verification criteria. Use before dispatching implementation work. Triggers on "plan execution", "generate execution plan", "how should we execute this", or internally when the orchestrator is about to implement a spec phase.