git-save

name	git-save
description	Stage and commit code changes with Conventional Commits format. Use when: code changes are complete and ready to commit, after review approval, user says 'save', 'commit', 'ship it'. Don't use when: tests are failing or work is still in progress.
trigger	commit, save, ship it, git save
disable-model-invocation	true
allowed-tools	Bash(git status *), Bash(git diff *), Bash(git log *), Bash(git add *), Bash(git commit *)

/git-save — Commit Workflow

1. git status — identify changed files
2. git diff — understand what changed
3. git log --oneline -5 — match existing commit style
4. Stage specific files by name (never git add -A)
5. Skip files that look sensitive (.env, credentials, keys)
6. Draft commit: type(scope): description

Commit Types

type	when
feat	new feature
fix	bug fix
refactor	restructure, no behavior change
docs	documentation only
test	tests added/updated
chore	build, deps, config

Rules

• NEVER commit if tests are failing
• NEVER commit .env or credential files
• NEVER auto-push (commit only, user pushes manually)
• Ask before committing if scope is unclear