git-commit-review

What I do

1. Check for sensitive files: Warn about .env, credentials.json, or other secrets before staging
2. Review changes: Run git status and git diff to review all unstaged changes
3. Stage changes: Execute git add -A to stage all changes (or offer git add -p for partial)
4. Review staged changes: Run git diff --cached to review what will be committed
5. Run pre-commit checks: Run lint/typecheck if available in package.json
6. Generate commit message: Create a clear, conventional commit message following standard conventions
7. Show preview & confirm: Display the full commit and ask user to confirm/edit
8. Commit changes: Execute git commit with the generated message
9. Check remote status: Verify branch is up-to-date before pushing
10. Push to remote: Push the commit to the current branch (warn on main/master)

When to use me

Use this when you want to:

• Commit all staged changes with a well-crafted commit message
• Ensure changes are properly reviewed before committing
• Quickly push commits to the remote repository