human-commit

Generate human-like Git commit messages from analyzed code changes.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/b4r7x/agent-skills --skill human-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: human-commit
Source: https://github.com/b4r7x/agent-skills/tree/main/human-commit
Command: npx skills add https://github.com/b4r7x/agent-skills --skill human-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill generates commit messages that sound like a human developer wrote them, avoiding generic or AI-like phrasing.

Core Features & Use Cases

  • Natural Language Commit Messages: Creates 3 distinct commit message options.
  • Context-Aware: Analyzes git diff to understand changes.
  • Style Matching: Adapts to Conventional Commits or plain lowercase styles based on repository history.
  • Use Case: After making several code changes, you need to commit them but are unsure how to phrase the message. This skill provides natural, descriptive options.

Quick Start

Generate three human-like commit message options for my current git changes.

Frequently Asked Questions about human-commit

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

FAQPage Schema
How do I generate human-like git commit messages automatically?

To generate human-like git commit messages, this Skill analyzes your staged or unstaged code changes and provides three natural-sounding options. It avoids generic phrasing by detecting your repository's commit style and matching it.

Can I generate conventional commits from my git diff?

Yes, you can generate conventional commits from your git diff. The Skill detects whether your repository uses Conventional Commits or plain lowercase styles based on history, then formats the generated options accordingly.

Does this tool provide multiple commit message options to choose from?

Yes, this tool provides multiple commit message options, generating three distinct choices for each set of changes. This allows you to select the most accurate description rather than being locked into a single automated message.

How do I include breaking change footers in automated commit messages?

To include breaking change footers in automated commit messages, the Skill detects when appropriate based on your code changes. It automatically adds optional bodies or breaking change footers to the generated messages when significant modifications are identified.

What's the best way to write descriptive commit messages after making several code changes?

The best way to write descriptive commit messages after several code changes is to analyze the git diff for context. This Skill parses your modifications and provides three natural, descriptive options tailored to your repository's style.

Will the generated commit messages sound like a real developer wrote them?

Yes, the generated commit messages will sound like a real developer wrote them. The Skill specifically avoids generic or AI-like phrasing by analyzing your actual code changes and producing natural, context-aware descriptions.