git-smart-commit

Generate conventional commit messages from staged Git changes.

1|Updated Dec 22, 2025

Search Tags:#git #commit #conventional-commits

Ready to run

npx skills add https://github.com/abdullah1854/ClaudeSuperSkills --skill git-smart-commit

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Generates conventional commit messages from staged changes, with optional scope and breaking-change support.

Core Features & Use Cases

Commit Message Engine: Suggests type, scope, and description.
Documentation: Shows conventional types for reference.

Quick Start

Generate a commit message for a staged change describing a new feature.

Frequently Asked Questions about git-smart-commit

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

FAQPage Schema

How do I generate conventional commit messages from staged changes?▼

Conventional commits are a standardized format for commit messages that specify type (feat, fix, refactor, docs, test, chore, style, perf, ci, build), optional scope, and description. This Skill reads your staged diff and generates the full commit message automatically, inferring the type and structure based on what changed.

What are conventional commits and why should I use them?▼

Conventional commits follow a structured format that makes commit history readable and enables automated changelog generation and versioning. They standardize how teams document changes—whether a commit introduces a feature, fixes a bug, or updates documentation—making history easier to parse and CI pipelines easier to automate.

Can I use conventional commits in my Git workflow for pre-commit automation?▼

Yes. This Skill generates conventional commit messages that work in local development, pre-commit hooks, and CI pipelines. You stage your changes, and the Skill produces a formatted commit message with type, scope, description, and optional breaking-change markers, fitting directly into automated Git workflows.

Do I need to manually specify the commit type and scope?▼

The Skill accepts optional inputs for type, scope, description, and breaking-change status, and also infers them from your staged diff. You can provide these parameters explicitly or let the Skill suggest them based on what files and code changed.

What commit types does this Skill support?▼

The Skill supports all standard conventional commit types: feat (new feature), fix (bug fix), refactor (code restructuring), docs (documentation), test (test changes), chore (maintenance), style (formatting), perf (performance), ci (CI configuration), and build (build system changes).

How do I document breaking changes in my commits?▼

The Skill generates conventional commit messages with optional breaking-change markers and footers. You can flag a commit as breaking by passing the breaking parameter, and it will include the appropriate footer in the formatted message.