upgrade-django SKILL.md skillA
upgrade-django from phaedra-solutions/cursor-rules is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add phaedra-solutions/cursor-rules/upgrade-django@git:20261029.8ceb69aPins git:20261029.8ceb69a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- phaedra-solutions/cursor-rules
- Path
skills/upgrade-django/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261029.8ceb69a, committed Oct 29, 2026
- Size
- 5,270 bytes
- Repository stars
- 4
- License
- MIT
Upgrade a Django project one feature release at a time (for example 4.2 → 5.0 → 5.1 → 5.2 LTS, then 6.x) with django-upgrade --target-version, deprecation warnings as errors, add-on (DRF, django-cors-headers, Celery) compatibility, Python compatibility, migrations checks and check --deploy, then verify with tests and a smoke test. Use when asked to upgrade Django, when legacy/django-legacy applies (4.2 LTS ended 7 Apr 2026), or when a security fix needs a newer release.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Upgrade Django ## When to use - The user asks to upgrade Django, or the project is below 5.2 (see `legacy/django-legacy`). - A security fix exists only in a supported release (5.2, 6.0, 6.1). - Moving from 5.2 LTS to 6.x as a planned change. For a patch release within the same feature release, update the pin and run Verify. ## Before you start - Read `django`, Python, and every Django add-on with its supported Django range: `djangorestframework` (3.17 supports 4.2–6.0; 3.18 needs 5.2+), `django-cors-headers`, `django-filter`, `celery`/`django-celery-*`, `django-allauth`, `django-storages`, `channels`, admin themes, and anything with its own migrations. - Python compatibility per target: 5.2 supports 3.10–3.14; 6.0 and 6.1 need 3.12+. Plan `upgrade-python` first if needed. - Working tree clean; new branch (`chore/django-5.2`). - Ask the user: - the target (default: **5.2 LTS**, security support to Apr 2028; 6.1 if they want the newest and can take Python 3.12+); - whether to stop after each feature release for review; - whether network installs are approved (`core/supply-chain` cooldown applies). …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_g6mhvhvymkj5ywwu/8a9798206f7cfc8fbc9d7cc110f40c921d2989e69e858bfd6fd58396f83bc69e.json
Then /plugin install upgrade-django@markdownregistry-g6mhvhvymkj5ywwu in Claude Code. It installs git:20261029.8ceb69a, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add phaedra-solutions/cursor-rules/upgrade-django@sha256:8a9798206f7cfc8fThe line at the top of this page pins the label git:20261029.8ceb69a, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_g6mhvhvymkj5ywwu)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in phaedra-solutions/cursor-rules/upgrade-django since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of upgrade-django from somewhere else? Ask it: where did my upgrade-django come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Oct 29, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/upgrade-django/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5270 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
phaedra-solutions/cursor-rules · 4 stars · license MIT · pushed 2026-11-02 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_g6mhvhvymkj5ywwu GET https://markdownregistry.com/api/v1/resolve?ref=phaedra-solutions/cursor-rules/upgrade-django GET https://markdownregistry.com/api/v1/blob/8a9798206f7cfc8fbc9d7cc110f40c921d2989e69e858bfd6fd58396f83bc69e
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.