django-verification

Automate Django project verification for migrations, quality, and security.

6|Updated Mar 25, 2023
One-click install
npx skills add https://github.com/songkg7/dotfiles --skill django-verification-songkg7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: django-verification
Source: https://github.com/songkg7/dotfiles/tree/main/dot_claude/skills/django-verification
Command: npx skills add https://github.com/songkg7/dotfiles --skill django-verification-songkg7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Django projects frequently slip into releases with migrations drift, missing tests, linting gaps, and insecure configurations. This Skill provides a repeatable verification loop to detect these issues before PRs or deployments.

Core Features & Use Cases

  • Migrations checks: identify unapplied migrations, conflicts, and migration hygiene before deploys.
  • Code quality & security: run mypy, ruff, black, isort, and security scans to enforce standards.
  • Deployment readiness: validate settings, static assets, and Django management tasks to ensure a smooth release.

Quick Start

This Quick Start follows Phase 1 through Phase 12 in the Skill body. Execute the steps in order in your Django project root to perform environment checks, code quality tasks, migrations, tests, security scans, and deployment readiness verifications.

Frequently Asked Questions about django-verification

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

FAQPage Schema
How do I automate Django pre-deployment verification for migrations and security?

Django pre-deployment verification automates checks for migration drift, code quality, and security gaps by running mypy, ruff, bandit, safety, and pip-audit to ensure release readiness across PRs and feature branches.

What's the best way to check for missing Django migrations before a release?

Checking missing Django migrations before a release involves identifying unapplied migrations, conflicts, and migration hygiene using automated verification workflows that validate database state against current models.

Do I need pytest-django and mypy installed to run Django deployment readiness checks?

Yes, Django deployment readiness checks require pytest-django, mypy, ruff, black, isort, bandit, safety, and pip-audit installed to perform type checking, testing, static analysis, and security scanning.

Can I run Django security scans and linting together in a single verification workflow?

Yes, Django security scans and linting can run together in a single verification workflow that executes mypy, ruff, black, isort, bandit, safety, and pip-audit sequentially to enforce code quality and security standards.

Why does my Django release fail due to insecure configurations and migration conflicts?

Django releases fail due to insecure configurations and migration conflicts when verification workflows are skipped, allowing settings defects, unapplied migrations, and security gaps to reach production undetected.

What Django configuration reviews are needed to ensure a smooth release?

Django configuration reviews for smooth releases validate settings, static assets, and management tasks to ensure deployment readiness, catching insecure configurations and missing dependencies before they impact production.