Git commit helper

Skill qyinm/agent-skills-archive/skills/git-commit-helper

Model-agnostic agent skills archive for reusable workflows, references, and scripts across coding assistants.

Install

npx -y skills add qyinm/agent-skills-archive --skill git-commit-helper

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Provides expert guidance for Git commit messages, including conventional commit formatting and best practices. Use when creating or editing Git commit messages.

SKILL.md

2.3 KB, as published. Nobody here has run it

Overview

Provides expert guidance for creating conventional commit messages that follow industry best practices. Helps generate clear, consistent commit messages by analyzing staged changes.

Conventional Commit Format

<type>(<scope>): <description>

[optional body]

[optional footer(s)]

Commit Types

feat: A new feature for the user
fix: A bug fix
docs: Documentation only changes
style: Changes that don't affect code meaning (white-space, formatting, missing semi-colons, etc.)
refactor: Code change that neither fixes a bug nor adds a feature
perf: Code change that improves performance
test: Adding missing tests or correcting existing tests
build: Changes that affect the build system or external dependencies
ci: Changes to CI configuration files and scripts
chore: Other changes that don't modify src or test files
revert: Reverts a previous commit

Rules

Type is mandatory: Choose the most appropriate type from the list above
Scope is optional: Add in parentheses to specify what part of codebase (e.g., feat(auth):, fix(api):)
Description:
- Use imperative mood ("add" not "added" or "adds")
- Don't capitalize first letter
- No period at the end
- Keep under 72 characters
Body is optional: Provide context about what and why, not how
Footer is optional: Reference issues, note breaking changes

Examples

Simple commit

feat: add user authentication

With scope

fix(auth): prevent token expiration on refresh

With body

refactor(api): restructure endpoint handlers

Move handler logic into separate service layer to improve
testability and maintain single responsibility principle.

Breaking change

feat(api): change authentication response format

BREAKING CHANGE: API now returns user object instead of just token.
Update all API consumers to handle new response structure.

Multiple footers

fix(database): resolve connection pool exhaustion

Fixes #123
Closes #456