Git commit helper

Skill lc-rezende/AI-Custom-Skills/skills/git-commit-helper

A repository containing a variety of custom AI Skills crafted to make our life easier.

Install

npx -y skills add lc-rezende/AI-Custom-Skills --skill git-commit-helper

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

One thing to look at

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

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.

SKILL.md

2.1 KB, as published. Nobody here has run it

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.