skills.rest
channingwalton
channingwaltonCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

Commit Helper

Generate conventional commit messages from staged git diffs.

3|1|Updated Jun 23, 2024
Search Tags:#automation#git#commit#diff#conventional-commits#staged-changes#commit-messages
One-click install
npx skills add https://github.com/channingwalton/dotfiles --skill commit-helper-channingwalton
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Commit Helper
Source: https://github.com/channingwalton/dotfiles/tree/main/.claude/skills/commit-helper
Command: npx skills add https://github.com/channingwalton/dotfiles --skill commit-helper-channingwalton

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you generate clear conventional commit messages from your git diffs, saving time when composing or reviewing commits and enforcing consistent messaging across your project.

Core Features & Use Cases

  • Automated message generation: Analyze staged changes and diff context to produce concise, conventional commit messages.
  • Commit once or iterate: Use with or without creating the commit; you can preview messages or commit immediately.
  • Conventional types: Follow the standard types (feat, fix, refactor, test, docs, chore) to keep history readable and scannable.

Quick Start

Generate a conventional commit message for the current staged changes.

Frequently Asked Questions about Commit Helper

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

FAQPage Schema
How do I generate conventional commit messages from git diffs?▼

Conventional commit messages are generated by analyzing your staged changes and producing a commit message that follows the standard format: a type (feat, fix, refactor, test, docs, chore), a short imperative summary under 50 characters, and optional body/footer. This Skill automates that analysis and formatting from your git diff.

What are conventional commits and why should I use them?▼

Conventional commits enforce a structured format for commit messages—type, scope, and description—that makes git history readable, scannable, and machine-parseable. They enable automated changelog generation, semantic versioning, and consistent communication across teams.

Can I preview a commit message before applying it?▼

Yes. This Skill generates conventional commit messages from staged changes and lets you review the output before deciding whether to create the commit or iterate on the message.

How do I use this Skill after writing tests or refactoring code?▼

Stage your changes with `git add`, then use this Skill to analyze the diff and generate a conventional commit message that matches the type of work (feat, test, refactor, etc.) you've completed.

Does this Skill work with any git workflow?▼

Yes. This Skill works with any git workflow—feature branches, trunk-based development, or pull requests—by analyzing staged changes in your current repository and generating compliant commit messages.

What happens if my staged changes span multiple types of work?▼

Conventional commits work best with atomic, single-purpose commits. If your staged changes mix different types (feat and fix), consider staging them separately so each commit has a clear, accurate type and message.

Related Skills

Explore More Software Engineering Skills→
AKMofficialAKMofficial
1

commit

Generate a conventional commit message from git diff --cached output.

Community
Intermediate
FradSerFradSer
577

commit-and-push

Creates atomic commits with the specified on-disk format and pushes to origin using git push -u <branch>.

Community
Basic
jovermierjovermier
1

git-workflow

Automate Git commits, branches, and pull requests with Conventional Commits.

Community
Basic
vulikjulikvulikjulik

aif-commit

Generate conventional commit messages from staged git changes.

Community
Intermediate