Does Claude claim authorship of the commits?

No, the skill is explicitly configured not to claim co-authorship, ensuring the user remains fully responsible for the changes.

How does it find the related issue number?

It follows a standard naming convention where development branches are named 'issue- - ', allowing the skill to automatically extract and reference the correct issue.

How does the skill determine which tags to use?

The skill requires a file located at docs/git-msg-tag.md which defines your project's specific tags. If this file is missing, Claude will prompt you to create it.

Can this skill bypass pre-commit hooks?

Bypassing pre-commit hooks is only permitted for 'Milestone' commits on development branches to track progress. 'Delivery' commits must always pass all hooks.

When does the skill generate a full commit message vs. a short one?

A short message is used for delivery commits with small changes. A full commit message with file-by-file descriptions is automatically generated if the changes exceed 20 lines.

Standardized Git Commit Messages

Name: Standardized Git Commit Messages
Author: Synthesys-Lab

bySynthesys-Lab

•

Developer Tools

Automates the creation of structured, meaningful git commit messages following project-specific tagging and milestone conventions.

About

The commit-msg skill streamlines your version control workflow by ensuring every git commit is professional, descriptive, and correctly formatted. It intelligently distinguishes between 'milestone' and 'delivery' commits, automatically extracting issue numbers from branch names and enforcing the use of standardized tags defined in your project's documentation. By providing file-level change descriptions for larger commits and managing pre-commit hook bypasses for work-in-progress milestones, it maintains a clean and searchable repository history without manual overhead.

Key Features

Intelligent distinction between milestone progress and delivery commits
37 GitHub stars
Context-aware issue number extraction from branch naming conventions
Granular file-level change summaries for commits exceeding 20 lines
Automated generation of structured short and full commit messages
Enforcement of custom project tags via git-msg-tags.md integration

Use Cases

Standardizing repository history across distributed development teams
Ensuring compliance with documentation-defined tagging systems
Automating progress tracking on complex features using milestone commits

About

Key Features

Intelligent distinction between milestone progress and delivery commits
37 GitHub stars
Context-aware issue number extraction from branch naming conventions
Granular file-level change summaries for commits exceeding 20 lines
Automated generation of structured short and full commit messages
Enforcement of custom project tags via git-msg-tags.md integration

Use Cases

Standardizing repository history across distributed development teams
Ensuring compliance with documentation-defined tagging systems
Automating progress tracking on complex features using milestone commits