pro-commit

Generate commit messages and link them to GitHub issues from branch names.

7|Updated Jun 19, 2025
One-click install
npx skills add https://github.com/Cassiiopeia/projectops --skill pro-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pro-commit
Source: https://github.com/Cassiiopeia/projectops/tree/main/skills/pro-commit
Command: npx skills add https://github.com/Cassiiopeia/projectops --skill pro-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, github-api, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of commit messages and links them to GitHub issues, saving time and reducing errors in the commit process.

Core Features & Use Cases

  • Automated Commit Creation: Automatically generates commit messages based on branch names and GitHub issue numbers.
  • Issue Linking: Links commits to specific GitHub issues for better traceability.
  • Use Case: Imagine you are working on a feature branch and want to automatically create a commit message that includes the issue number you are addressing. This Skill can do that for you.

Quick Start

Use the pro-commit skill to create a commit for your changes in the current branch.

Frequently Asked Questions about pro-commit

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

FAQPage Schema
How do I automate commit message creation and link it to a GitHub issue?

Automate commit message creation by using a tool that extracts GitHub issue numbers from your current branch name via regex and generates a linked commit message automatically. This ensures every commit is traceable to its corresponding issue without manual entry.

How does linking a commit to a GitHub issue from a branch name work?

Linking a commit to a GitHub issue works by parsing the branch name with regular expressions to find the issue number, then passing that reference to the GitHub API. The generated commit message includes this reference to establish the traceability link.

Do I need GitHub API access to automate commit creation and issue linking?

Yes, you need GitHub API access to automate commit creation and issue linking. The API connection is required to validate the issue numbers extracted from your branch names and to successfully link the commits to the GitHub repository.

Can I review automated commit messages before they are created in GitHub?

Yes, you can review automated commit messages before they are created. The automation process supports optional user confirmation, allowing you to verify the generated message and the extracted GitHub issue number before the commit is finalized.

What is the best way to ensure consistent issue linking across multiple feature branches?

The best way to ensure consistent issue linking is to standardize your branch naming convention with issue numbers and use commit automation. The tool extracts the issue number using regex, guaranteeing that every commit across all branches is properly linked to its GitHub issue.

Why are my automated commit messages not linking to the correct GitHub issues?

Automated commit messages may fail to link correctly if the branch name does not contain a recognizable issue number for the regex extraction. Ensure your branch naming convention includes the exact GitHub issue number so the automation can parse and link it properly.