agentleFS
Sign inStart free
dosu-aidosu-ai/decant/.claude/skills/schema-migration/SKILL.md

schema-migration

Skill74 starsChanged 9 days agoApache-2.0View on GitHub

Change Decant's SQLite schema (tables, columns, indexes, triggers) or force a re-derive of existing archives. Use when editing src/db.ts migrations, src/schema.sql, src/schema-manifest.ts, LATEST_SCHEMA_VERSION, or INGEST_PIPELINE_REVISION.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. microsoft/PilotSwarm★ 14same name
    2. dafaalz/agent-skills★ 2same 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 repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run the migration against a scratch copy of a large archive and time it (DECANT_DB=<copy>).

    line 36
  2. Very specific:

    Update docs/data-lifecycle.md when archive state, sync, or migration behavior changes, and docs/architecture.md if module boundaries move.

    line 41

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

Schema migration

The rules are AGENTS.md invariant 5 and the "Rebuilds and migrations" section of docs/data-lifecycle.md. Read both before editing.

Rules

  • A migration is frozen once it is committed, because someone may already have opened an archive with that branch. Never edit an existing if (current < N) block, on main or on a feature branch; add a new one, even to fix a mistake in the previous one.
  • Bump LATEST_SCHEMA_VERSION in src/db.ts. Refer to that constant in docs instead of writing the number.
  • Guard each statement so a partially-migrated or operator-modified archive still converges (IF NOT EXISTS, hasTable, hasColumn), and stamp the new version in schema_migrations inside the same block.
  • src/schema.sql is the effective baseline for a fresh archive. Apply the same change there so a fresh archive and a migrated one produce the same buildSchemaManifest fingerprint; src/schema-manifest.ts changes only if the manifest needs to learn a new object kind.
  • Bump INGEST_PIPELINE_REVISION in src/ingest.ts only when unchanged source files must be re-derived. The next sync then backfills them once and later syncs stay idempotent. A pure index or constraint change does not need it.
  • Unsupported older archives are rebuild-only; do not add upgrade paths below the baseline.

Tests

  • test/db.test.ts: migrate a previous-version archive and compare it with a fresh one; assert any query plan the new index exists for.
  • Run the migration against a scratch copy of a large archive and time it (DECANT_DB=<copy>). Never point a migration at ~/.decant/decant.db.

Docs

Update docs/data-lifecycle.md when archive state, sync, or migration behavior changes, and docs/architecture.md if module boundaries move.

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