skills.rest
brillianodhiya
brillianodhiyaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

commit-helper

Generate conventional commit messages from staged git diffs.

Updated Jun 11, 2026
Search Tags:#git#code review#version control#conventional commits#commit message#git diff
One-click install
npx skills add https://github.com/brillianodhiya/VisionScript --skill commit-helper-brillianodhiya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-helper
Source: https://github.com/brillianodhiya/VisionScript/tree/main/.agents/skills/commit-helper
Command: npx skills add https://github.com/brillianodhiya/VisionScript --skill commit-helper-brillianodhiya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing clear, consistent commit messages is a common friction point for developers, often resulting in vague or inconsistent history that is hard to review and maintain. ## Core Features & Use Cases - Diff Analysis: Inspects staged changes via git diff --staged to identify modified files, change type, and affected scope. - Conventional Commit Formatting: Produces messages with type prefixes (feat, fix, docs, refactor, test, chore), optional scopes, and concise summary lines under 50 characters. - Use Case: After staging changes to an authentication module, ask for a commit message and receive a structured output like feat(auth): add OAuth2 support for GitHub login with a detailed body and issue reference. ## Quick Start Analyze my staged git changes and write a conventional commit message for them.

Frequently Asked Questions about 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 git changes?▼

Run git diff --staged to review staged changes, identify the change type and scope, then write a summary under 50 characters with a type prefix like feat or fix. Add a body explaining what changed and why.

What commit types are used in conventional commits?▼

Common types include feat for new features, fix for bug fixes, docs for documentation, refactor for code restructuring, test for test changes, and chore for maintenance tasks. Each type signals the nature of the change.

How long should a commit message summary be?▼

The summary line should stay under 50 characters and use present tense, such as "Add feature" rather than "Added feature". Keep it concise but descriptive enough to understand the change at a glance.

When should I include a scope in a commit message?▼

Include a scope in parentheses after the type when changes affect a specific component or module, like feat(auth) or fix(api). Scopes help teams quickly identify which part of the codebase changed.

Should commit messages reference issue numbers?▼

Yes, reference issue numbers when applicable using footers like "Closes #123" in the commit body. This links the commit to tracked work and helps automate issue closure in platforms like GitHub.

Related Skills

Explore More Software Engineering Skills→
gajjalaashok75-UIgajjalaashok75-UI
2

git-pushing

Stages modified files, commits conventionally, and pushes to remote tracking repository.

Community
Basic
VYRE-StudiosVYRE-Studios

commit-push-pr

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

Official
Intermediate
tgmarinhotgmarinho

setup-pre-commit

Automate pre-commit hook setup with Husky and lint-staged.

Community
Intermediate
jaeyeonlingjaeyeonling

git-workflow

Standardize Git workflows with conventional commits and branching strategies.

Community
Intermediate