upgrade-backend-deps SKILL.md skillA
upgrade-backend-deps from tam159/next-role is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tam159/next-role/upgrade-backend-deps@git:20260904.adadf35Pins git:20260904.adadf35 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tam159/next-role
- Path
.agents/skills/upgrade-backend-deps/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260904.adadf35, committed Sep 4, 2026
- First version recorded
- Jul 10, 2026
- Size
- 15,612 bytes
- Repository stars
- 62
- License
- MIT
Upgrade Python backend dependencies to their latest compatible versions. Resolves the lockfile with `uv lock --upgrade`, syncs the venv, bumps the matching `>=` pins in `backend/pyproject.toml` and `ruff-pre-commit` rev in `.pre-commit-config.yaml`, runs the backend unit tests, rebuilds the backend Docker image if requested, verifies thread state still loads on the restarted stack, opens a PR with the change (watching CI for upgrade fallout), and reports what moved vs. what stayed pinned by…
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 the backend's Python dependencies, reconcile the version pins in tracked config, and (optionally) rebuild the Docker image so the running container picks up the new versions. ## Workflow ### 1. Resolve and sync ```bash cd backend uv lock --upgrade 2>&1 | tee /tmp/uv-upgrade.log uv sync ``` `uv lock --upgrade` re-resolves every dep against PyPI within the constraint set in `pyproject.toml`. Its stdout lists every `Updated <pkg> vX -> vY` line — that diff is the source of truth for steps 2, 3, 5, and 11. Keep it. If the log shows `Resolved N packages` with no `Updated` lines, also check whether the lockfile itself changed: ```bash git diff --stat backend/uv.lock ``` - **No diff at all** → truly up to date. Stop and report "already up to date." …
Read the whole file at its exact version.
How to install
mdr add tam159/next-role/upgrade-backend-deps@sha256:8750c1fccbfc5a61The line at the top of this page pins the label git:20260904.adadf35, 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_7xc6ko3wnyn3xhgq)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jul 10, 2026 and Sep 4, 2026, about one every 56 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260904.adadf35 latest | 2026-09-04 | adadf35 | 15,612 B | A | view · diff |
| git:20260710.ecf66e2 | 2026-07-10 | ecf66e2 | 10,911 B | A | view |
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 (15612 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
tam159/next-role · 62 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7xc6ko3wnyn3xhgq GET https://markdownregistry.com/api/v1/resolve?ref=tam159/next-role/upgrade-backend-deps GET https://markdownregistry.com/api/v1/blob/8750c1fccbfc5a61bf235eec9ac376a7bd797455ae726d835ff1840b4015de53
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.
More from tam159/next-role
Every file in tam159/next-role