skills.rest
mattstruble
mattstrubleCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-commit

Analyze git history and staged changes to craft conventional commit messages.

2|1|Updated Mar 8, 2026
Search Tags:#git#workflow#software-engineering#conventional-commits#commit-messages#repo-conventions
One-click install
npx skills add https://github.com/mattstruble/skills --skill git-commit-mattstruble
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/mattstruble/skills/tree/main/git-commit
Command: npx skills add https://github.com/mattstruble/skills --skill git-commit-mattstruble

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Git conventional commits help teams create consistent, meaningful commit messages and plan commits with intent, improving history readability and collaboration.

Core Features & Use Cases

  • Analyze working tree changes and group by intent to craft conventional commit messages that align with repo conventions.
  • Respect local repository conventions by inspecting git history and config to ensure messages follow team standards.
  • Provide guidance for planning, staging, and grouping commits to reflect intent across a project.

Quick Start

Generate conventional commit messages for the current staged changes.

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 commit messages for staged git changes?▼

To generate conventional commit messages, the skill analyzes your staged repository changes and git history to craft appropriate feat, fix, or docs prefixes and scaffolds the commit body.

What are conventional commits and how do they improve git history readability?▼

Conventional commits standardize commit messages using structured prefixes like feat and fix, enforcing consistent project history and improving readability and collaboration across software engineering teams.

Can I use this to plan and group git commits by intent before staging?▼

Yes, you can use this to plan and group git commits by intent, providing guidance on staging changes so that your commits accurately reflect the logical boundaries of your project updates.

Does this respect existing repo conventions when writing commit messages?▼

Yes, it respects existing repo conventions by inspecting your local git history and config to ensure that generated commit messages follow your team's specific formatting standards.

What is the best way to enforce consistent commit messages across a software engineering team?▼

The best way to enforce consistent commit messages is by analyzing working tree changes and repo conventions, then scaffolding structured conventional commit bodies and prefixes that align with team standards.

Why do my git commit messages fail to follow conventional commit standards?▼

Git commit messages fail conventions when not properly grouped by intent, but analyzing git history and applying structured feat, fix, or docs prefixes ensures consistent project history formatting.

Related Skills

Explore More Software Engineering Skills→
kaosnyrbkaosnyrb
12

commit

Stage and commit Git changes with a diff-derived message.

Community
Intermediate
mbelenmontoyambelenmontoya

commit-message-helper

Generate conventional commit messages with project-specific types and scopes.

Community
Basic
queen-of-codequeen-of-code
8

git-workflow

Standardize Git workflows with conventional commits and branch protection rules.

Community
Intermediate
ehtbantonehtbanton

commitlint-config-generator

Generate commitlint configuration files enforcing Conventional Commits 1.0.0 standards.

Community
Basic