sqlite-schema-versioning

Name: sqlite-schema-versioning
Author: GuilhermeFerrarezi

Use when a schema change needs versioned migration and legacy compatibility.

by GuilhermeFerrarezi(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Imported from GuilhermeFerrarezi/biblioteca-de-jogos-unificada (cloud - biblioteca de jogos/skills/sqlite-schema-versioning/SKILL.md). Install upstream with npx skills add GuilhermeFerrarezi/biblioteca-de-jogos-unificada --skill sqlite-schema-versioning. Copyright stays with the author.

SQLite Schema Versioning

Use when

The local schema changes in a backward-sensitive way.
Legacy databases need to keep working.
Migration history must stay explicit.

Checklist

Record a version for the change.
Keep migrations incremental and idempotent.
Test upgrade from legacy data.
Preserve user records and settings.

Output

Schema version:
Tables affected:
Migration path:
Legacy support:
Tests:
Risks:

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot
curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

guilhermeferrarezi-biblioteca-de-jogos-unificada-sqlite-6b5d8e.ocm.jsonjson

{
  "ocm": "1",
  "id": "guilhermeferrarezi-biblioteca-de-jogos-unificada-sqlite-6b5d8e",
  "kind": "skill",
  "name": "sqlite-schema-versioning",
  "description": "Use when a schema change needs versioned migration and legacy compatibility.",
  "publisher": "GuilhermeFerrarezi",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "github"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Use when a schema change needs versioned migration and legacy compatibility."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github",
      "repository": "https://github.com/GuilhermeFerrarezi/biblioteca-de-jogos-unificada",
      "path": "cloud - biblioteca de jogos/skills/sqlite-schema-versioning/SKILL.md",
      "ref": "8132eb7ba1de664306ef5d20143069f3673eef94",
      "url": "https://github.com/GuilhermeFerrarezi/biblioteca-de-jogos-unificada/blob/8132eb7ba1de664306ef5d20143069f3673eef94/cloud - biblioteca de jogos/skills/sqlite-schema-versioning/SKILL.md",
      "key": "GuilhermeFerrarezi/biblioteca-de-jogos-unificada/cloud - biblioteca de jogos/skills/sqlite-schema-versioning/SKILL.md"
    }
  },
  "instructions": "# SQLite Schema Versioning\n\n## Use when\n\n- The local schema changes in a backward-sensitive way.\n- Legacy databases need to keep working.\n- Migration history must stay explicit.\n\n## Checklist\n\n- Record a version for the change.\n- Keep migrations incremental and idempotent.\n- Test upgrade from legacy data.\n- Preserve user records and settings.\n\n## Output\n\n```text\nSchema version:\nTables affected:\nMigration path:\nLegacy support:\nTests:\nRisks:\n```",
  "cost": {
    "context_tokens": 111
  }
}

Fetch it by URL: GET /api/v1/registry/guilhermeferrarezi-biblioteca-de-jogos-unificada-sqlite-6b5d8e/manifest?version=1.0.0