Name: create-pr
Author: asabocinski

Prompt file imported from asabocinski/bravo-edd (.codex/prompts/create-pr.md). Copyright stays with the author.

Create PR Command

Automate professional pull request creation with conventional commits and structured descriptions

Usage

/create-pr                           # Auto-detect changes and create PR
/create-pr "feat: add user auth"     # Create PR with custom title
/create-pr --draft                   # Create as draft PR
/create-pr --review                  # Run dual AI review before PR creation
/create-pr --review --draft          # Review + create as draft

Pre-PR Review Option

When using --review, the command runs a dual AI review (CodeRabbit + Claude) before creating the PR:

┌─────────────────────────────────────────────────────────────────┐
│                  /create-pr --review WORKFLOW                    │
├─────────────────────────────────────────────────────────────────┤
│                                                                  │
│   1. Analyze Changes                                             │
│          ↓                                                       │
│   2. Run CodeRabbit CLI (static analysis)                       │
│          ↓                                                       │
│   3. Run Claude Review (architectural)                          │
│          ↓                                                       │
│   4. Check for Critical Issues                                  │
│          ↓                                                       │
│   ┌──────┴──────┐                                               │
│   │             │                                                │
│   ▼             ▼                                                │
│ Critical     No Critical                                         │
│ Issues       Issues                                              │
│   │             │                                                │
│   ▼             ▼                                                │
│ STOP &       Continue                                            │
│ Show         to PR                                               │
│ Issues       Creation                                            │
│                                                                  │
└─────────────────────────────────────────────────────────────────┘

Review Behavior

Review Result	Action
🔴 Critical issues found	Stop and show issues, do not create PR
🟠 Errors found	Warn user, ask to continue or fix
🟡 Warnings only	Continue to PR, include warnings in description
✅ Clean	Continue to PR

Review Integration

# Run CodeRabbit + Claude review
source ~/.zshrc && coderabbit review --plain 2>&1

# Parse results and check for blockers
# If critical issues: STOP
# If errors: ASK user
# Otherwise: CONTINUE

Overview

This command streamlines PR creation by:

Analyzing all staged/unstaged changes
Categorizing changes by type (feat/fix/refactor/docs)
Generating conventional commit messages
Building structured PR descriptions with test plans
Creating the PR via GitHub CLI

Process

Step 1: Analyze Changes

# Run these commands to understand the change scope
git status
git diff --stat
git log origin/main..HEAD --oneline

Categorize files into change types:

CHANGE CATEGORIES
═════════════════

feat:     New features, capabilities
fix:      Bug fixes, error corrections
refactor: Code restructuring, no behavior change
docs:     Documentation only
test:     Test additions or corrections
chore:    Build, CI/CD, dependencies
style:    Formatting, whitespace
perf:     Performance improvements

Step 2: Determine PR Type

Based on file analysis, identify the primary change type:

Files Changed	Likely Type
`src/*/.py` + new functionality	`feat:`
`src/*/.py` + bug fix	`fix:`
`src/*/.py` + restructure	`refactor:`
`.md`, `docs/*`	`docs:`
`tests/*`, `_test.py`	`test:`
`.github/**`, `Makefile`, `pyproject.toml`	`chore:`
`.codex/skills/**`	`refactor(agents):`
`.codex/kb/**`	`docs(kb):`
`.codex/sdd/**`	`docs(sdd):`

Step 3: Generate Commit Message

Use Conventional Commits format:

<type>(<scope>): <short description>

<body - what changed and why>

Co-Authored-By: Claude <noreply@anthropic.com>

Examples:

feat(auth): add OAuth2 token refresh flow

- Implement OAuth2 token refresh with PKCE
- Add backward compatibility for session-based auth
- Update validation rules for new token format

Co-Authored-By: Claude <noreply@anthropic.com>

Step 4: Ask Clarifying Questions

Use AskUserQuestion to confirm:

Question 1: PR Type

Does this categorization look correct?
Options: feat, fix, refactor, docs, test, chore

Question 2: Scope

What component/area does this affect?
Options: Based on detected file paths (e.g., parser, agents, kb, api)

Question 3: Breaking Changes

Are there any breaking changes?
Options: Yes (describe), No

Question 4: Related Issues

Link to any related issues?
(Open text - e.g., "Closes #123")

Step 5: Build PR Description

Generate structured description following this template:

## Summary

{2-3 bullet points describing the change}

### Key Changes
- {Primary change 1}
- {Primary change 2}
- {Primary change 3}

## What's Changed

### {Category 1}
{Description of changes in this category}

### {Category 2}
{Description of changes in this category}

## Files Changed

| Category | Files | Description |
|----------|-------|-------------|
| {cat1} | {count} | {brief description} |
| {cat2} | {count} | {brief description} |

## Test Plan

- [ ] {Test case 1}
- [ ] {Test case 2}
- [ ] {Test case 3}

## Breaking Changes

{Describe breaking changes or "None"}

## Related Issues

{Closes #XXX or "None"}

---

Generated with [Claude Code](https://claude.ai/code)

Step 6: Create Branch (if needed)

# If on main, create feature branch
git checkout -b <type>/<short-description>

# Examples:
git checkout -b feat/user-authentication
git checkout -b fix/parser-null-handling
git checkout -b refactor/agents-standardization

Step 7: Commit and Push

# Stage all changes (or specific files)
git add -A

# Commit with conventional message
git commit -m "<message>"

# Push with upstream tracking
git push -u origin <branch-name>

Step 8: Create PR

gh pr create \
  --title "<type>(<scope>): <description>" \
  --body "<generated-body>" \
  --base main

For draft PRs:

gh pr create --draft ...

Output

Branch: <type>/<short-description>
Commit: Conventional commit format
PR URL: Returned from gh pr create

Quality Checklist

Before creating PR, verify:

COMMIT MESSAGE
[ ] Uses conventional commits format
[ ] Type matches the primary change
[ ] Scope is specific and meaningful
[ ] Description is concise (< 72 chars)

PR DESCRIPTION
[ ] Summary explains WHY not just WHAT
[ ] Files changed table is accurate
[ ] Test plan has actionable items
[ ] Breaking changes documented (if any)

BRANCH
[ ] Branch name matches convention
[ ] Not committing directly to main
[ ] All changes are staged

Conventional Commits Reference

Type	When to Use	Example
`feat`	New feature	`feat(api): add user endpoint`
`fix`	Bug fix	`fix(parser): handle null dates`
`refactor`	Code restructure	`refactor(auth): extract token service`
`docs`	Documentation	`docs(readme): add setup instructions`
`test`	Tests	`test(parser): add edge case coverage`
`chore`	Maintenance	`chore(deps): update dependencies`
`style`	Formatting	`style: apply black formatting`
`perf`	Performance	`perf(query): add index for lookups`
`ci`	CI/CD	`ci: add github actions workflow`
`build`	Build system	`build: update dockerfile`

Scopes for this project:

Scope	Applies To
`agents`	`.codex/skills/**`
`kb`	`.codex/kb/**`
`sdd`	`.codex/sdd/**`
`commands`	`.codex/prompts/**`
`handlers`	`src/handlers/**`
`services`	`src/services/**`
`api`	`src/api/**`
`infra`	`terraform/`, `infrastructure/`
`ci`	`.github/**`

Examples

Example 1: Feature PR

/create-pr

# Detected: New files in src/handlers/
# Suggested: feat(auth): add OAuth2 refresh support

→ Created branch: feat/oauth2-refresh
→ Committed: feat(auth): add OAuth2 token refresh
→ PR: https://github.com/org/repo/pull/42

Example 2: Refactor PR

/create-pr "refactor(agents): standardize agent definitions"

→ Created branch: refactor/agents-standardization
→ Committed: refactor(agents): standardize agent definitions
→ PR: https://github.com/org/repo/pull/43

Example 3: Documentation PR

/create-pr --draft

# Detected: Changes in .codex/kb/
# Suggested: docs(kb): add redis caching patterns

→ Created branch: docs/kb-redis-patterns
→ Committed: docs(kb): add redis caching patterns
→ Draft PR: https://github.com/org/repo/pull/44

Example 4: PR with Pre-Review

/create-pr --review

# Running CodeRabbit analysis...
# ✅ No critical issues
# ⚠️ 2 warnings (code style)
#
# Running Claude deep review...
# ✅ Architecture looks good
# ⚠️ Consider adding type hints to new functions
#
# Proceeding to PR creation...

→ Created branch: feat/new-feature
→ Committed: feat(api): add new endpoint
→ PR: https://github.com/org/repo/pull/45

# PR description includes review summary

Tips

Keep PRs Small — Aim for < 400 lines changed
One Concern Per PR — Don't mix features with refactors
Write for Reviewers — Assume they don't know the context
Link Issues — Use "Closes #XX" to auto-close issues
Test Plan Matters — Reviewers should know how to verify

Review Command: .codex/prompts/review/review.md
Code Reviewer Agent: .codex/skills/python/code-reviewer.md
Workflow: .codex/sdd/_index.md
Agents: .codex/skills/

Install create-pr and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# Create PR Command > Automate professional pull request creation with conventional commits and structured descriptions ## Usage ```bash /create-pr # Auto-detect changes and create PR /create-pr "feat: add user auth" # Create PR with custom title /create-pr --draft # Create as draft PR /create-pr --review # Run dual AI review before PR creation /create-pr --review --draft # Review + create as draft ``` --- ## Pre-PR Review Option When using `--review`, the command runs a **dual AI review** (CodeRabbit + Claude) before creating the PR: ```text ┌─────────────────────────────────────────────────────────────────┐ │ /create-pr --review WORKFLOW │ ├─────────────────────────────────────────────────────────────────┤ │ │ │ 1. Analyze Changes │ │ ↓ │ │ 2. Run CodeRabbit CLI (static analysis) │ │ ↓ │ │ 3. Run Claude Review (architectural) │ │ ↓ │ │ 4. Check for Critical Issues │ │ ↓ │ │ ┌──────┴──────┐ │ │ │ │ │ │ ▼ ▼ │ │ Critical No Critical │ │ Issues Issues │ │ │ │ │ │ ▼ ▼ │ │ STOP & Continue │ │ Show to PR │ │ Issues Creation │ │ │ └─────────────────────────────────────────────────────────────────┘ ``` ### Review Behavior | Review Result | Action | |---------------|--------| | 🔴 Critical issues found | Stop and show issues, do not create PR | | 🟠 Errors found | Warn user, ask to continue or fix | | 🟡 Warnings only | Continue to PR, include warnings in description | | ✅ Clean | Continue to PR | ### Review Integration ```bash # Run CodeRabbit + Claude review source ~/.zshrc && coderabbit review --plain 2>&1 # Parse results and check for blockers # If critical issues: STOP # If errors: ASK user # Otherwise: CONTINUE ``` --- ## Overview This command streamlines PR creation by: 1. **Analyzing** all staged/unstaged changes 2. **Categorizing** changes by type (feat/fix/refactor/docs) 3. **Generating** conventional commit messages 4. **Building** structured PR descriptions with test plans 5. **Creating** the PR via GitHub CLI --- ## Process ### Step 1: Analyze Changes ```bash # Run these commands to understand the change scope git status git diff --stat git log origin/main..HEAD --oneline ``` Categorize files into change types: ```text CHANGE CATEGORIES ═════════════════ feat: New features, capabilities fix: Bug fixes, error corrections refactor: Code restructuring, no behavior change docs: Documentation only test: Test additions or corrections chore: Build, CI/CD, dependencies style: Formatting, whitespace perf: Performance improvements ``` ### Step 2: Determine PR Type Based on file analysis, identify the primary change type: | Files Changed | Likely Type | |---------------|-------------| | `src/**/*.py` + new functionality | `feat:` | | `src/**/*.py` + bug fix | `fix:` | | `src/**/*.py` + restructure | `refactor:` | | `*.md`, `docs/**` | `docs:` | | `tests/**`, `*_test.py` | `test:` | | `.github/**`, `Makefile`, `pyproject.toml` | `chore:` | | `.codex/skills/**` | `refactor(agents):` | | `.codex/kb/**` | `docs(kb):` | | `.codex/sdd/**` | `docs(sdd):` | ### Step 3: Generate Commit Message Use Conventional Commits format: ```text <type>(<scope>): <short description> <body - what changed and why> Co-Authored-By: Claude <noreply@anthropic.com> ``` **Examples:** ```text feat(auth): add OAuth2 token refresh flow - Implement OAuth2 token refresh with PKCE - Add backward compatibility for session-based auth - Update validation rules for new token format Co-Authored-By: Claude <noreply@anthropic.com> ``` ### Step 4: Ask Clarifying Questions Use AskUserQuestion to confirm: **Question 1: PR Type** - Does this categorization look correct? - Options: feat, fix, refactor, docs, test, chore **Question 2: Scope** - What component/area does this affect? - Options: Based on detected file paths (e.g., parser, agents, kb, api) **Question 3: Breaking Changes** - Are there any breaking changes? - Options: Yes (describe), No **Question 4: Related Issues** - Link to any related issues? - (Open text - e.g., "Closes #123") ### Step 5: Build PR Description Generate structured description following this template: ```markdown ## Summary {2-3 bullet points describing the change} ### Key Changes - {Primary change 1} - {Primary change 2} - {Primary change 3} ## What's Changed ### {Category 1} {Description of changes in this category} ### {Category 2} {Description of changes in this category} ## Files Changed | Category | Files | Description | |----------|-------|-------------| | {cat1} | {count} | {brief description} | | {cat2} | {count} | {brief description} | ## Test Plan - [ ] {Test case 1} - [ ] {Test case 2} - [ ] {Test case 3} ## Breaking Changes {Describe breaking changes or "None"} ## Related Issues {Closes #XXX or "None"} --- Generated with [Claude Code](https://claude.ai/code) ``` ### Step 6: Create Branch (if needed) ```bash # If on main, create feature branch git checkout -b <type>/<short-description> # Examples: git checkout -b feat/user-authentication git checkout -b fix/parser-null-handling git checkout -b refactor/agents-standardization ``` ### Step 7: Commit and Push ```bash # Stage all changes (or specific files) git add -A # Commit with conventional message git commit -m "<message>" # Push with upstream tracking git push -u origin <branch-name> ``` ### Step 8: Create PR ```bash gh pr create \ --title "<type>(<scope>): <description>" \ --body "<generated-body>" \ --base main ``` For draft PRs: ```bash gh pr create --draft ... ``` --- ## Output - **Branch:** `<type>/<short-description>` - **Commit:** Conventional commit format - **PR URL:** Returned from `gh pr create` --- ## Quality Checklist Before creating PR, verify: ```text COMMIT MESSAGE [ ] Uses conventional commits format [ ] Type matches the primary change [ ] Scope is specific and meaningful [ ] Description is concise (< 72 chars) PR DESCRIPTION [ ] Summary explains WHY not just WHAT [ ] Files changed table is accurate [ ] Test plan has actionable items [ ] Breaking changes documented (if any) BRANCH [ ] Branch name matches convention [ ] Not committing directly to main [ ] All changes are staged ``` --- ## Conventional Commits Reference | Type | When to Use | Example | |------|-------------|---------| | `feat` | New feature | `feat(api): add user endpoint` | | `fix` | Bug fix | `fix(parser): handle null dates` | | `refactor` | Code restructure | `refactor(auth): extract token service` | | `docs` | Documentation | `docs(readme): add setup instructions` | | `test` | Tests | `test(parser): add edge case coverage` | | `chore` | Maintenance | `chore(deps): update dependencies` | | `style` | Formatting | `style: apply black formatting` | | `perf` | Performance | `perf(query): add index for lookups` | | `ci` | CI/CD | `ci: add github actions workflow` | | `build` | Build system | `build: update dockerfile` | **Scopes for this project:** | Scope | Applies To | |-------|------------| | `agents` | `.codex/skills/**` | | `kb` | `.codex/kb/**` | | `sdd` | `.codex/sdd/**` | | `commands` | `.codex/prompts/**` | | `handlers` | `src/handlers/**` | | `services` | `src/services/**` | | `api` | `src/api/**` | | `infra` | `terraform/**`, `infrastructure/**` | | `ci` | `.github/**` | --- ## Examples ### Example 1: Feature PR ```bash /create-pr # Detected: New files in src/handlers/ # Suggested: feat(auth): add OAuth2 refresh support → Created branch: feat/oauth2-refresh → Committed: feat(auth): add OAuth2 token refresh → PR: https://github.com/org/repo/pull/42 ``` ### Example 2: Refactor PR ```bash /create-pr "refactor(agents): standardize agent definitions" → Created branch: refactor/agents-standardization → Committed: refactor(agents): standardize agent definitions → PR: https://github.com/org/repo/pull/43 ``` ### Example 3: Documentation PR ```bash /create-pr --draft # Detected: Changes in .codex/kb/ # Suggested: docs(kb): add redis caching patterns → Created branch: docs/kb-redis-patterns → Committed: docs(kb): add redis caching patterns → Draft PR: https://github.com/org/repo/pull/44 ``` ### Example 4: PR with Pre-Review ```bash /create-pr --review # Running CodeRabbit analysis... # ✅ No critical issues # ⚠️ 2 warnings (code style) # # Running Claude deep review... # ✅ Architecture looks good # ⚠️ Consider adding type hints to new functions # # Proceeding to PR creation... → Created branch: feat/new-feature → Committed: feat(api): add new endpoint → PR: https://github.com/org/repo/pull/45 # PR description includes review summary ``` --- ## Tips 1. **Keep PRs Small** — Aim for < 400 lines changed 2. **One Concern Per PR** — Don't mix features with refactors 3. **Write for Reviewers** — Assume they don't know the context 4. **Link Issues** — Use "Closes #XX" to auto-close issues 5. **Test Plan Matters** — Reviewers should know how to verify --- ## Related - Review Command: `.codex/prompts/review/review.md` - Code Reviewer Agent: `.codex/skills/python/code-reviewer.md` - Workflow: `.codex/sdd/_index.md` - Agents: `.codex/skills/`

{ "prompt": "# Create PR Command\n\n> Automate professional pull request creation with conventional commits and structured descriptions\n\n## Usage\n\n```bash\n/create-pr # Auto-detect changes and create PR\n/create-pr \"feat: add user auth\" # Create PR with custom title\n/create-pr --draft # Create as draft PR\n/create-pr --review # Run dual AI review before PR creation\n/create-pr --review --draft # Review + create as draft\n```\n\n---\n\n## Pre-PR Review Option\n\nWhen using `--review`, the command runs a **dual AI review** (CodeRabbit + Claude) before creating the PR:\n\n```text\n┌─────────────────────────────────────────────────────────────────┐\n│ /create-pr --review WORKFLOW │\n├─────────────────────────────────────────────────────────────────┤\n│ │\n│ 1. Analyze Changes │\n│ ↓ │\n│ 2. Run CodeRabbit CLI (static analysis) │\n│ ↓ │\n│ 3. Run Claude Review (architectural) │\n│ ↓ │\n│ 4. Check for Critical Issues │\n│ ↓ │\n│ ┌──────┴──────┐ │\n│ │ │ │\n│ ▼ ▼ │\n│ Critical No Critical │\n│ Issues Issues │\n│ │ │ │\n│ ▼ ▼ │\n│ STOP & Continue │\n│ Show to PR │\n│ Issues Creation │\n│ │\n└─────────────────────────────────────────────────────────────────┘\n```\n\n### Review Behavior\n\n| Review Result | Action |\n|---------------|--------|\n| 🔴 Critical issues found | Stop and show issues, do not create PR |\n| 🟠 Errors found | Warn user, ask to continue or fix |\n| 🟡 Warnings only | Continue to PR, include warnings in description |\n| ✅ Clean | Continue to PR |\n\n### Review Integration\n\n```bash\n# Run CodeRabbit + Claude review\nsource ~/.zshrc && coderabbit review --plain 2>&1\n\n# Parse results and check for blockers\n# If critical issues: STOP\n# If errors: ASK user\n# Otherwise: CONTINUE\n```\n\n---\n\n## Overview\n\nThis command streamlines PR creation by:\n\n1. **Analyzing** all staged/unstaged changes\n2. **Categorizing** changes by type (feat/fix/refactor/docs)\n3. **Generating** conventional commit messages\n4. **Building** structured PR descriptions with test plans\n5. **Creating** the PR via GitHub CLI\n\n---\n\n## Process\n\n### Step 1: Analyze Changes\n\n```bash\n# Run these commands to understand the change scope\ngit status\ngit diff --stat\ngit log origin/main..HEAD --oneline\n```\n\nCategorize files into change types:\n\n```text\nCHANGE CATEGORIES\n═════════════════\n\nfeat: New features, capabilities\nfix: Bug fixes, error corrections\nrefactor: Code restructuring, no behavior change\ndocs: Documentation only\ntest: Test additions or corrections\nchore: Build, CI/CD, dependencies\nstyle: Formatting, whitespace\nperf: Performance improvements\n```\n\n### Step 2: Determine PR Type\n\nBased on file analysis, identify the primary change type:\n\n| Files Changed | Likely Type |\n|---------------|-------------|\n| `src/**/*.py` + new functionality | `feat:` |\n| `src/**/*.py` + bug fix | `fix:` |\n| `src/**/*.py` + restructure | `refactor:` |\n| `*.md`, `docs/**` | `docs:` |\n| `tests/**`, `*_test.py` | `test:` |\n| `.github/**`, `Makefile`, `pyproject.toml` | `chore:` |\n| `.codex/skills/**` | `refactor(agents):` |\n| `.codex/kb/**` | `docs(kb):` |\n| `.codex/sdd/**` | `docs(sdd):` |\n\n### Step 3: Generate Commit Message\n\nUse Conventional Commits format:\n\n```text\n<type>(<scope>): <short description>\n\n<body - what changed and why>\n\nCo-Authored-By: Claude <noreply@anthropic.com>\n```\n\n**Examples:**\n\n```text\nfeat(auth): add OAuth2 token refresh flow\n\n- Implement OAuth2 token refresh with PKCE\n- Add backward compatibility for session-based auth\n- Update validation rules for new token format\n\nCo-Authored-By: Claude <noreply@anthropic.com>\n```\n\n### Step 4: Ask Clarifying Questions\n\nUse AskUserQuestion to confirm:\n\n**Question 1: PR Type**\n- Does this categorization look correct?\n- Options: feat, fix, refactor, docs, test, chore\n\n**Question 2: Scope**\n- What component/area does this affect?\n- Options: Based on detected file paths (e.g., parser, agents, kb, api)\n\n**Question 3: Breaking Changes**\n- Are there any breaking changes?\n- Options: Yes (describe), No\n\n**Question 4: Related Issues**\n- Link to any related issues?\n- (Open text - e.g., \"Closes #123\")\n\n### Step 5: Build PR Description\n\nGenerate structured description following this template:\n\n```markdown\n## Summary\n\n{2-3 bullet points describing the change}\n\n### Key Changes\n- {Primary change 1}\n- {Primary change 2}\n- {Primary change 3}\n\n## What's Changed\n\n### {Category 1}\n{Description of changes in this category}\n\n### {Category 2}\n{Description of changes in this category}\n\n## Files Changed\n\n| Category | Files | Description |\n|----------|-------|-------------|\n| {cat1} | {count} | {brief description} |\n| {cat2} | {count} | {brief description} |\n\n## Test Plan\n\n- [ ] {Test case 1}\n- [ ] {Test case 2}\n- [ ] {Test case 3}\n\n## Breaking Changes\n\n{Describe breaking changes or \"None\"}\n\n## Related Issues\n\n{Closes #XXX or \"None\"}\n\n---\n\nGenerated with [Claude Code](https://claude.ai/code)\n```\n\n### Step 6: Create Branch (if needed)\n\n```bash\n# If on main, create feature branch\ngit checkout -b <type>/<short-description>\n\n# Examples:\ngit checkout -b feat/user-authentication\ngit checkout -b fix/parser-null-handling\ngit checkout -b refactor/agents-standardization\n```\n\n### Step 7: Commit and Push\n\n```bash\n# Stage all changes (or specific files)\ngit add -A\n\n# Commit with conventional message\ngit commit -m \"<message>\"\n\n# Push with upstream tracking\ngit push -u origin <branch-name>\n```\n\n### Step 8: Create PR\n\n```bash\ngh pr create \\\n --title \"<type>(<scope>): <description>\" \\\n --body \"<generated-body>\" \\\n --base main\n```\n\nFor draft PRs:\n```bash\ngh pr create --draft ...\n```\n\n---\n\n## Output\n\n- **Branch:** `<type>/<short-description>`\n- **Commit:** Conventional commit format\n- **PR URL:** Returned from `gh pr create`\n\n---\n\n## Quality Checklist\n\nBefore creating PR, verify:\n\n```text\nCOMMIT MESSAGE\n[ ] Uses conventional commits format\n[ ] Type matches the primary change\n[ ] Scope is specific and meaningful\n[ ] Description is concise (< 72 chars)\n\nPR DESCRIPTION\n[ ] Summary explains WHY not just WHAT\n[ ] Files changed table is accurate\n[ ] Test plan has actionable items\n[ ] Breaking changes documented (if any)\n\nBRANCH\n[ ] Branch name matches convention\n[ ] Not committing directly to main\n[ ] All changes are staged\n```\n\n---\n\n## Conventional Commits Reference\n\n| Type | When to Use | Example |\n|------|-------------|---------|\n| `feat` | New feature | `feat(api): add user endpoint` |\n| `fix` | Bug fix | `fix(parser): handle null dates` |\n| `refactor` | Code restructure | `refactor(auth): extract token service` |\n| `docs` | Documentation | `docs(readme): add setup instructions` |\n| `test` | Tests | `test(parser): add edge case coverage` |\n| `chore` | Maintenance | `chore(deps): update dependencies` |\n| `style` | Formatting | `style: apply black formatting` |\n| `perf` | Performance | `perf(query): add index for lookups` |\n| `ci` | CI/CD | `ci: add github actions workflow` |\n| `build` | Build system | `build: update dockerfile` |\n\n**Scopes for this project:**\n\n| Scope | Applies To |\n|-------|------------|\n| `agents` | `.codex/skills/**` |\n| `kb` | `.codex/kb/**` |\n| `sdd` | `.codex/sdd/**` |\n| `commands` | `.codex/prompts/**` |\n| `handlers` | `src/handlers/**` |\n| `services` | `src/services/**` |\n| `api` | `src/api/**` |\n| `infra` | `terraform/**`, `infrastructure/**` |\n| `ci` | `.github/**` |\n\n---\n\n## Examples\n\n### Example 1: Feature PR\n\n```bash\n/create-pr\n\n# Detected: New files in src/handlers/\n# Suggested: feat(auth): add OAuth2 refresh support\n\n→ Created branch: feat/oauth2-refresh\n→ Committed: feat(auth): add OAuth2 token refresh\n→ PR: https://github.com/org/repo/pull/42\n```\n\n### Example 2: Refactor PR\n\n```bash\n/create-pr \"refactor(agents): standardize agent definitions\"\n\n→ Created branch: refactor/agents-standardization\n→ Committed: refactor(agents): standardize agent definitions\n→ PR: https://github.com/org/repo/pull/43\n```\n\n### Example 3: Documentation PR\n\n```bash\n/create-pr --draft\n\n# Detected: Changes in .codex/kb/\n# Suggested: docs(kb): add redis caching patterns\n\n→ Created branch: docs/kb-redis-patterns\n→ Committed: docs(kb): add redis caching patterns\n→ Draft PR: https://github.com/org/repo/pull/44\n```\n\n### Example 4: PR with Pre-Review\n\n```bash\n/create-pr --review\n\n# Running CodeRabbit analysis...\n# ✅ No critical issues\n# ⚠️ 2 warnings (code style)\n#\n# Running Claude deep review...\n# ✅ Architecture looks good\n# ⚠️ Consider adding type hints to new functions\n#\n# Proceeding to PR creation...\n\n→ Created branch: feat/new-feature\n→ Committed: feat(api): add new endpoint\n→ PR: https://github.com/org/repo/pull/45\n\n# PR description includes review summary\n```\n\n---\n\n## Tips\n\n1. **Keep PRs Small** — Aim for < 400 lines changed\n2. **One Concern Per PR** — Don't mix features with refactors\n3. **Write for Reviewers** — Assume they don't know the context\n4. **Link Issues** — Use \"Closes #XX\" to auto-close issues\n5. **Test Plan Matters** — Reviewers should know how to verify\n\n---\n\n## Related\n\n- Review Command: `.codex/prompts/review/review.md`\n- Code Reviewer Agent: `.codex/skills/python/code-reviewer.md`\n- Workflow: `.codex/sdd/_index.md`\n- Agents: `.codex/skills/`", "variables": [], "notes": "Create pull request with conventional commits and structured descriptions", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/asabocinski/bravo-edd", "path": ".codex/prompts/create-pr.md", "ref": "ae4c539580470e782ac67d2dc4a4eabe9fc68336", "url": "https://github.com/asabocinski/bravo-edd/blob/ae4c539580470e782ac67d2dc4a4eabe9fc68336/.codex/prompts/create-pr.md", "key": "asabocinski/bravo-edd/.codex/prompts/create-pr.md" } } }

create-pr

About