commit-pr

Stage changes, create conventional commits, and manage pull requests with git and gh.

888|82|Updated Aug 13, 2025
One-click install
npx skills add https://github.com/videojs/v10 --skill commit-pr-videojs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-pr
Source: https://github.com/videojs/v10/tree/main/.claude/skills/commit-pr
Command: npx skills add https://github.com/videojs/v10 --skill commit-pr-videojs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates staging changes, creating conventional commits, and managing pull requests in line with project conventions, saving time and reducing human error.

Core Features & Use Cases

  • Automated commit workflow: Stage changes, generate a conventional commit message, and push to a feature branch.
  • PR management: Open new pull requests or update existing ones using standardized templates and reference conventions.
  • Workflow integration: Works with git and GitHub CLI to accelerate collaboration in team projects.

Quick Start

Run the commit-pr command to stage changes, commit with a conventional message, push the branch, and create or update a PR.

Frequently Asked Questions about commit-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate creating conventional commits and pull requests?

You can automate staging changes, generating conventional commit messages, and managing pull requests by running the commit-pr command, which inspects git status and git diff to process changes and uses gh to create or update PRs.

How does conventional commit scope inference work from git diff?

Conventional commit scope inference works by analyzing git status and git diff output to detect changed files, then matching those changes against project conventions defined in references/scope.md to generate appropriate scope labels.

Can I use existing project templates for pull request descriptions?

Yes, pull request descriptions are generated using standardized templates loaded from references/pr.md, ensuring every PR follows your project's specific formatting and documentation conventions automatically.

Do I need GitHub CLI installed to manage pull requests with this workflow?

Yes, GitHub CLI (gh) is required because the workflow relies on it directly to create new pull requests or update existing ones on your remote repository after pushing the feature branch.

What's the best way to enforce consistent commit messaging across a team?

Enforcing consistent commit messaging is achieved by automating the commit workflow to generate messages from conventional commit standards, integrating rules from references/commit.md, and inferring scope from git diff to reduce human error.

Why are my staged changes not generating the correct conventional commit type?

Conventional commit types are determined by inspecting git diff and matching the changes against loaded project conventions, so incorrect types typically indicate a mismatch between your actual code changes and the rules defined in references/commit.md.