code-review

Django code review for multi-file changes analyzes correctness, completeness, and sprint goal alignment. It evaluates lint/type-check results, performance, code smells, typing, documentation quality, test coverage, and security, producing a structured report with concrete evidence per criterion and a file-by-file status list.

Yes, code review evaluates Django patterns including Fat Model, FBV, PRG, and soft delete. The deep per-file review phase verifies correctness and completeness while specifically assessing performance considerations, typing, and adherence to established Django architectural patterns.

Code review verifies planning adherence by evaluating delivered work line by line against the sprint plan. It ensures completeness and alignment with sprint goals, generating a per-file status list that documents whether the implementation satisfies the planned requirements.

The best way to review security and test coverage is through a structured code review that assesses both dimensions alongside lint, type-check, and performance. It produces a report with concrete evidence for each criterion, covering security vulnerabilities and test coverage gaps on a per-file basis.

This code review applies specifically to Django-based projects and multi-file changes. It evaluates Django-specific patterns like Fat Model, FBV, PRG, and soft delete, meaning it may not provide accurate architectural assessments for non-Django frameworks.