generating-smart-commits

name	generating-smart-commits
description	Execute use when generating conventional commit messages from staged git changes. Trigger with phrases like "create commit message", "generate smart commit", "/commit-smart", or "/gc". Automatically analyzes changes to determine commit type (feat, fix, docs), identifies breaking changes, and formats according to conventional commit standards.
allowed-tools	Read, Write, Edit, Grep, Glob, Bash(git:*)
version	1.28.0
author	Jeremy Longshore <[e-mail]>
license	MIT
tags	["devops","git","smart-commits"]
compatibility	Designed for Claude Code, also compatible with Codex and OpenClaw

Generating Smart Commits

Current State

!git diff --cached --stat !git log --oneline -5 !git status --short

Overview

Analyze staged git changes and generate Conventional Commits messages with accurate type classification, scope detection, and breaking change identification. Supports feat, fix, docs, style, refactor, test, chore, perf, ci, and build types following the Conventional Commits 1.0.0 specification.

Prerequisites

• Git repository initialized in the working directory
• Changes staged via git add (at least one staged file)
• Git user name and email configured (git config user.name, git config user.email)
• Understanding of the project's commit message conventions (check recent history)

Instructions

1. Run git diff --cached --stat to get an overview of staged files and change volume
2. Run git diff --cached to examine the actual code changes in detail
3. Classify the commit type based on the nature of changes:
   • feat: new functionality visible to users
   • fix: bug correction
   • refactor: code restructuring without behavior change
   • docs: documentation only
   • test: adding or updating tests
   • chore: build process, dependencies, or tooling
   • perf: performance improvement
   • ci: CI/CD configuration changes
4. Determine scope from the primary directory or module affected (e.g., auth, api, cli, db)
5. Check for breaking changes: removed public APIs, changed function signatures, renamed exports, schema migrations
6. Check recent commit history with git log --oneline -10 to match the project's style conventions
7. Construct the commit message: type(scope): imperative description under 72 characters