Automatic commit with change analysis
Automatically analyze all changes, detect commit type, and generate conventional commit message with proper formatting and context
automatic-commit-with-change-analysis.txt
plaintext
/git-smart-commitLoading...
Intelligently analyzes changes and creates well-formatted git commits with conventional commit messages
<type>(<scope>): <subject>
<body>
<footer>Automatically analyze all changes, detect commit type, and generate conventional commit message with proper formatting and context
/git-smart-commitCreate commit with specified type (feat) and custom message, following conventional commit format with automatic body generation
/git-smart-commit feat "Add user authentication"Generate fix commit with scope detection and detailed message explaining the bug fix and resolution
/git-smart-commit fix "Resolve login redirect issue"Detect breaking changes and automatically format commit with BREAKING CHANGE footer or exclamation mark notation
/git-smart-commit feat "Remove legacy API endpoint"Create documentation commit with proper type and message for documentation-only changes
/git-smart-commit docs "Update API documentation"Generate refactor commit with scope detection and explanation of code improvements without functional changes
/git-smart-commit refactor "Simplify authentication logic"Group related changes (components, API routes, tests) into single logical commit with comprehensive message
/git-smart-commit feat "Implement user profile feature"Command stages unwanted files like .env or credentials.json
Add sensitive files to .gitignore immediately: echo '.env' >> .gitignore. Use git reset HEAD <file> to unstage. Configure global ignore: git config --global core.excludesfile ~/.gitignore_global
Conventional commit message exceeds 50 character limit
Use scope to shorten subject: feat(auth): add OAuth instead of feat: add OAuth authentication system. Put details in body. Run: git commit --amend to rewrite if already committed.
Command fails with 'nothing to commit, working tree clean'
Verify changes exist: git status. Check if files are tracked: git ls-files. Stage new files: git add <file>. For ignored files: git add -f <file> or update .gitignore.
Breaking change not properly indicated in commit message
Add BREAKING CHANGE: footer or ! after type: feat(api)!: remove legacy endpoint. Use git commit --amend to fix recent commit. Format: type(scope)!: subject\n\nBREAKING CHANGE: description
Multiple unrelated changes need separate commits
Stage files selectively: git add src/auth.ts && git commit -m 'feat: add auth'. Then: git add src/logging.ts && git commit -m 'feat: add logging'. Use git add -p for partial staging.
Smart commit generates incorrect or vague commit messages
Review staged changes with git diff before committing. Use --verbose flag to see analysis process. Manually edit commit message if auto-generated is inaccurate. Check if changes are too complex for automatic analysis.
Commit message format doesn't match team conventions
Configure commit message template with --template flag. Use --conventional flag for conventional commits format. Set up .gitmessage template file for consistent formatting. Review team commit message guidelines.
Smart commit fails to detect changes or shows no staged files
Verify files are staged with git add. Check git status to confirm staged changes. Ensure working directory is a git repository. Use --force flag if detection is incorrect.
Loading reviews...
Manage Claude Code checkpoints to safely rewind code changes, restore conversation states, and explore alternatives without fear using ESC+ESC or /rewind commands
Intelligent documentation generator with API specs, code examples, tutorials, and interactive guides
Advanced debugging assistant with root cause analysis, step-by-step troubleshooting, and automated fix suggestions
Growing community of AI engineers actively building with Claude
Live in 5 minutes • Growing community