ask-commit-assistance

❌ NO `git add .` → stage specific files only ❌ NO auto-running `git commit` → provide command for user ❌ NO committing secrets/debug code without warning ✅ MUST scan for API keys, tokens, passwords before staging ✅ MUST use Conventional Commits format ✅ MUST offer detailed and short message options </critical_constraints> 1. **Identify new files**: `git status`, `git diff --cached --name-only --diff-filter=A` 2. **Review**: Check for bugs, refactoring opportunities 3. **Safety scan**: API keys, debug code (print/console.log/dd), TODO/FIXME 4. **Stage**: `git add ` for reviewed files only 5. **Draft message**: Conventional Commits format, two options 6. **Present command**: `git commit -m "..."` for user to run Check for: - Secrets: API keys, tokens, passwords - Debug: print(), console.log(), dd() - Markers: TODO, FIXME, HACK → Warn user before staging if found </safety_scan> Types: feat, fix, docs, style, refactor, test, chore Format: `type(scope): description`

Option 1 (detailed): subject + body explaining why/what
Option 2 (short): just subject line
</commit_format>

```bash git status git diff --cached --name-only --diff-filter=A git ls-files --others --exclude-standard git add git commit -m "feat(scope): description" ```