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

1. Determine scope from the primary directory or module affected (e.g., auth, api, cli, db)
2. Check for breaking changes: removed public APIs, changed function signatures, renamed exports, schema migrations
3. Check recent commit history with git log --oneline -10 to match the project's style conventions
4. Construct the commit message: type(scope): imperative description under 72 characters
5. Add a body with bullet points explaining the "why" behind the change if the diff is non-trivial
6. Append BREAKING CHANGE: footer if applicable

Output

Conventional commit message following this format:

type(scope): imperative description

- Explanation of what changed and why
- Impact on existing functionality

BREAKING CHANGE: description (if applicable)

Error Handling

git add .

/commit-smart
/gc

git add src/auth/login.js src/api/users.js

/gc

feat(auth): add OAuth2 Google login support

Implements Google OAuth2 authentication flow using Passport.js.
Users can now sign in with their Google account instead of
creating a new password.

Closes #123

yes

fix(api): correct typo in email normalization

Changed tolowerCase() to toLowerCase() to fix TypeError
when processing user emails.

feat(search): add global search functionality

Implements full-text search across products, users, and orders.
New SearchBar component provides real-time suggestions as user types.

Closes #45

refactor(auth)!: change login to use email instead of username

BREAKING CHANGE: login() now requires email parameter instead of username.
Clients must update their authentication calls:
- Before: login(username, password)
- After: login(email, password)