skills.rest
ultraviollettnympho
ultraviollettnymphoCOMMUNITY
Explore all skills by this author →
GitHub

git-commit

Generate conventional commit messages by analyzing staged git diffs and staging files.

1|1|Updated Jan 29, 2026
Search Tags:#git#diff analysis#version control#commit#conventional commits#staging#commit message
One-click install
npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill git-commit-ultraviollettnympho
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/ultraviollettnympho/transit-ticket/tree/main/.github/skills/git-commit
Command: npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill git-commit-ultraviollettnympho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, meaningful git commit messages is tedious and often inconsistent across a team. This Skill analyzes your actual code changes and produces standardized Conventional Commits messages with the correct type, scope, and description. ## Core Features & Use Cases - Diff-Based Message Generation: Inspects staged or working-tree diffs to auto-detect the commit type (feat, fix, docs, refactor, etc.) and scope. - Intelligent Staging: Groups and stages files logically before committing, while warning against committing secrets like .env files or credentials. - Breaking Change Support: Formats breaking changes with the ! marker or BREAKING CHANGE footer per the Conventional Commits spec. - Use Case: After finishing a bug fix across three files, ask the AI to commit your changes and it stages the files, determines the type is fix, and creates a properly formatted commit like fix(auth): correct token expiration check. ## Quick Start Ask the AI 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 follows the format type[scope]: description, using types like feat, fix, docs, or refactor. This Skill analyzes your git diff to pick the right type and scope, then writes the description in present tense under 72 characters.

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

The Skill runs git diff --staged or git diff to inspect your actual changes, infers the change type and affected module, and executes git commit with a formatted message. You can override the type, scope, or description interactively.

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

Add an exclamation mark after the type or scope, like feat!: remove deprecated endpoint, or include a BREAKING CHANGE footer in the commit body explaining what behavior changed.

Can it prevent committing secrets or sensitive files?▼

Yes, the workflow explicitly warns against committing secrets such as .env files, credentials.json, or private keys during the staging step. It also prohibits destructive git operations like force pushes to main or skipping hooks without explicit request.

What happens if a git hook fails during commit?▼

If a commit fails due to hooks, the guidance is to fix the underlying issue and create a new commit rather than amending or bypassing the hook with --no-verify. This keeps history clean and respects project checks.

Related Skills

Explore More Software Engineering Skills→
codeaholicguycodeaholicguy
1.6k

dev-commit

Creates verified conventional git commits containing only intended changes.

Community
Intermediate
sumrae412sumrae412
2

shipping-workflow

Automate conventional commits, pull requests, and 10-step code review before merging.

Community
Advanced
MeshJSMeshJS
2

code-review

Analyze uncommitted diffs for security and quality issues.

Official
Intermediate
theslashdojotheslashdojo

git-rebase

Replay commits onto a new base with interactive rebase and autosquash.

Official
Intermediate