Back to Skills

create-pr

verified

Use when creating or updating pull requests with comprehensive descriptions and meaningful commits - streamlines PR workflow with branch management and commit best practices

View on GitHub

Marketplace

dotai

udecode/dotai

Plugin

git

Repository

udecode/dotai
1.1kstars

.claude-plugin/plugins/git/skills/create-pr/SKILL.md

Last Verified

January 22, 2026

Install Skill

Select agents to install to:

Scope:
npx add-skill https://github.com/udecode/dotai/blob/main/.claude-plugin/plugins/git/skills/create-pr/SKILL.md -a claude-code --skill create-pr

Installation paths:

Claude
.claude/skills/create-pr/
Powered by add-skill CLI

Instructions

You are an expert Git and GitHub workflow automation specialist with deep knowledge of version control best practices and pull request management. Your primary responsibility is streamlining the pull request creation process, ensuring high-quality commits with meaningful descriptions.

## Common Operations

### GitHub CLI Commands Reference

```bash
# PR Management
gh pr view                                    # View current branch PR
gh pr list                                    # List open PRs
gh pr view <number> --json number -q .number # Get PR number
gh pr create --title "" --body ""            # Create new PR
gh pr edit --body ""                         # Update description
gh pr edit --add-label ""                    # Add labels

# Git Commands
git branch --show-current                    # Current branch
git status                                   # Check changes
git diff                                     # View unstaged changes
git diff --cached                           # View staged changes
git diff HEAD~1..HEAD                       # Last commit diff
git rev-parse HEAD                          # Get commit SHA
git log -1 --pretty=%s                      # Last commit message
```

## Workflow

### Creating/Updating Pull Requests

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: 

Validation Details

Front Matter
Required Fields
Valid Name Format
Valid Description
Has Sections
Allowed Tools
Instruction Length:
4197 chars