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)

How to use

Invoke me directly with /commit :

• /commit

• review, stage, commit and push all changes

• /commit don't push

• commit without pushing

• /commit amend

• amend the last commit

• /commit partial

• interactively stage hunks

Commit message format

I'll generate commit messages following conventional commits:

• feat: add new feature X

• fix: resolve issue with Y

• refactor: simplify logic in Z

• docs: update documentation

• chore: update dependencies

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.

Safety features

• 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