pr

corv89's avatarfrom corv89

Commit changes, bump version, update changelog, and open a PR

⭐6stars🔀0forks📁View on GitHub🕐Updated Dec 29, 2025

When & Why to Use This Skill

This Claude skill automates the end-to-end Git workflow for preparing and submitting code changes. It streamlines developer productivity by handling branch creation, staging files, generating conventional commit messages, managing semantic versioning (patch, minor, major), updating CHANGELOG.md files, and opening Pull Requests via the GitHub CLI. By enforcing standardized practices, it ensures repository consistency and professional project documentation.

Use Cases

  • Automated Feature Submission: Quickly transition from coding to the review phase by automatically creating feature branches and opening descriptive Pull Requests with a single command.
  • Semantic Versioning and Release Prep: Simplify the release process by letting the agent determine the appropriate version bump and update project metadata (like pyproject.toml) and changelogs automatically.
  • Standardized Git Workflow Enforcement: Maintain a clean and professional commit history across a team by automating conventional commit messages and ensuring PR descriptions are consistently formatted and linked to issues.
namepr
descriptionCommit changes, bump version, update changelog, and open a PR

/pr - Prepare and Submit Changes

Purpose

Commit changes to a feature branch, bump version if needed, update changelog, and open a PR.

Before Starting

  • Check for uncommitted changes: git status --porcelain
  • Ensure tests pass: make test or equivalent
  • Confirm current branch (create one if on main)

Process

  1. Create or verify feature branch

    If on main, create a branch from the work context:

    git checkout -b <descriptive-branch-name>
    
  2. Stage and commit changes

    Use the user's git identity (never sign as Claude, no Co-authored-by). Write conventional commit messages:

    • feat: add remote file sync
    • fix: resolve timeout on large files
  3. Bump version if warranted

    • Bug fixes → patch
    • New features → minor
    • Breaking changes → major

    Update version in pyproject.toml (or equivalent).

  4. Update CHANGELOG.md

    Use /changelog skill to generate entry if changes are user-facing.

  5. Push and create PR

    git push -u origin <branch>
    gh pr create --fill
    

    PR description should summarize changes. Link issues if referenced in commits.

Notes

  • Don't add "Signed-off-by" or "Co-authored-by: Claude" trailers
  • Ask before force-pushing
  • If tests fail, stop and report