How do I install the Git Commit skill?

Run npx skillmds@latest add stackloklabs/git-commit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Git Commit skill do?

Write clear, conventional commit messages that communicate changes effectively It is listed under Coding & Dev Tools on SkillMD.

Is Git Commit safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Commit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Git Commit free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Git Commit?

StacklokLabs (@stackloklabs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Commit by stackloklabs — Agent Skill

Name: Git Commit
Author: StacklokLabs

File contents

Git Commit Message Skill

Write commit messages that are clear, consistent, and useful for understanding project history.

Conventional Commits Format

<type>(<scope>): <subject>

<body>

<footer>

Types

Type	Description
`feat`	New feature for users
`fix`	Bug fix for users
`docs`	Documentation changes
`style`	Formatting, missing semicolons, etc.
`refactor`	Code change that neither fixes a bug nor adds a feature
`perf`	Performance improvement
`test`	Adding or updating tests
`build`	Changes to build system or dependencies
`ci`	CI configuration changes
`chore`	Other changes that don't modify src or test files
`revert`	Reverts a previous commit

Scope

Optional. Describes the section of codebase affected:

auth, api, db, ui, config, etc.

Subject Line Rules

Use imperative mood: "add feature" not "added feature"
Don't capitalize first letter
No period at the end
Max 50 characters (72 absolute max)
Complete the sentence: "If applied, this commit will..."

Body Guidelines

Wrap at 72 characters
Explain what and why, not how
Use bullet points for multiple changes
Reference issues when relevant

Footer

BREAKING CHANGE: <description> for breaking changes
Fixes #123 or Closes #456 for issue references
Co-authored-by: Name <email> for pair programming

Examples

Simple Feature

feat(auth): add password reset functionality

Bug Fix with Body

fix(api): handle null response from payment provider

The payment API sometimes returns null instead of an error object
when the service is degraded. This caused unhandled exceptions
in production.

Fixes #892

Breaking Change

feat(api)!: change authentication to use JWT tokens

Migrate from session-based auth to JWT tokens for better
scalability and stateless operation.

BREAKING CHANGE: All API clients must now include JWT token
in Authorization header instead of session cookie.

Documentation

docs: update API reference with rate limiting info

Refactoring

refactor(db): extract query builder into separate module

No functional changes. Improves testability and
reduces coupling between repository and query logic.

Anti-Patterns to Avoid

"WIP" or "work in progress"
"fix stuff" or "updates"
"asdfasdf" or keyboard mashing
Multiple unrelated changes in one commit
Commit messages longer than the code change
"Fixed PR comments"

Git Commands Reference

# Stage specific files
git add <file1> <file2>

# Interactive staging
git add -p

# Commit with message
git commit -m "feat: add new feature"

# Commit with body (opens editor)
git commit

# Amend last commit
git commit --amend

---name: git-commitdescription: Write clear, conventional commit messages that communicate changes effectivelylicense: Apache-2.0---# Git Commit Message SkillWrite commit messages that are clear, consistent, and useful for understanding project history.## Conventional Commits Format```<type>(<scope>): <subject><body><footer>```### Types| Type | Description ||------|-------------|| `feat` | New feature for users || `fix` | Bug fix for users || `docs` | Documentation changes || `style` | Formatting, missing semicolons, etc. || `refactor` | Code change that neither fixes a bug nor adds a feature || `perf` | Performance improvement || `test` | Adding or updating tests || `build` | Changes to build system or dependencies || `ci` | CI configuration changes || `chore` | Other changes that don't modify src or test files || `revert` | Reverts a previous commit |### ScopeOptional. Describes the section of codebase affected:- `auth`, `api`, `db`, `ui`, `config`, etc.### Subject Line Rules1. Use imperative mood: "add feature" not "added feature"2. Don't capitalize first letter3. No period at the end4. Max 50 characters (72 absolute max)5. Complete the sentence: "If applied, this commit will..."### Body Guidelines- Wrap at 72 characters- Explain **what** and **why**, not **how**- Use bullet points for multiple changes- Reference issues when relevant### Footer- `BREAKING CHANGE: <description>` for breaking changes- `Fixes #123` or `Closes #456` for issue references- `Co-authored-by: Name <email>` for pair programming## Examples### Simple Feature```feat(auth): add password reset functionality```### Bug Fix with Body```fix(api): handle null response from payment providerThe payment API sometimes returns null instead of an error objectwhen the service is degraded. This caused unhandled exceptionsin production.Fixes #892```### Breaking Change```feat(api)!: change authentication to use JWT tokensMigrate from session-based auth to JWT tokens for betterscalability and stateless operation.BREAKING CHANGE: All API clients must now include JWT tokenin Authorization header instead of session cookie.```### Documentation```docs: update API reference with rate limiting info```### Refactoring```refactor(db): extract query builder into separate moduleNo functional changes. Improves testability andreduces coupling between repository and query logic.```## Anti-Patterns to Avoid- "WIP" or "work in progress"- "fix stuff" or "updates"- "asdfasdf" or keyboard mashing- Multiple unrelated changes in one commit- Commit messages longer than the code change- "Fixed PR comments"## Git Commands Reference```bash# Stage specific filesgit add <file1> <file2># Interactive staginggit add -p# Commit with messagegit commit -m "feat: add new feature"# Commit with body (opens editor)git commit# Amend last commitgit commit --amend```

Frequently asked questions

Git Commit