Pre-commit Code Review Checklist for AI-Assisted Elixir/Phoenix Projects
Pre-commit checklist for AI-assisted Elixir projects: verify docs, check for hardcoded values and debug code, validate security (no secrets, parameterized queries), ensure tests pass, and follow existing patterns.
A checklist for reviewing code before committing in Elixir/Phoenix projects, particularly when using AI coding assistants: Documentation: - Deep dive on docs to ensure accuracy - AGENTS.md and similar project guides up to date - Check what patterns other modules in the project follow Code quality: - No hardcoded values that should be configuration - No debug code left in (IO.inspect, dbg, console.log) - Error handling is appropriate (not over-handling, not under-handling) - No unused imports, aliases, or variables Security: - No credentials, API keys, or secrets in code - Input validation at system boundaries - SQL injection prevention (parameterized queries) - No XSS vectors in templates Tests: - New functionality has tests - Existing tests still pass - Edge cases covered Architecture: - Changes follow existing patterns in the codebase - No unnecessary abstractions or premature generalization - Database migrations are reversible where possible