suggest-commit

Generate a git commit message from the current diff.

1|Updated Mar 16, 2026

Search Tags:#git #commit #diff #draft #version-control #message

Ready to run

npx skills add https://github.com/andeart/dotfiles --skill suggest-commit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: suggest-commit
Source: https://github.com/andeart/dotfiles/tree/main/agents/skills/suggest-commit
Command: npx skills add https://github.com/andeart/dotfiles --skill suggest-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers draft precise commit messages that reflect the changes in the diff, improving clarity and traceability in version history.

Core Features & Use Cases

Generate a concise, conventional commit message from the current diff (staged or unstaged)
Enforce imperative present tense and default to a single-line subject, with an optional body for multiple concerns
Apply in workflows where you need a readable summary of changes before committing

Quick Start

Suggest a commit message for the current diff.

Frequently Asked Questions about suggest-commit

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

FAQPage Schema

How do I generate a git commit message from a diff?▼

To generate a git commit message from a diff, you can use a tool that reads staged or unstaged changes and drafts a concise summary reflecting those modifications. It automatically creates a readable message based on the detected code updates.

What is the best way to write conventional commit messages for bug fixes and features?▼

The best way to write conventional commit messages for bug fixes and features is to enforce imperative present tense and keep the subject under 100 characters. This ensures clarity and traceability in version history while summarizing the changes.

Does the commit message generator work with unstaged changes?▼

Yes, the commit message generator works with unstaged changes by accessing them via the git diff command. It can also process staged changes using git diff --staged to help you draft a message before committing.

How do I summarize multiple code changes in a single git commit message?▼

To summarize multiple code changes in a single git commit message, you draft a single-line subject under 100 characters and include an optional body. This separates the brief overview from the detailed concerns of the refactor or feature.

Do I need to stage files before drafting a commit message?▼

You do not need to stage files before drafting a commit message, as the tool processes both staged and unstaged diffs. You can generate a summary from your current working directory changes at any point in your workflow.