Analyzes staged Git changes to generate an intelligent conventional commit message with type, scope, body, and footers; presents for review and commits if approved.
From smart-commitnpx claudepluginhub rohitg00/awesome-claude-code-toolkit --plugin smart-commit/commitStages unstaged changes based on git status and diff analysis, then creates a commit with a generated message. Uses current branch and recent commit history for context.
/commitAnalyzes local git changes, stages files excluding secrets, drafts Conventional Commits message, confirms with user, and commits locally.
/commitCreates well-formatted git commits with conventional messages and emojis. Runs pre-commit checks (lint/format/build/docs), auto-stages files if needed, analyzes diffs, and suggests splitting multi-change commits unless --no-verify.
/commitCreates well-formatted git commits with conventional messages and emojis. Runs pre-commit checks (lint/format/build/docs), auto-stages files if needed, analyzes diffs, and suggests splitting multi-change commits unless --no-verify.
/commitAnalyzes current git diff, generates 3 conventional commit message options (concise, detailed, comprehensive), presents for user selection, and executes git commit.
/commitRuns git checks, lint/typecheck/tests, code review, then creates conventional commit message and commits staged changes. Supports --no-verify, --amend, --push flags.
Analyze all staged git changes and generate an intelligent conventional commit message.
Run git diff --cached --stat to identify all staged files and their change magnitudes.
Run git diff --cached to read the full diff of staged changes.
Determine the primary commit type based on the nature of changes:
feat - New functionality, new files introducing features, new endpoints or UI componentsfix - Bug corrections, error handling improvements, null checks, edge case fixesrefactor - Code restructuring without behavior change, renaming, extraction of functionsdocs - Documentation-only changes, comments, README updates, docstringstest - Adding or modifying tests, test fixtures, test utilitieschore - Build config, dependency updates, CI changes, tooling, linting rulesperf - Performance improvements, caching, query optimization, lazy loadingstyle - Formatting, whitespace, semicolons, code style (no logic change)ci - CI/CD pipeline changes, workflow files, deployment configsDerive the scope from the most affected directory or module:
auth, api, ui)core, app)Write the commit subject line (max 72 characters):
Determine if a body is needed (skip for obvious single-line changes):
Add footers when applicable:
BREAKING CHANGE: <description> if the change breaks existing APIs or behaviorCloses #<number> if the change resolves a tracked issueRefs: <context> for related PRs, issues, or discussionsPresent the commit message for review, then execute git commit with the approved message.
type(scope): concise imperative description
Optional body explaining the motivation and approach.
Optional footers.
feat and refactor, ask: does the user-visible behavior change?git log --oneline -10 first to match the repository's existing commit style