skills.rest
jmrplens
jmrplensCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-commit

Generates conventional commit messages by analyzing git diffs and staging changes.

37|4|Updated Apr 11, 2026
Search Tags:#git#diff analysis#version control#commit#conventional commits#staging#commit message
One-click install
npx skills add https://github.com/jmrplens/gitlab-mcp-server --skill git-commit-jmrplens
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/jmrplens/gitlab-mcp-server/tree/main/.github/skills/git-commit
Command: npx skills add https://github.com/jmrplens/gitlab-mcp-server --skill git-commit-jmrplens

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, meaningful commit messages is tedious and often skipped, leading to messy git histories that are hard to review, search, and automate against. ## Core Features & Use Cases - Diff-Based Message Generation: Analyzes staged or working-tree diffs to infer the correct conventional commit type, scope, and description. - Intelligent Staging: Groups and stages files logically before committing, while blocking secrets like .env files and credentials. - Conventional Commits Compliance: Enforces the Conventional Commits specification including breaking-change markers, footers, and issue references. - Use Case: After finishing a bug fix across several files, ask the assistant to commit your changes and receive a properly formatted message like "fix(auth): handle expired token refresh" with one logical commit per change. ## Quick Start Ask the assistant to commit my current changes with a conventional commit message based on the diff.

Frequently Asked Questions about git-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a conventional commit message?▼

A conventional commit message follows the format "type[optional scope]: description", using types like feat, fix, docs, refactor, or chore. The description should be present tense, imperative mood, and under 72 characters.

How to generate a commit message from a git diff automatically?▼

Analyze the staged diff with git diff --staged to identify what changed, then map the change to a conventional commit type and scope. This skill automates that analysis and produces the formatted message before running git commit.

How do I mark a breaking change in conventional commits?▼

Add an exclamation mark after the type or scope, such as "feat!: remove deprecated endpoint", or include a "BREAKING CHANGE:" footer in the commit body describing what changed.

Can I commit only some of my changed files?▼

Yes, stage specific files with git add followed by paths or patterns, then commit only the staged changes. This supports grouping related edits into one logical commit per change.

What should I do when a git commit fails due to hooks?▼

Fix the issue reported by the hook and create a new commit rather than amending or bypassing with --no-verify. Skipping hooks should only happen when the user explicitly requests it.

Related Skills

Explore More Software Engineering Skills→
OpenAuthorityOpenAuthority
8

git_status

Report staged, unstaged, and untracked files from git status --porcelain.

Official
Intermediate
VYRE-StudiosVYRE-Studios

commit-push-pr

Commit staged changes, push the branch, and open a pull request via GitHub CLI.

Official
Intermediate
owenlamontowenlamont
1

python-lint-format

Automate Python code linting and formatting with pre-commit hooks.

Community
Advanced
paywherebpaywhereb

squash

Squash all branch commits into one via interactive git rebase.

Official
Intermediate