commit-checklistlisted

# Commit Checklist ## Purpose Validate staged changes against best practices before committing. Catch common issues (secrets, debug code, missing tests), generate well-structured commit messages following conventional commit format, and enforce scope discipline. Works with any git-based project. ## When to Use - **Pre-commit validation:** "Check if my changes are ready to commit" - **Commit message:** "Write a commit message for these changes" - **Review staged changes:** "Review what I'm about to commit" - **Before pushing:** "Validate before I push" ## Pre-Commit Validation ### The Checklist Run through these checks on staged changes (`git diff --cached`): #### Security - [ ] **No secrets:** No API keys, tokens, passwords, or connection strings - [ ] **No .env files:** `.env`, `.env.local`, credentials files not staged - [ ] **No private keys:** No `.pem`, `.key`, `.p12` files - [ ] **No hardcoded URLs:** No internal/staging URLs that shouldn't be public #### Code Quality - [ ] **No debug code:** No `console.log`, `print()`, `debugger`, `binding.pry`, `TODO` left in - [ ] **No commented-out code:** Remove dead code, don't comment it out - [ ] **No merge conflict markers:** No `<<<<<<<`, `=======`, `>>>>>>>` markers - [ ] **No large files:** No binaries, datasets, or files >1MB that belong in LFS or `.gitignore` #### Completeness - [ ] **Tests included:** New features have corresponding tests - [ ] **Tests pass:** All existing tests still pass - [ ] **Linter clean: