django-verification_skill

Overview

This skill runs a repeatable verification loop for Django projects to validate migrations, code quality, tests with coverage, security scans, and deployment readiness before PRs or releases. It automates environment checks, linting, type checking, migration validation, test execution, security audits, and configuration reviews. The goal is fast, actionable reports and a clear pre-deploy checklist to reduce production risk.

How this skill works

The skill executes a staged pipeline: environment validation, formatting and static analysis (mypy, ruff, black, isort), migration inspection and dry-run, pytest with coverage, dependency and code security scans (pip-audit, bandit, safety), and configuration and performance checks. It aggregates results into a concise verification report and a prioritized next-steps list. Outputs include test counts, coverage percentages, security findings, migration status, and a pass/fail recommendation for deployment.

When to use it

• Before opening a pull request for Django changes
• After modifying models, migrations, or dependencies
• As a pre-deployment gate for staging or production
• On CI for continuous verification on push and pull_request events
• When enforcing coverage and security thresholds before release

Best practices

• Run in an isolated, reproducible environment (CI container or consistent dev VM) with required env vars set
• Fail fast on misconfigured environment or unapplied migrations to avoid false positives
• Enforce coverage targets per component and block merge if overall coverage is below threshold
• Auto-fix formatting and import ordering in pre-commit hooks; keep type checks in CI
• Treat pip-audit/bandit findings as actionable tickets and prioritize fixes before deploy

Example use cases

• CI job that runs the full verification pipeline on pull requests and blocks merges on failures
• Pre-release script developers run locally to ensure migrations, tests, and static assets are ready
• Security triage after dependency upgrades to identify vulnerable packages before production deploy
• Staging acceptance check to confirm DEBUG=False, secret keys, ALLOWED_HOSTS, and logging configuration are correct
• Audit run after refactors to ensure no debug statements, TODOs, or hardcoded secrets slipped into diffs