conventional-commit

Name: conventional-commit
Availability: InStock
Author: shysssthanhtri

Generate Conventional Commit messages from staged Git diffs with Jira ticket IDs.

Updated Mar 19, 2026

Search Tags:#automation #git #workflow #jira #github-copilot #conventional-commits #commit-messages

Ready to run

npx skills add https://github.com/shysssthanhtri/AI-tools --skill conventional-commit-shysssthanhtri

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: conventional-commit
Source: https://github.com/shysssthanhtri/AI-tools/tree/main/skills/conventional-commit
Command: npx skills add https://github.com/shysssthanhtri/AI-tools --skill conventional-commit-shysssthanhtri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes guesswork and inconsistency from writing Git commit messages by generating standardized Conventional Commit messages from the actual staged diff and optionally including a Jira ticket ID extracted from the branch name.

Core Features & Use Cases

Staged-diff-based messages: Generates the commit subject, optional body, and footer using only the staged changes as the source of truth.
Branch-aware ticket insertion: Automatically extracts a Jira ticket ID when the branch follows feature/{ticket-id}-ticket-title and inserts it into the subject.
Validation and automatic commit: Enforces allowed Conventional Commit types, suggests/body/footer usage, and runs git commit with the generated message when applicable.

Quick Start

Run the conventional-commit skill to generate a validated Conventional Commit message from your staged changes and automatically commit it.

Frequently Asked Questions about conventional-commit

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

FAQPage Schema

How do I generate conventional commit messages from staged Git changes automatically?▼

To generate conventional commit messages from staged Git changes, this Skill parses your staged diffs to produce a standardized commit subject, optional body, and footer. It then formats the message as XML and executes the git commit automatically.

Can I automatically include a Jira ticket ID in my conventional commit messages?▼

Yes, you can automatically include a Jira ticket ID in conventional commit messages by reading your current branch name. If the branch follows the feature/{ticket-id}-ticket-title pattern, the Skill extracts the ticket ID and inserts it into the commit subject.

How does this approach enforce allowed conventional commit types and message structure?▼

This approach enforces allowed conventional commit types and message structure by validating the generated commit message against established rules before committing. It ensures the subject, body, and footer conform to standard conventional commit specifications.

Do I need a specific branch naming convention to extract Jira ticket IDs for commit messages?▼

Yes, you need a specific branch naming convention to extract Jira ticket IDs for commit messages. The Skill requires branches to follow the feature/{ticket-id}-ticket-title format to successfully parse and insert the Jira ticket ID into the commit subject.

What is the best way to automate consistent commit messages in a local Git workflow?▼

The best way to automate consistent commit messages in a local Git workflow is using a Skill that analyzes staged diffs and branch names. This generates validated conventional commits with optional Jira ticket IDs, ensuring uniform message structure across your project.

How do I use GitHub Copilot to write standardized Git commit messages?▼

To use GitHub Copilot to write standardized Git commit messages, run this Skill after staging your changes. It leverages Copilot to parse the staged diff, validate conventional commit types, and output an XML-formatted message before running the commit.