migrations skillA
migrations is agent-read markdown (skill) from nahid-sparktales/agent-dispatcher: Change a live schema without breaking the application on it — expand/contract sequencing, lock-safe DDL, batched backfills, and a rollback that is actually reachable. Use when writing, reviewing or sequencing a migration that will run against a database holding real data with live readers. Not for designing a schema from scratch, not for proving afterwards that a migration did what it claimed (that is database-migration-verification), and it never runs the production step for you..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Live schema migrations A migration that passes on an empty dev database proves the SQL parses. It says nothing about how long the lock is held, whether the old application version still reads the column you dropped, or whether the rollback can reach the data. ## When this fires You are about to write, review or sequence a schema or data migration against a database that has rows in it and something reading them. It does not fire for greenfield schema design, for a throwaway local database, or for a query change with no DDL. ## Procedure 1. **Read the current state before writing any SQL.** The live schema, the migration history, and every reader of the objects you are touching — grep the application, the reports, the jobs, the other services. A column no code in this repo reads may still be read by a deployed older version. Name the readers you found; say if you could not enumerate them. 2. **Classify the change.** *Additive* (new table, new nullable column, new index), *rewriting* (type change, adding NOT NULL or a unique constraint to existing data, renaming, dropping), or …
Read the whole file at its exact version.
How to install
mdr add nahid-sparktales/agent-dispatcher/migrations@git:20260919.a0d4f55mdr add nahid-sparktales/agent-dispatcher/migrations@sha256:0c47e48966b31a62Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_nznevpdxxwnpiek4)
1 badge views in 30 days
Versions
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 (7295 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
nahid-sparktales/agent-dispatcher · 49 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_nznevpdxxwnpiek4 GET https://markdownregistry.com/api/v1/resolve?ref=nahid-sparktales/agent-dispatcher/migrations GET https://markdownregistry.com/api/v1/blob/0c47e48966b31a626044dbea18eb969e96b0a4228cdc2d50426b22f3cd9922a4
Your agent 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.