django-verification

Run before PRs, after major changes, and pre-deploy to ensure Django application quality and security. If environment is misconfigured, stop and fix. Common issues: Report: Report: Coverage targets: Report: Report: Checklist: Remember: Automated verification catches common issues but doesn't replace manual code review and testing in staging environment. - Before opening a pull request for a Django project - After major model changes, migration updates, or dependency upgrades - Pre-deployment verification for staging or production - Running full environment → lint → test → security → deploy readiness pipeline - Validating migration safety and test coverage - Missing type hints on public functions - PEP 8 formatting violations - Unsorted imports - Debug settings left in production configuration - Number of pending migrations - Any migration conflicts - Model changes without migrations - Total tests: X passed, Y failed, Z skipped - Overall coverage: XX% - Per-app coverage breakdown - Vulnerable dependencies found - Security configuration issues - Hardcoded secrets detected - DEBUG mode status (should be False in production) - Number of queries per page (should be < 50 for typical pages) - Missing database indexes - Duplicate queries detected - No debugging statements (print, pdb, breakpoint()) - No TODO/FIXME comments in critical code - No hardcoded secrets or credentials -...