git:commit

Generate conventional git commits with JIRA ticket enrichment from diffs.

1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/davidarce/devrune-starter-catalog --skill git-commit-davidarce
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git:commit
Source: https://github.com/davidarce/devrune-starter-catalog/tree/main/skills/git-commit
Command: npx skills add https://github.com/davidarce/devrune-starter-catalog --skill git-commit-davidarce

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Creating git commits that follow the Conventional Commits format and embed JIRA context can be error-prone and inconsistent across a team.

Core Features & Use Cases

  • Generate conventional commits from diffs, branches, and user intent
  • Optionally fetch JIRA ticket details to enrich commit messages
  • Detect breaking changes and apply the exclamation mark syntax
  • Determine the correct scope from modified modules (domain, infrastructure, API, etc.)

Quick Start

Create a conventional commit for the current changes, including JIRA context when available.

Frequently Asked Questions about git:commit

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

FAQPage Schema
How do I generate conventional commits automatically from my staged git diff?

Conventional commits are generated automatically by analyzing your local git diff results and branch context. The tool detects modified modules to determine the correct scope, identifies breaking changes to apply exclamation mark syntax, and crafts precise standardized messages.

Can I automatically embed JIRA ticket details into my git commit messages?

JIRA ticket details can be optionally fetched and embedded into your git commit messages. The tool auto-detects available JIRA data based on your branch context and enriches the standardized commit output with the relevant ticket information.

How does automatic scope detection work for conventional commits across different modules?

Automatic scope detection works by analyzing modified modules within your local repository's diff results. It identifies affected areas such as domain, infrastructure, or API layers, and applies the correct scope label to your conventional commit message.

What is the best way to format breaking changes in git commits using the exclamation mark syntax?

Formatting breaking changes with exclamation mark syntax is handled automatically by detecting breaking modifications in your code changes. The tool applies the required conventional commit breaking-change markers to ensure your commit history meets formatting standards.

Does this git commit automation work in a local repository without external dependencies?

This git commit automation operates directly within your local repository environment without requiring external dependencies. It auto-detects branch context and diff results locally, requiring only optional JIRA data availability to enrich commit messages further.