agentleFS
Sign inStart free
aprameyakaprameyak/coding-skills/database-changes/SKILL.md

database-changes

Skill1 starsChanged 41 days agoMITView on GitHub

Make safe schema and query changes. Use when writing migrations, altering tables, adding indexes, or changing data access.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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
  1. Distinctive:

    Prefer additive, backward-compatible migrations first.

    line 10
  2. Distinctive:

    Test migrations up (and down if supported) on realistic data volume when possible.

    line 14
  3. Distinctive:

    Never drop/rename columns in the same release that still reads them.

    line 18
  4. Distinctive:

    Avoid long locks on hot tables.

    line 19

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Database Changes

Process

  1. Prefer additive, backward-compatible migrations first.
  2. Separate schema deploy from code that depends on destructive changes when zero-downtime matters.
  3. Name migrations clearly; make them idempotent when the tool allows.
  4. Index for real query patterns; avoid unused indexes.
  5. Test migrations up (and down if supported) on realistic data volume when possible.

Safety

  • Never drop/rename columns in the same release that still reads them.
  • Avoid long locks on hot tables; use online/concurrent strategies supported by the DB.
  • Backfill in batches; checkpoint progress.
  • Backup/restore plan for destructive ops.
  • Parameterize all queries; no string-built SQL with untrusted input.

Checklist

  • Migration is reversible or explicitly marked irreversible
  • App compatibility across expand/contract phases considered
  • Heavy locks avoided or scheduled
  • Data integrity constraints defined

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free