commit

Generate conventional commit messages with task numbers from branch names.

3|Updated Oct 20, 2025
One-click install
npx skills add https://github.com/mrstroz/claude-code-plugins --skill commit-mrstroz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/mrstroz/claude-code-plugins/tree/main/utils/skills/commit
Command: npx skills add https://github.com/mrstroz/claude-code-plugins --skill commit-mrstroz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of clean, single-line conventional commits, ensuring consistency and saving developers time by automatically detecting task numbers from branch names.

Core Features & Use Cases

  • Automated Commit Message Generation: Creates commit messages following conventional commit standards.
  • Task Number Detection: Automatically extracts Jira or GitHub issue numbers from branch names.
  • Use Case: When you've finished a feature and want to commit your changes, this skill will help you craft a perfect commit message like feat: PROJ-123 add user avatar upload endpoint without manual effort.

Quick Start

Use the commit skill to create a commit message for your staged changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commit messages automatically from my branch name?

You can generate conventional commit messages by using a tool that automatically detects task numbers from your branch name and enforces strict formatting rules for commit types and summaries. This produces clean, single-line messages like `feat: PROJ-123 add endpoint`.

What are conventional commits and how do task numbers fit into the format?

Conventional commits use a structured format with a type prefix, an optional task number, and a summary. This approach enforces strict formatting rules for commit types like `feat` or `fix`, and automatically maps Jira or GitHub issue numbers from your branch into the commit message.

Can I automatically detect Jira or GitHub issue numbers for my git commits?

Yes, automated commit generation tools can detect Jira and GitHub issue number formats directly from your branch names. By parsing the branch reference, they extract the task number and insert it into your conventional commit summary without manual effort.

How do I enforce strict formatting rules for single-line git commits?

To enforce strict formatting for single-line git commits, use a commit generation tool that validates conventional commit standards. It ensures the correct commit type prefix and summary structure are applied, automatically integrating any detected task numbers into the final message.

Does this conventional commit generator support multi-line commit message bodies?

No, this commit generation approach is designed exclusively for single-line conventional commits. It focuses on automating the commit type and summary with task number detection, and does not support generating multi-line bodies or extended descriptions.

Do I need any external dependencies or plugins to automate conventional commits?

No external dependencies or plugins are required to automate these conventional commits. The tool operates independently to parse your branch name, extract Jira or GitHub task numbers, and enforce strict formatting rules for your single-line commit message.