Creating Pr Skill for Claude

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

1k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

320

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/Microck/ordinary-claude-skills --skill creating-pr

What comes with it

631 bytes besides the instruction

metadata.json

The instruction itself

12 sections, as written by the author

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

# 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

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

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

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

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

## 🔄 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

## 🚨 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

## ✨ 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 Patterns

Creating PR:

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

Commit Message Conventions

feat: - New features
fix: - Bug fixes
refactor: - Code refactoring
docs: - Documentation changes
test: - Test additions/modifications
chore: - Maintenance tasks
style: - Formatting changes

Branch Naming Conventions

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

Other skills for the same job

different authors, same section of the catalogue

Receiving Code Review

by ZhanlinCui

×7

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

2k tokens

Requesting Code Review

by ZhanlinCui

×6

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

Comprehensive GitHub code review with AI-powered swarm coordination

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2k tokens

How to use it

Copy the folder

Take microck/creating-pr from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.