git-commit

Standardized git commits using Conventional Commits specification with intelligent diff analysis and message generation. Create standardized, semantic git commits using the Conventional Commits specification. Analyze the actual diff to determine appropriate type, scope, and message. If nothing is staged or you want to group changes differently: Never commit secrets (.env, credentials.json, private keys). Analyze the diff to determine: - Auto-detects commit type (feat, fix, docs, refactor, perf, test, build, ci, chore, revert) and scope from actual code changes - Generates semantic commit messages following conventional format with optional body and footer sections - Intelligently stages files for logical grouping when needed, with support for pattern-based and interactive staging - Detects breaking changes and formats them with exclamation mark or BREAKING CHANGE footer - Enforces git safety protocols: prevents destructive operations, config changes, and secret commits without explicit user request - Type : What kind of change is this? - Scope : What area/module is affected? - Description : One-line summary of what changed (present tense, imperative mood, <72 chars) - One logical change per commit - Present tense: "add" not "added" - Imperative mood: "fix bug" not "fixes bug" - Reference issues: Closes #123 , Refs #456 - Keep description under 72 characters - NEVER update git...