skills.rest
eklyukin
eklyukinCOMMUNITY
Explore all skills by this author →
GitHub

Git Commit Helper

Generates conventional commit messages by analyzing staged git diffs.

Updated Jul 24, 2026
Search Tags:#git#code review#version control#developer workflow#conventional commits#commit message#git diff
One-click install
npx skills add https://github.com/eklyukin/my-ai-config --skill git-commit-helper-eklyukin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Git Commit Helper
Source: https://github.com/eklyukin/my-ai-config/tree/main/skills/git-commit-helper
Command: npx skills add https://github.com/eklyukin/my-ai-config --skill git-commit-helper-eklyukin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, well-formatted commit messages is repetitive and often inconsistent across a team. This Skill analyzes your staged changes and drafts a conventional commit title that follows the repository's commit rules, removing guesswork and enforcing a uniform style. ## Core Features & Use Cases - Diff-Based Analysis: Inspects git status and git diff --staged to understand the actual change before drafting a message. - Conventional Format Enforcement: Produces title-only messages in the <type>[optional scope]: <description> format using types like feat, fix, refactor, docs, test, and chore. - Safe Commit Workflow: Shows the proposed title and file list, waits for explicit confirmation, and stages only files touched in the current session. - Use Case: After staging changes to an authentication module, ask for a commit message and receive a proposal like feat(auth): add JWT token validation for review before committing. ## Quick Start Ask the assistant to review my staged changes and write a commit message for them.

Frequently Asked Questions about Git Commit Helper

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

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

Stage your changes, then let the Skill run git status and git diff --staged to understand the modification. It drafts a title in the format type(optional scope): description, shows it with the file list, and commits only after your confirmation.

What commit types does the conventional commit format support?▼

The supported types are feat, fix, refactor, docs, test, and chore, with definitions maintained in rules/commit.md. An optional scope in parentheses can narrow the change to a module like auth or api.

Can I include a commit body or trailers like Co-Authored-By?▼

No. This workflow enforces title-only commits with no body, no footers, and no trailers such as BREAKING CHANGE or Co-Authored-By. The convention keeps history compact and scannable.

Does the Skill commit automatically without my approval?▼

No. It always shows the proposed commit title and the list of files to be added first, then waits for explicit confirmation before running git commit. It also avoids blanket git add -A without reviewing git status.

When should I omit the scope in a commit message?▼

Omit the scope when the change touches the whole repository rather than a single module. Inventing a scope for broad changes is discouraged; a plain type prefix like chore or refactor is preferred.

Related Skills

Explore More Software Engineering Skills→
OpenAuthorityOpenAuthority
8

git_status

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

Official
Intermediate
ryan-mahoneyryan-mahoney

pr

Open a GitHub pull request linked to an issue from a branch name.

Community
Intermediate
owenlamontowenlamont
1

python-lint-format

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

Community
Advanced
nmdranmdra
26

git-commiter

Generate Conventional Commits messages from git diff analysis.

Community
Advanced