Agent skill · software engineering · jeremylongshore
generating-smart-commits
Execute use when generating conventional commit messages from staged
Why this skill is useful
Adds automation for generating conventional commit messages based on staged changes, which the AI wouldn't reliably generate on its own.
What it needs
Requires git installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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 8. Add a body with bullet points explaining the "why" behind the change if the diff is non-trivial 9. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/generating-smart-commits--a91ee8