How do I install the Git Commit Helper skill?

Run npx skillmds@latest add lc-rezende/git-commit-helper 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.

Is Git Commit Helper 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 Helper?

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 Helper free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Git Commit Helper?

lc-rezende (@lc-rezende) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Commit Helper by lc-rezende — Agent Skill

Name: Git Commit Helper
Author: lc-rezende

File contents

Git Commit Helper (No Scope)

Generate conventional commit messages without a scope.

When to use this skill

The user asks for a commit message
Staged changes exist
The user is about to run git commit
The user mentions conventional or semantic commits

Workflow

Review staged files and the staged diff.
Identify the primary change type and any breaking changes.
Draft a commit message using the format below.
Provide a short rationale and ask if the user wants adjustments.

Commit format (no scope)

<type>: <subject>

<body>

<footer>

Types

feat: New feature
fix: Bug fix
docs: Documentation changes
style: Formatting only (no logic change)
refactor: Code restructuring without behavior change
perf: Performance improvements
test: Test additions or fixes
build: Build system or tooling changes
ci: CI/CD pipeline changes
chore: Maintenance tasks

Subject checklist

Imperative mood ("add", "fix", "update")
50-72 characters max
No trailing period
Describes what and why, not how
Lowercase after the type

Breaking changes

If the change is breaking, include a footer:

BREAKING CHANGE: <what changed and how to migrate>

Examples

Feature

feat: add jwt authentication for api requests

- implement token validation middleware
- add login and refresh endpoints

Closes #42

Fix

fix: prevent memory leak in user list

Clean up subscriptions when the component unmounts.

Refactor

refactor: extract repository layer for database access

No functional changes. Improves testability and separation.

Breaking change

feat: update user api response structure

BREAKING CHANGE: response is now { data, metadata }.

Output expectations

Provide the recommended commit message in full.
Explain the chosen type and any breaking change rationale.

---name: git-commit-helperdescription: Generate conventional commit messages without scopes based on staged changes. Use when the user asks for commit message help, has staged changes, or is about to commit.---# Git Commit Helper (No Scope)Generate conventional commit messages without a scope.## When to use this skill- The user asks for a commit message- Staged changes exist- The user is about to run `git commit`- The user mentions conventional or semantic commits## Workflow1. Review staged files and the staged diff.2. Identify the primary change type and any breaking changes.3. Draft a commit message using the format below.4. Provide a short rationale and ask if the user wants adjustments.## Commit format (no scope)```<type>: <subject><body><footer>```## Types- `feat`: New feature- `fix`: Bug fix- `docs`: Documentation changes- `style`: Formatting only (no logic change)- `refactor`: Code restructuring without behavior change- `perf`: Performance improvements- `test`: Test additions or fixes- `build`: Build system or tooling changes- `ci`: CI/CD pipeline changes- `chore`: Maintenance tasks## Subject checklist- Imperative mood ("add", "fix", "update")- 50-72 characters max- No trailing period- Describes what and why, not how- Lowercase after the type## Breaking changesIf the change is breaking, include a footer:```BREAKING CHANGE: <what changed and how to migrate>```## Examples### Feature```feat: add jwt authentication for api requests- implement token validation middleware- add login and refresh endpointsCloses #42```### Fix```fix: prevent memory leak in user listClean up subscriptions when the component unmounts.```### Refactor```refactor: extract repository layer for database accessNo functional changes. Improves testability and separation.```### Breaking change```feat: update user api response structureBREAKING CHANGE: response is now { data, metadata }.```## Output expectations- Provide the recommended commit message in full.- Explain the chosen type and any breaking change rationale.

Frequently asked questions

Git Commit Helper