agentleFS
Sign inStart free
chrysogonuschrysogonus/prompt-maker-studio/.claude/skills/db-migration/SKILL.md

db-migration

Skill7 starsChanged 18 days agoApache-2.0View on GitHub

Add or modify a database column/table in Prompt Maker Studio's SQLite schema, using the repo's custom idempotent migration runner (no Alembic). Use when asked to change the database schema, add a column, add a table, or migrate the database.

26 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use api-endpoint, write-tests and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • tadoEngSkill

    api-endpoint

    Add or change a backend API endpoint on this product, keeping Pydantic as the single contract authority and regenerating the TypeScript client. Use when asked to add an endpoint, expose data to the frontend, change a request or response shape, or wire a new backend capability into a page.

    Also in 4 projects that use this

  • SentrySkill

    write-tests

    Write tests following project conventions. Use when adding new tests or modifying existing ones.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    git-workflow

    Squad branching model: dev-first workflow with insiders preview channel

    Also in 3 projects that use this

  • Microsoft AzureSkill

    design

    Design rules and conventions for the API Center Portal. Use when editing detail pages, card components, badges, layout, navigation, sidebars, or headers. Covers badge styling, metadata placement, page navigation patterns, and layout alignment.

    Also in 3 projects that use this

  • AnthropicSkill

    debug

    Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.

    Also in 3 projects that use this

  • VercelSkill

    agent-browser

    Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

    Also in 3 projects that use this

  • +1 more from Azure

The file

Create a free account to mount
Files
SKILL.md

Database schema change

This repo does not use Alembic or any migration-tool CLI. Do not run a .sql file directly against a database, and do not hand-edit rows in schema_migrations.

The real mechanism:

  1. Update the SQLAlchemy model in backend/app/models/ (the matching entity module) to reflect the new column/table — this is what Base.metadata.create_all(...) uses for fresh databases. Re-export new models from backend/app/models/__init__.py; declare appropriate ORM and database delete behavior for owned data.
  2. Add a migration step as a new vNNN_*.py module in backend/app/database/migrations/, then register its stable ID and function in registry.py. Follow the pattern of existing numbered migrations (read backend/app/database/migrations/registry.py for the next ID and backend/migrations/README.md for historical behavior) — each backfills/adds what create_all() can't change on an existing SQLite table, and the runner records the completed ID in schema_migrations. Keep applied IDs and ordering stable; make the step idempotent and preserve historical upgrade behavior.
  3. Document the upgrade — add the migration to backend/migrations/README.md. Add a reference .sql file in backend/migrations/ with the same number as the registered step, documenting the equivalent raw SQL — this is a historical reference only, never executed directly by the app or by you.
  4. Update Pydantic schemas in backend/app/schemas/ if the new column is exposed via the API.
  5. Write/extend tests — backend/tests/test_migrations.py covers legacy-schema upgrade and idempotency; add a case there for the new migration step. Also check backend/tests/test_models.py / test_schemas.py if the model or schema shape changed.
  6. Verify: .venv/bin/pytest backend/tests/test_migrations.py backend/tests/test_backup_restore.py -q, then make lint-backend && make test.

Full detail and the production deployment checklist (backup before deploy, verify migration log lines, restore procedure if validation fails): backend/migrations/README.md. Do not run make restore-db yourself — that's a human-confirmed, production-affecting action.

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