commit

Generate descriptive Git commit messages from repository changes with conventional formatting.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/mgoodman60/foremanos --skill commit-mgoodman60
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/mgoodman60/foremanos/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/mgoodman60/foremanos --skill commit-mgoodman60

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers create clear, consistent Git commit messages by auto-generating descriptive text from the repo changes.

Core Features & Use Cases

  • Automated commit message generation: Build meaningful messages from diffs and file changes.
  • Conventional commit support: Aligns messages to standard formats (feat/fix/docs, etc.).
  • Use Case: While working on a feature branch, run this to generate a first-pass commit message, then review and adjust.

Quick Start

Use the commit skill to auto-generate a commit message for the current changes and commit them.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I auto-generate Git commit messages from staged and unstaged changes?

Auto-generating Git commit messages analyzes your repository changes using git status and git diff to build descriptive text. It reads local development workflows across feature branches and applies conventional commit formatting to stage and commit the changes.

What is conventional commit formatting and how does it apply to my feature branch?

Conventional commit formatting standardizes messages using prefixes like feat, fix, and docs. It applies to your feature branch by analyzing unstaged changes and generating a formatted first-pass commit message that you can review and adjust before applying.

Do I need Git installed locally to auto-generate commit messages for version control?

Yes, Git must be installed and accessible locally to generate commit messages. The process uses git status, git diff, and git commit commands to read repository changes and apply conventional commit messages to your local development workflow.

What's the best way to create consistent Git commit messages from repository diffs?

Creating consistent Git commit messages from diffs involves automating descriptive text generation from file changes. This approach builds meaningful messages aligned with conventional commit formats, serving as a first-pass draft for you to review and adjust.

Can I use an automated commit message generator across different feature branches?

Yes, automated commit message generation applies to local development workflows across feature branches. It reads staged or unstaged changes from your repository diffs and generates conventional commit messages regardless of the active branch context.

Why use conventional commits instead of writing manual Git commit messages?

Conventional commits solve the problem of inconsistent Git commit messages by auto-generating descriptive text from repository changes. This standardizes your version control history with feat, fix, and docs prefixes, providing a reviewable first-pass draft.