pr

Original source / Raw SKILL.md

---
name: pr
description: Comprehensive GitHub pull request management - create regular/draft PRs with descriptions and commits, review PRs with severity ratings. Triggers on "create a PR", "make a draft PR", "review PR", or any PR workflow task.
---

Expert Git and GitHub workflow automation with three core operations:

## Operations

1. **Create PR** - Regular PRs with comprehensive descriptions
2. **Draft PR** - WIP PRs without automatic review
3. **Review PR** - Code analysis with severity ratings

## Common GitHub CLI Commands

```bash
# PR info
gh pr view [number]                    # View PR
gh pr list                             # List PRs
gh pr diff [number]                    # Get diff

# PR creation
gh pr create --title "" --body ""      # Regular PR
gh pr create --draft --title "" --body ""  # Draft PR

# PR updates
gh pr edit --body ""                   # Update description
gh pr comment [number] --body ""       # Add comment
gh pr ready [number]                   # Mark draft ready

# Reviews
gh pr review [number] --approve --body ""
gh pr review [number] --request-changes --body ""
gh pr view [number] --comments         # View comments

# Git commands
git branch --show-current              # Current branch
git status                             # Check changes
git diff [--cached]                    # View changes
git log --oneline -n 5                 # Recent commits
```

## Workflow Selection

Determine operation from user request:

- **"Create a PR"** → Read [references/create.md](references/create.md)
- **"Create a draft PR"** or **"Draft PR"** → Read [references/draft.md](references/draft.md)
- **"Review PR"** or **"Review this PR"** → Read [references/review.md](references/review.md)

Each reference file contains complete workflow, templates, and best practices for that operation.

## Branch Naming Conventions

- `feature/description` - New features
- `fix/bug-description` - Bug fixes
- `refactor/component-name` - Code refactoring
- `docs/update-readme` - Documentation
- `test/add-unit-tests` - Test additions

## Commit Message Conventions

- `feat:` - New features
- `fix:` - Bug fixes
- `refactor:` - Code refactoring
- `docs:` - Documentation
- `test:` - Tests
- `chore:` - Maintenance
- `style:` - Formatting


---

## Referenced Files

> The following files are referenced in this skill and included for context.

### references/create.md

```markdown
# Creating Regular Pull Requests

Complete workflow for creating PRs with comprehensive descriptions and meaningful commits.

## Workflow

### 1. Branch Management

- Check current branch: `git branch --show-current`
- If on main/master/next, create feature branch with conventional naming
- Switch to new branch: `git checkout -b branch-name`

### 2. Analyze & Stage

- Review changes: `git status` and `git diff`
- Identify change type (feature, fix, refactor, docs, test, chore)
- Stage ALL changes: `git add .` (preferred due to slow Husky hooks)
- Verify: `git diff --cached`

### 3. Commit & Push

- **Single Commit Strategy**: Use one comprehensive commit per push due to slow Husky hooks
- Format: `type: brief description` (simple format preferred)
- Commit: `git commit -m "type: description"` with average git comment
- Push: `git push -u origin branch-name`

### 4. PR Management

- Check existing: `gh pr view`
- If exists: push updates, **add update comment** (preserve original description)
- If not: `gh pr create` with title and description

## Update Comment Templates

When updating existing PRs, use these comment templates to preserve the original description:

### General PR Update Template

```markdown
## 🔄 PR Update

**Commit**: `<commit-sha>` - `<commit-message>`

### Changes Made

- [List specific changes in this update]
- [Highlight any breaking changes]
- [Note new features or fixes]

### Impact

- [Areas of code affected]
- [Performance/behavior changes]
- [Dependencies updated]

### Testing

- [How to test these changes]
- [Regression testing notes]

### Next Steps

- [Remaining work if any]
- [Items for review focus]

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

### Critical Fix Update Template

```markdown
## 🚨 Critical Fix Applied

**Commit**: `<commit-sha>` - `<commit-message>`

### Issue Addressed

[Description of critical issue fixed]

### Solution

[Technical approach taken]

### Verification Steps

1. [Step to reproduce original issue]
2. [Step to verify fix]
3. [Regression test steps]

### Risk Assessment

- **Impact**: [Low/Medium/High]
- **Scope**: [Files/features affected]
- **Backwards Compatible**: [Yes/No - details if no]

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

### Feature Enhancement Template

```markdown
## ✨ Feature Enhancement

**Commit**: `<commit-sha>` - `<commit-message>`

### Enhancement Details

[Description of feature improvement/addition]

### Technical Implementation

- [Key architectural decisions]
- [New dependencies or patterns]
- [Performance considerations]

### User Experience Impact

[How this affects end users]

### Testing Strategy

[Approach to testing this enhancement]

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

## Example Usage

### Creating PR

1. Create branch and make changes
2. Stage, commit, push → triggers PR creation
3. Each subsequent push triggers update comment

```

### references/draft.md

```markdown
# Creating Draft Pull Requests

Streamline draft PR creation and management for work-in-progress. **Focus**: Create and update draft PRs efficiently without automatic reviews.

## Workflow

### 1. Branch Management

- Check current branch: `git branch --show-current`
- If on main/master/next, create feature branch with conventional naming
- Switch to new branch: `git checkout -b branch-name`

### 2. Analyze & Stage Changes

- Review changes: `git status` and `git diff`
- Identify change type (feature, fix, refactor, docs, test, chore)
- Stage ALL changes: `git add .` (preferred due to slow Husky hooks)
- Verify: `git diff --cached`

### 3. Commit & Push

- **Single Commit Strategy**: Use one comprehensive commit per push due to slow Husky hooks
- Format: `type: brief description` (simple format preferred)
- Commit: `git commit -m "type: description"` with average git comment
- Push: `git push -u origin branch-name`

### 4. Draft PR Management

- Check existing: `gh pr view`
- If exists: push updates, **add update comment** (preserve original description)
- If not: `gh pr create --draft` with comprehensive title and description

## PR Description Template

```markdown
## Summary

[Brief description of what this PR accomplishes]

## Changes Made

- [List key changes made]
- [Include file modifications]
- [Highlight new features/fixes]

## Technical Details

- [Implementation approach]
- [Key architectural decisions]
- [Dependencies added/removed]

## Testing

- [How to test the changes]
- [Test cases covered]
- [Manual testing steps]

## Screenshots/Demo

[If applicable, include screenshots or demo links]

## Checklist

- [ ] Tests pass
- [ ] Documentation updated
- [ ] Ready for review

## Notes

[Any additional context, considerations, or follow-up items]

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

## Update Comment Templates

When updating existing draft PRs, use these comment templates instead of editing the original description:

### New Commit Update Template

```markdown
## 📝 Draft PR Update

**Commit**: `<commit-sha>` - `<commit-message>`

### Changes Made

- [List specific changes in this commit]
- [Highlight new features/fixes added]
- [Note any breaking changes]

### Status

- [Current implementation status]
- [Remaining work items]
- [Any blockers or questions]

### Testing

- [How to test the new changes]
- [Updated test instructions if needed]

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

### Feature Addition Template

```markdown
## ✨ Feature Added

**Commit**: `<commit-sha>` - `<commit-message>`

### New Feature

[Description of the feature added]

### Implementation Details

- [Key technical decisions]
- [Files modified/added]
- [Dependencies changed]

### Testing Instructions

[How to test the new feature]

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

### Bug Fix Template

```markdown
## 🐛 Bug Fix Applied

**Commit**: `<commit-sha>` - `<commit-message>`

### Issue Fixed

[Description of the bug that was fixed]

### Root Cause

[What caused the issue]

### Solution

[How it was resolved]

### Verification

[How to verify the fix works]

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

## Example Usage

### Creating a new draft PR

1. Make changes on feature branch
2. Stage and commit with conventional message
3. Push changes: `git push -u origin feature-branch`
4. Create draft PR: `gh pr create --draft --title "feat: add new feature" --body "$(cat description.md)"`

### Updating existing draft PR

1. Make additional changes
2. Commit and push
3. **Add update comment**: `gh pr comment <pr-number> --body "$(cat update-comment.md)"`
4. Use appropriate template based on change type (feature, fix, general update)

### Making PR ready for review

1. Ensure all changes are complete
2. Run final tests
3. Mark as ready: `gh pr ready`

## Draft PR Best Practices

- **Clear Titles**: Use descriptive, action-oriented titles
- **Comprehensive Descriptions**: Include context, changes, and testing info (preserve original)
- **Progressive Updates**: Keep pushing improvements to the same draft
- **Update Comments**: Add comments for each significant update instead of editing description
- **Change History**: Use update comment templates to track evolution of changes
- **Testing Notes**: Always include how to test the changes (in comments for updates)
- **Screenshots**: Add visuals for UI changes
- **Dependencies**: Note any new packages or breaking changes
- **Preserve Context**: Keep original PR description intact for reference

## Labels and Metadata

Common labels to add:

- `draft` - Work in progress
- `feature` - New functionality
- `bug` - Bug fixes
- `enhancement` - Improvements
- `documentation` - Docs updates
- `breaking-change` - Breaking changes

Use `gh pr edit --add-label "label-name"` to add labels.

```

### references/review.md

```markdown
# Reviewing Pull Requests

For comprehensive PR reviews, use the compound-engineering workflows:review skill which provides exhaustive multi-agent analysis with ultra-thinking and worktrees.

## Quick Review (Use this reference)

For simple, fast PR reviews without the full workflows system:

### GitHub CLI Commands

```bash
# PR Info
gh pr view <number>                          # View PR details
gh pr view <number> --json number,title,body,files  # Get PR metadata
gh pr diff <number>                          # Get full PR diff

# Comments
gh pr view <number> --comments               # View existing comments
gh api repos/{owner}/{repo}/pulls/<number>/comments     # Get inline comments

# Review Actions
gh pr review <number> --approve --body ""    # Approve PR
gh pr review <number> --request-changes --body ""       # Request changes
gh pr review <number> --comment --body ""    # Comment without approval
```

### Simple Review Workflow

1. **Gather Context**:
   ```bash
   gh pr view <number> --json number,title,body,files
   gh pr view <number> --comments  # Check existing feedback
   gh pr diff <number>
   ```

2. **Analyze Changes**:
   - Code correctness and functionality
   - Project conventions and standards
   - Test coverage
   - Security considerations
   - Performance implications

3. **Post Review**:
   ```bash
   gh pr comment <number> --body "Review comments here"
   ```

## Comprehensive Review

For thorough, multi-agent reviews with ultra-thinking:

```bash
/workflows:review
```

This invokes the compound-engineering workflows:review skill which provides:
- Multi-agent parallel analysis
- Ultra-thinking mode for deep reasoning
- Git worktree isolation
- Comprehensive severity ratings
- Detailed recommendations

```