git-commit

Analyze recent Git history to infer commit message conventions.

Updated Dec 15, 2025
One-click install
npx skills add https://github.com/scruffydan/AI-Agents --skill git-commit-scruffydan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/scruffydan/AI-Agents/tree/main/source/skills/git-commit
Command: npx skills add https://github.com/scruffydan/AI-Agents --skill git-commit-scruffydan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams enforce consistent commit messages by deriving the repository's preferred style from historical commits and guiding you to create messages that match that style.

Core Features & Use Cases

  • Analyze recent commit history to detect formatting conventions (types, scopes, capitalization, body usage).
  • Produce commit messages that align with discovered patterns, minimizing drift and improving changelog readability.
  • Use Case: You inherited a project with a custom commit convention; this skill helps you craft new messages that fit the established pattern.

Quick Start

Run the following steps to examine recent history and begin composing messages that fit the repository's conventions:

  • Inspect the last 10 commits: git log -10 --oneline
  • When ready to commit, format messages using the discovered pattern, e.g., git commit -m "type(scope): description" with an appropriate body if needed.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I match my git commit messages to existing repository conventions?

Git commit conventions are detected by inspecting the last 10 commits to infer formatting patterns like type/scope: description. The skill analyzes this history to guide you in crafting messages that match the repository's established style.

How do I automatically format git commit messages based on project history?

Formatting git commit messages based on project history involves inspecting recent commits to extract style patterns such as types and scopes. The skill uses this analysis to produce a ready-to-use commit command and templates that fit the discovered format.

What is the best way to enforce consistent git commit styles without external dependencies?

Enforcing consistent git commit styles without external dependencies is achieved by analyzing recent repository history directly. The skill inspects the last 10 commits to detect custom conventions and provides templates that match those patterns.

Does this approach work with custom git commit conventions?

Yes, this approach works with custom git commit conventions by deriving the repository's preferred style from historical commits. It detects custom formats and guides you to create messages that fit the established pattern.

How many commits does it analyze to detect repository commit conventions?

It analyzes the last 10 commits to detect repository commit conventions. By inspecting this recent history, it identifies formatting patterns like type/scope: description and provides matching commit templates.