database-changes
Skill2 starsChanged 56 days agoMITView on GitHub
Use when changing a database schema, migration, query contract, index, or persisted data shape.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- getvibekits/vibe-coding-rulestheir own version, first seen Oct 25, 2026
- aprameyak/coding-skillstheir own version, first seen Oct 2, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- aprameyak/coding-skills★ 1same name
- getvibekits/vibe-coding-rules★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- code-reviewSkill
- coding-best-practicesSkill
- debuggingSkill
- dependency-managementSkill
- documentationSkill
- git-workflowSkill
- release-managementSkill
- securitySkill
- testingSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Prefer backward-compatible expand-and-contract changes.
- Distinctive: line 11
Test both a fresh database and an upgrade from the last supported schema.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Database changes
- Identify supported database versions, data volume, deployment order, and whether old and new application versions overlap.
- Prefer backward-compatible expand-and-contract changes. Separate destructive cleanup from the change that stops using old data.
- Make migrations deterministic, restartable where practical, and observable. Avoid long locks; explain backfill and rollback behavior.
- Test both a fresh database and an upgrade from the last supported schema. Review query plans for index-sensitive changes.
Done when deployment order is safe, existing data has a defined path, and recovery does not depend on guesswork.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.