django-verification

Runs a multi-phase verification pipeline covering Django migrations, tests, security scans, and deployment readiness.

1|Updated Oct 11, 2025
One-click install
npx skills add https://github.com/ibytechaos/claude --skill django-verification-ibytechaos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: django-verification
Source: https://github.com/ibytechaos/claude/tree/main/plugins/everything-claude-code/skills/django-verification
Command: npx skills add https://github.com/ibytechaos/claude --skill django-verification-ibytechaos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Django projects often ship with unapplied migrations, low test coverage, vulnerable dependencies, or unsafe production settings. This Skill runs a structured 12-phase verification loop that catches these issues before a pull request or deployment. ## Core Features & Use Cases - Full Quality Pipeline: Executes environment checks, mypy/ruff/black linting, migration validation, pytest with coverage targets, and security scans via pip-audit, bandit, and gitleaks. - Deployment Readiness: Verifies DEBUG, SECRET_KEY, ALLOWED_HOSTS, HTTPS/HSTS settings, static assets, logging, and DRF schema generation, then produces a structured verification report. - Use Case: Before merging a feature branch with new models, run the verification loop to confirm migrations exist, coverage stays above 80%, no vulnerable dependencies were introduced, and production settings are safe. ## Quick Start Run the Django verification loop on my project before I open a pull request and report any failing phases.

Frequently Asked Questions about django-verification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a Django project before deployment?

Run a phased verification covering environment checks, ruff/black/mypy linting, migration validation with manage.py makemigrations --check, pytest with coverage, and security scans via pip-audit and bandit. Finish with manage.py check --deploy to validate production settings.

How to check test coverage in a Django project?

Use pytest with pytest-cov: run pytest --cov=apps --cov-report=term-missing to get per-app coverage. Typical targets are 90% for models, 85% for serializers, 80% for views, and 80% overall.

What security checks should Django projects run before release?

Run pip-audit and safety for dependency vulnerabilities, bandit for insecure code patterns, gitleaks for hardcoded secrets, and manage.py check --deploy for Django security settings. Also confirm DEBUG is False and SECRET_KEY is properly configured.

Does this verification work with Django REST Framework APIs?

Yes. It includes a phase for DRF projects that generates an OpenAPI schema with manage.py generateschema and validates the resulting JSON, plus checks Swagger UI availability when drf-yasg is installed.

Why does Django migration verification fail before a PR?

Failures usually come from model changes without generated migrations, unapplied migrations, or conflicting migration branches. Use makemigrations --check to detect missing migrations and migrate --plan to preview pending changes.