skills.rest
malston
malstonCOMMUNITY
Explore all skills by this author →
𝕏@marsguitarsGitHub

generating-commit-messages

Convert staged diffs into structured commit messages with summaries and affected components.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/malston/claude-config --skill generating-commit-messages-malston
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: generating-commit-messages
Source: https://github.com/malston/claude-config/tree/main/skills/commit-helper
Command: npx skills add https://github.com/malston/claude-config --skill generating-commit-messages-malston

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers automatically craft clear and consistent commit messages from their staged changes, saving time during code reviews and push workflows.

Core Features & Use Cases

  • Automated Summary: Generate a concise 50-character summary of the diffs in present tense.
  • Detailed Description: Provide a descriptive paragraph explaining what changed and why.
  • Affected Components: Identify potentially impacted modules or files for quick review.
  • Use Case: After staging multiple files, generate a compliant commit message ready for commit.

Quick Start

  • View the current changes with git diff --staged, then ask me to generate a commit message for these changes.

Frequently Asked Questions about generating-commit-messages

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

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

Generate a commit message by viewing your staged diffs with git diff --staged, then request a message. The Skill converts those diffs into a structured commit with a 50-character summary, detailed description, and affected components in present tense.

What format does the commit message follow?▼

Commit messages follow a three-part structure: a concise summary under 50 characters, a detailed description explaining what changed and why, and a list of affected components. All text uses present tense and focuses on what and why rather than how.

Can I use this for bug fixes and feature updates?▼

Yes. The Skill handles multiple commit types including bug fixes, feature updates, refactors, and documentation changes. It adapts the structured format to each change type while maintaining consistency across your commits.

When should I generate commit messages this way?▼

Generate commit messages after staging multiple files but before committing. This ensures your message is complete, compliant with the structured format, and ready for code reviews and push workflows.

Does this work with different project types?▼

Yes. The Skill applies across software projects regardless of language or framework. It converts staged diffs into readable messages applicable to any codebase that uses git for version control.

Related Skills

AKMofficialAKMofficial
1

commit

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

Community
Intermediate
consultantvisionconsultantvision

git-sync

Automate Git commits and push local changes to GitHub.

Community
Intermediate
zerwizzerwiz

requesting-code-review

Verify staged git changes for security issues and regressions before commit.

Community
Advanced
ss49919201ss49919201

git-add-commit

Stage git changes and generate commit messages from diffs.

Community
Basic