skills.rest
exception-coder
exception-coderCOMMUNITY
Explore all skills by this author →
GitHub

git-commit-standards

Generate standardized commit messages from staged diffs with user confirmation.

6|1|Updated Mar 30, 2026
Search Tags:#git#commit#pre-commit#commit-message#conventional-commits#diff-analysis#author-info
One-click install
npx skills add https://github.com/exception-coder/team-standards --skill git-commit-standards-exception-coder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit-standards
Source: https://github.com/exception-coder/team-standards/tree/main/skills/git-commit-standards
Command: npx skills add https://github.com/exception-coder/team-standards --skill git-commit-standards-exception-coder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many commit messages are written from memory or guesswork and do not reflect the actual staged changes; this leads to unclear history and lowers code review quality. This Skill enforces a repeatable checklist that reads git config and staged diffs, determines type and scope, composes a formatted message, and requires explicit user confirmation before committing.

Core Features & Use Cases

  • Diff-first commit generation: Mandatory inspection of git diff --staged to derive the commit title, type, and scope.
  • Five-step guarded workflow: Automatic checks for Author info, staged content, type/scope analysis, user confirmation, and safe commit execution via HEREDOC.
  • Conventional format & team rules: Produces a standardized commit header, a Chinese explanatory body, and an Author line while forbidding AI signatures or appended metadata.
  • Use Case: Prepare a release or bugfix commit where accuracy and auditability of the commit message are required for code review and changelogs.

Quick Start

Use the git-commit-standards skill to read the staged diff, generate a formatted commit message based on the changes, and request your confirmation before executing the commit.

Frequently Asked Questions about git-commit-standards

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

FAQPage Schema
How do I generate a conventional commit message from a staged diff?▼

To generate a conventional commit message from a staged diff, the skill reads your staged changes, determines the commit type and scope, and creates a formatted message for explicit user confirmation before committing.

Can I automate pre-commit message generation based on actual code changes?▼

You can automate pre-commit message generation by running a guarded workflow that inspects staged content, analyzes the diff, composes a formatted Chinese body, and commits via a HEREDOC without adding external metadata.

Why do my git commit messages not match the staged changes?▼

Git commit messages often mismatch staged changes because they are written from memory rather than diff analysis; reading the staged diff first ensures the commit text accurately reflects actual code modifications.

Does this git commit workflow support feature additions and CI config updates?▼

This git commit workflow supports feature additions, bug fixes, refactors, CI/config updates, and documentation changes by applying standardized formatting rules during the prepare-to-commit and pre-commit phases.

How to ensure my commit history includes author info and avoids AI signatures?▼

To ensure commit history includes author info and avoids AI signatures, the workflow reads git config for the Author line and explicitly forbids appending AI signatures or external metadata to the final commit.

Related Skills

Explore More Software Engineering Skills→
le-goff-benoitle-goff-benoit
2

source_show_commit

Inspect a specific Git commit and analyze its diff, message, author, date, and file changes.

Community
Intermediate
l3ochol3ocho

changelog-format

Parse Conventional Commits and Keep a Changelog formats to generate release notes.

Community
Intermediate
guille-galloguille-gallo

setup-pre-commit

Automate pre-commit hook setup with Husky and lint-staged for Git repositories.

Community
Intermediate
ebknebkn
8

commit

Stage and commit changes with conventional messages and logical grouping.

Community
Intermediate