Skip to content
Skills Library
Programming · Writing

pr-creator

/pr-creator

Create comprehensive pull requests with detailed descriptions, test plans, and proper git workflow. Use when finalizing features to ensure high-quality PRs.

Repository
llms ↗
Licence
MIT
Last repository change
21.05.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
4
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 21.05.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Create comprehensive pull requests with detailed descriptions, test plans, and proper git workflow. Use when finalizing features to ensure high-quality PRs.

Original author description

Create comprehensive pull requests with detailed descriptions, test plans, and proper git workflow. Use when finalizing features to ensure high-quality PRs.

How it works

  1. Purpose
  2. When to Use
  3. PR Creation Workflow
  4. PR Templates
  5. Git Workflow
  6. Common Issues
  7. Quick Reference
  8. Related Skills
Original SKILL.md headings · 237 lines, 765 words
SKILL.md preview
---
name: pr-creator
description: Create comprehensive pull requests with detailed descriptions, test plans, and proper git workflow. Use when finalizing features to ensure high-quality PRs.
allowed-tools: Read, Bash, Grep
---

# Pull Request Creator Skill

## Purpose

Systematic guidance for creating high-quality pull requests with comprehensive descriptions and proper commit messages.

## When to Use

- Called by `/ship` after `/pre-commit` passes — standard path
- Directly when you've already committed and pushed manually and need a PR
- Following git workflow best practices

> **Called by `/ship`?** Skip Step 1 (pre-flight). `/pre-commit` already ran. Start at Step 1.5.

## PR Creation Workflow

### 1. Pre-Flight Checks (skip if called by /ship)

```bash
# All changes committed
git status
# Should show: "nothing to commit, working tree clean"

# All tests passing
pytest

# Code quality checks passed
/quality-check

# CHANGELOG updated
head -50 CHANGELOG.md
```

**If any check fails**: Fix before proceeding.

---

### 1.5. Release Artifact Verification

Run `/release verify commits` to check commit↔changelog consistency.

If result is **WARN** or **FAIL**: report the unmatched commits, ask user whether to fix now (run `/release changelog`) or proceed anyway.

Additionally check:

```bash
# Detect version files in the project
for f in pyproject.toml package.json setup.cfg Cargo.toml; do
  [[ -f "$f" ]] && echo "Version file found: $f"
done

# Check for hardcoded version strings in README
grep -n 'v[0-9]\+\.[0-9]\+\.[0-9]\+' README.md 2>/dev/null || echo "No version refs in README"

# Check roadmap
[[ -f ROADMAP.md ]] && echo "ROADMAP.md exists — verify it reflects shipped features"

# Check project-level CLAUDE.md
[[ -f CLAUDE.md ]] && echo "CLAUDE.md exists — verify new features/skills documented"
```

**Checklist (verify each, report missing):**

- [ ] **CHANGELOG.md** — `/release verify commits` PASS or acknowledged WARN
- [ ] **Version files** — if release PR, version bumped in detected files
- [ ] **README.md** — hardcoded version references updated (if any)
- [ ] **ROADMAP.md** — updated if exists and features affect roadmap
- [ ] **Project CLAUDE.md** — reflects new features/skills/rules if applicable

If any item is missing: report clearly, ask user whether to fix now or proceed.

---

### 2. Review Changes

```bash
# Detect base (supports release/* sub-branching)
# Try upstream tracking branch first, then fall back to main
BASE_BRANCH=$(git config "branch.$(git branch --show-current).merge" 2>/dev/null | sed 's|refs/heads/||')
if [[ -z "$BASE_BRANCH" ]]; then
  # No upstream configured — check if branch was created from a release/*
  PARENT=$(git log --oneline --decorate --all --ancestry-path HEAD 2>/dev/null | grep -m1 'origin/release/' | sed 's|.*origin/\(release/[^ ,)]*\).*|\1|')
  BASE_BRANCH="${PARENT:-main}"
fi

# View commits in feature branch
git log --oneline "$BASE_BRANCH"..HEAD

# View files changed
git diff --stat "$BASE_BRANCH"..HEAD
```

---

### 3. Push to Remote

```bash
git push -u origin feature/issue-123-description
```

---

### 4. Create Pull Request

**PR Title Format**: `<type>: <brief description> (#<issue>)`

**Commit Types**: feat, fix, docs, style, refactor, perf, test, chore

**Create PR with gh CLI**:

```bash
gh pr create \
  --title "feat: implement feature (#123)" \
  --body "$(cat <<'EOF'
[PR description from template]
EOF
)"
```

---

## PR Templates

Templates are in `templates/` directory:

- **minimal.md** - Quick fixes, small changes
- **standard.md** - Normal features
- **comprehensive.md** - Major features, complex changes

Choose based on PR scope.

---

### 5. Update Project Tracking

Update TASK.md to mark issue completed with PR link.

---

### 6. Verify PR Quality

```bash
# View PR in browser
gh pr view --web

# Check CI status
gh pr checks
```

**Quality Checklist**:

- [ ] PR title follows conventional commits
- [ ] PR description comprehensive
- [ ] Test coverage details included
- [ ] Breaking changes documented
- [ ] Issue references included (Closes #123)
- [ ] All CI checks passing

---

## Git Workflow

### Branch Naming

`<type>/<issue-number>-<brief-description>`

Examples:

- `feature/123-user-authentication`
- `fix/124-memory-leak`
- `docs/125-api-documentation`

### Keeping Branch Updated

```bash
# Rebase on main
git fetch origin main
git rebase origin/main

# Force push (if already pushed)
git push --force-with-lease
```

---

## Common Issues

### PR too large

Break into smaller PRs, create epic issue for tracking.

### Merge conflicts

```bash
git checkout main && git pull
git checkout feature/123 && git rebase main
# Resolve conflicts
git push --force-with-lease
```

### CI checks failing

```bash
gh pr checks
# Fix issues locally, commit, push
```

---

## Quick Reference

```bash
# Create PR
gh pr create --title "..." --body "..."

# View PR
gh pr view 123

# Edit PR
gh pr edit 123

# Check status
gh pr checks
```

---

## Related Skills

- `/quality-check` - Run before PR
- `/release changelog` - Update CHANGELOG
- `/pre-commit` - Full validation suite
- `/review changes` - Companion review (run before PR)
- `/pr-merge` - Post-PR merge workflow
- `/release plan` - Version planning
Files in this package (4)
  • SKILL.md 5 KB
  • templates/comprehensive.md 3 KB
  • templates/minimal.md 1 KB
  • templates/standard.md 1 KB

Versions

RepositoryScoreLicence
This page · matteocervelli/llms100MIT
mblode/agent-skills100MIT
roselletabuena/skills100MIT
google-gemini/gemini-cli95Apache-2.0
matteocervelli/llms91MIT

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version cc4e7e12894b (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100git-pr
    Create pull requests with descriptions, labels, and issue references. Use when user says "create PR", "open pull request", or "submit for review". From pushed branches.
  • 100git-pr
    Guide for creating effective Pull Requests. Use when opening PRs, writing PR descriptions, requesting reviews, or managing PR workflow.
  • 100ac-git-pull-request
    Creates comprehensive GitHub Pull Requests with authentication validation and structured documentation. Triggers on keywords: pull request, PR, create PR, open PR
  • 100jj-create-pr
    Creates GitHub pull requests from Jujutsu changes with AI-generated descriptions. Use when the user wants to create a PR, push changes for review, or open a pull request.
  • 100create-pr
    Create Pull Requests following best conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review.
  • 100comprehensive-review-pr-enhance
    Create high-quality pull requests with comprehensive descriptions, automated review checks, and a size and structure that keep them easy to review. Use when preparing or improving a pull request.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.