dev-workflowlisted

# Development Workflow Patterns ## Quick Reference | Task | Command | What It Does | |------|---------|-------------| | Commit | `/commit` | Stage changes, write conventional commit message | | Review | `/review` | Analyze branch changes for bugs, security, quality | | Test | `/test` | Detect test framework, run tests, diagnose failures | | Fix | `/fix` | Trace root cause, implement minimal fix, verify | | PR | `/pr` | Create pull request with summary and test plan | | Status | `/status` | Full repo overview: branches, PRs, CI, sync state | | Check PR | `/check-pr` | CI status, reviews, comments, merge readiness | ## Commit Workflow 1. Run `git status` and `git diff` to understand changes 2. Run `git log --oneline -5` to match the repo's commit style 3. Stage only relevant files (never stage .env, credentials, binaries) 4. Write a conventional commit message: - Format: `type: short description` - Types: `feat`, `fix`, `refactor`, `docs`, `test`, `chore`, `style`, `perf` - Focus on WHY, not WHAT - Keep first line under 72 chars 5. Never push unless explicitly asked ## Code Review Checklist When reviewing branch changes (`git diff main...HEAD`): | Category | Check For | |----------|----------| | Logic | Bugs, off-by-one errors, null handling | | Security | Injection, XSS, secrets exposure, CORS | | Performance | N+1 queries, unnecessary loops, missing indexes | | Error handling | Unhandled exceptions, missing edge cases | | Style | Consistency with surroundin