git-commit-review

Skip push: Tell me &quot;don&#x27;t push&quot; to skip the push step
Amend: Tell me &quot;amend&quot; to amend the last commit
Dry run: Tell me &quot;preview&quot; to see what would happen without committing
Partial staging: Tell me &quot;partial&quot; to interactively stage hunks

What I do

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

Use this when you want to:

I'll generate commit messages following conventional commits:

For multiple changes, I'll create a summary line and bullet points for details.

If the branch name contains an issue/ticket reference (e.g.,

feature/ABC-123

), I'll include it in the commit message.

Sensitive file warnings: Alert if
```
.env
```
,
```
credentials.json
```
,
```
*.key
```
, etc. are being staged
Hook verification: Never skip pre-commit hooks (
```
--no-verify
```
is prohibited)
Branch protection: Warn when pushing directly to
```
main
```
or
```
master
```
Force push protection: Use
```
--force-with-lease
```
instead of
```
--force
```
if force push is needed
Up-to-date check: Warn if branch is behind remote before pushing