commit

Generate a conventional commit message from the current working tree diff.

1|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/huangeddie/dotfiles --skill commit-huangeddie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/huangeddie/dotfiles/tree/main/dot_agents/exact_packages/coding/exact_skills/commit
Command: npx skills add https://github.com/huangeddie/dotfiles --skill commit-huangeddie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you avoid vague, manual commit messages by turning your current changes into a clear conventional commit that reflects the work done.

Core Features & Use Cases

  • Conventional commit creation: Produces a commit message aligned with conventional commit style based on the current diff.
  • Small-issue cleanup: Optionally resolves minor issues “along the way” before writing the final commit description.
  • Workflow fit: Useful when you want consistent commit history during everyday development and quick iteration.

Quick Start

Use the commit skill to create a new conventional commit for your current uncommitted changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate a conventional commit message from a git diff?

To generate a conventional commit message from a git diff, the skill analyzes your current working tree changes and outputs a ready-to-use commit summary. It deterministically resolves the change summary to ensure consistent, high-signal commit history.

What is the best way to automate conventional commit creation for incremental changes?

Automating conventional commit creation involves parsing the working tree diff to produce aligned commit messages. This skill fits development workflows needing consistent commit history during everyday development and quick iteration by turning current changes into clear conventional commits.

Can I fix minor code issues before writing a git commit message?

Yes, you can fix minor code issues before writing a git commit message using the small-issue cleanup feature. The skill optionally resolves minor issues along the way before finalizing and outputting the final commit description.

How do I avoid vague manual commit messages in version control?

To avoid vague manual commit messages in version control, you can analyze your current uncommitted changes to automatically generate a clear conventional commit. This ensures the commit message accurately reflects the work done based on the actual diff.

Does generating conventional commits require analyzing the entire repository history?

Generating conventional commits does not require analyzing the entire repository history. The skill focuses on analyzing the current working tree diff and any applicable small issues to produce a deterministic, ready-to-use commit message for incremental changes.