rumo-database-change-safety SKILL.md skillA
rumo-database-change-safety from rumoii/rumo-engineering-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add rumoii/rumo-engineering-skills/rumo-database-change-safety@git:20261026.bef6e05Pins git:20261026.bef6e05 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- rumoii/rumo-engineering-skills
- Path
skills/rumo-database-change-safety/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261026.bef6e05, committed Oct 26, 2026
- First version recorded
- Oct 16, 2026
- Size
- 6,203 bytes
- Repository stars
- 9
- License
- MIT
Use when planning, reviewing, generating, testing, or executing any write to an application database, including schema migrations, new columns, backfills, data repairs, cleanup, resets, destructive SQL, restores, and rollback. Start read-only, identify the exact database and application versions, require explicit authorization before changing any existing or persistent database, and prove backup, compatibility, bounded effects, and rollback readiness. Use rumo-debug instead for purely…
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
# Rumo Database Change Safety A database change is a data-lifecycle operation, not a SQL statement. A migration that exits successfully is not done until existing data, application compatibility, recovery, and business behavior are checked. ## The Write Boundary - Start read-only. Writing migration code, reviewing SQL, fixing an application bug, or investigating an environment does not authorize changing an existing database. - Writes include migration runners, `INSERT`, `UPDATE`, `DELETE`, `MERGE`, `TRUNCATE`, `ALTER`, `CREATE`, `DROP`, import tools, repair jobs, reset scripts, and application endpoints or jobs that mutate stored data. - A disposable database created and owned by an isolated test run may be changed freely. - Any existing local, shared, remote, staging, production, or customer database needs either the user's direct instruction to run against that exact target, or explicit approval after seeing the plan. - Never infer the target from a familiar hostname, earlier deployment, environment variable, screenshot, or package name. Stop when the database identity, write authorization, or recovery owner is unclear. …
Read the whole file at its exact version.
How to install
mdr add rumoii/rumo-engineering-skills/rumo-database-change-safety@sha256:c53b13790fc170eaThe line at the top of this page pins the label git:20261026.bef6e05, 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_zjp3wpykdty2cbqn)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Oct 16, 2026 and Oct 26, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261026.bef6e05 latest | 2026-10-26 | bef6e05 | 6,203 B | A | view · diff |
| git:20261017.cd37f56 | 2026-10-17 | cd37f56 | 6,178 B | A | view · diff |
| git:20261017.eaea6d9 | 2026-10-17 | eaea6d9 | 5,248 B | A | view · diff |
| git:20261016.0003443 | 2026-10-16 | 0003443 | 5,151 B | A | view · diff |
| git:20261016.7812090 | 2026-10-16 | 7812090 | 12,761 B | A | view · diff |
| git:20261016.65fcbd4 | 2026-10-16 | 65fcbd4 | 12,787 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 (6203 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
rumoii/rumo-engineering-skills · 9 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zjp3wpykdty2cbqn GET https://markdownregistry.com/api/v1/resolve?ref=rumoii/rumo-engineering-skills/rumo-database-change-safety GET https://markdownregistry.com/api/v1/blob/c53b13790fc170ea6dba043cb324a0a739a78c0f508ecfcbacc90dfeddbd96c2
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.