smart-commit

Generate Conventional Commits messages with rationale from staged diffs.

13|3|Updated Mar 27, 2026

Search Tags:#git #commit #diff #semantic #conventional-commits #body #why

Ready to run

npx skills add https://github.com/heaptracetechnology/heaptrace-skills --skill smart-commit-heaptracetechnology

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: smart-commit
Source: https://github.com/heaptracetechnology/heaptrace-skills/tree/main/smart-commit
Command: npx skills add https://github.com/heaptracetechnology/heaptrace-skills --skill smart-commit-heaptracetechnology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of meaningful commit messages that explain why changes were made, not just what changed, improving git history readability.

Core Features & Use Cases

Generates subject lines that follow conventional commits and include scope
Produces a detailed body explaining the rationale and potential side effects
Helps maintain clean, navigable git history across large codebases

Quick Start

Stage your changes and run the smart-commit skill to generate a semantic commit message.

Frequently Asked Questions about smart-commit

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

FAQPage Schema

How do I generate conventional commit messages that explain why changes were made?▼

To generate conventional commit messages that explain why changes were made, run the smart-commit skill against your staged diffs or working directory changes. It automatically produces semantic commit messages with a clear rationale in the body.

What is the best way to automate writing semantic git commit bodies for monorepos?▼

The best way to automate semantic git commit bodies for monorepos is to apply the smart-commit skill across your working directory changes. It handles multiple files in monorepos and generates detailed commit bodies explaining the rationale.

Can I include scope and capture breaking changes in conventional commits automatically?▼

Yes, you can include scope and capture breaking changes in conventional commits automatically. The smart-commit skill ensures messages follow Conventional Commits standards, supporting optional scopes and flagging breaking changes in the output.

How do I create a git commit message from a staged diff without writing it manually?▼

To create a git commit message from a staged diff without writing it manually, stage your changes and run the smart-commit skill. It analyzes the diff to generate a WHY-focused commit message automatically.

Does the smart-commit skill work with unstaged working directory changes across multiple files?▼

Yes, the smart-commit skill works with unstaged working directory changes across multiple files. It can apply to both staged diffs and working directory changes in any project, generating semantic commit messages accordingly.

What are the limitations of using automated tools for conventional commit generation?▼

A limitation of automated conventional commit generation is that while the skill produces structured messages with rationale, developers must still review the output to ensure the generated rationale accurately reflects complex, project-specific side effects.