Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From smart-commit
Analyzes staged Git changes to generate an intelligent conventional commit message with type, scope, body, and footers; presents for review and commits if approved.
npx claudepluginhub rohitg00/awesome-claude-code-toolkit --plugin smart-commitHow this command is triggered — by the user, by Claude, or both
Slash command
/smart-commit:commitThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /smart-commit:commit Analyze all staged git changes and generate an intelligent conventional commit message. ## Process 1. Run `git diff --cached --stat` to identify all staged files and their change magnitudes. 2. Run `git diff --cached` to read the full diff of staged changes. 3. Determine the primary commit type based on the nature of changes: - `feat` - New functionality, new files introducing features, new endpoints or UI components - `fix` - Bug corrections, error handling improvements, null checks, edge case fixes - `refactor` - Code restructuring without behavior chang...
/commitAnalyzes currently staged git changes via git diff --cached, determines type and scope, and generates a conventional commit message for approval.
/commit-smartAnalyzes staged Git changes to generate a conventional commit message (type(scope): description), confirms with user, and commits if approved.
/commitAnalyzes git diffs or staged changes to generate conventional commit messages explaining WHY changes were made. Auto-detects type/scope, supports staging, validation, and overrides.
/commit-msgDrafts a Conventional Commit message for staged git changes: analyzes diffs/status/log, classifies type (feat/fix/etc.) and scope, formats summary/body/footer, performs slop check, and writes to commit_msg.txt.
/commitCreates a conventional git commit by analyzing staged changes and auto-generating a message in 'type(scope): description' format. Optional scope or message hint.
Share bugs, ideas, or general feedback.
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