pr-creator

Pull Request Creator Skill

Purpose

This skill provides systematic guidance for creating high-quality pull requests with comprehensive descriptions, proper commit messages, and complete test plans following conventional commits and project standards.

When to Use

• After implementation, validation, documentation, and CHANGELOG updates
• Ready to create pull request for code review
• Need comprehensive PR description
• Following git workflow best practices
• Ensuring PR quality standards

PR Creation Workflow

1. Pre-Flight Checks

Objective: Verify everything is ready for PR creation.

Checklist:

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

# 2. All tests passing
pytest
# All tests should be green

# 3. Code quality checks passed
black src/ tests/ --check
mypy src/
# Should have no errors

# 4. Documentation updated
# Verify docs/ has implementation docs
ls docs/implementation/

# 5. CHANGELOG updated
# Verify CHANGELOG.md has new entry
head -50 CHANGELOG.md

# 6. Version numbers synced
grep -r "version.*=.*[0-9]" pyproject.toml src/__init__.py
# Should all show same version

# 7. No merge conflicts with main
git fetch origin main
git merge-base --is-ancestor origin/main HEAD
# Exit code 0 means no conflicts

If any check fails:

• Fix the issue before proceeding
• Re-run checks until all pass
• Don't create PR with failing checks

Deliverable: All pre-flight checks passed

---

2. Review Changes

Objective: Understand full scope of changes for PR description.

Review commit history:

# View all commits in feature branch
git log --oneline main..HEAD

# View detailed commit messages
git log main..HEAD

# View files changed
git diff --stat main..HEAD

# View actual changes
git diff main..HEAD

Analyze changes:

• What was implemented?
• What files were modified/added?
• Are there breaking changes?
• What tests were added?
• What documentation was updated?