Borrowing it
Nothing to install: this file belongs to jpicklyk/task-orchestrator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jpicklyk/task-orchestrator/main/.claude/skills/migration-review/SKILL.mdgit clone --depth 1 https://github.com/jpicklyk/task-orchestratorWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/jpicklyk/task-orchestrator/migration-review)<a href="https://agentmods.dev/skills/jpicklyk/task-orchestrator/migration-review"><img src="https://agentmods.dev/badge/skills/jpicklyk/task-orchestrator/migration-review.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00047 | $0.00572 |
| Opus 5 | $0.00023 | $0.00286 |
| Sonnet 5 | $0.00009 | $0.00114 |
| Haiku 4.5 | $0.00005 | $0.00057 |
Grade A, and why
migration-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migration Review Framework
Evaluate database migration safety for SQLite-specific constraints. This project uses Flyway migrations with SQLite, which has significant limitations compared to PostgreSQL/MySQL.
Step 1: Identify Schema Changes
Read the changed files and migration SQL to determine:
- New columns —
ALTER TABLE ADD COLUMNworks in SQLite - Modified columns — SQLite has NO
ALTER COLUMN. Requires table recreation:- Create new table with desired schema
- Copy data from old table
- Drop old table
- Rename new table
- New tables — check foreign key ordering in
DirectDatabaseSchemaManager - Index changes —
CREATE INDEX/DROP INDEXwork normally
Step 2: SQLite Constraint Check
Verify against known SQLite limitations:
- No
ALTER COLUMN— if modifying existing columns, table recreation pattern is used - No
DROP COLUMNin older SQLite versions — check if the Docker image's SQLite supports it - Foreign key constraints — new tables must be inserted in correct order in
DirectDatabaseSchemaManager -
TEXTaffinity — SQLite stores all strings as TEXT regardless of declared type - No concurrent write transactions — migrations must be sequential
Step 3: Data Migration Strategy
For migrations that modify existing data:
- Existing rows handled — default values for new columns, or explicit data migration
- Null safety — new NOT NULL columns require a DEFAULT or data backfill
- Large table performance — SQLite locks the entire database during writes
Step 4: Flyway Integration
- Migration file follows naming:
V{N}__{Description}.sql - Version number is sequential (no gaps, no conflicts with existing migrations)
- Migration is idempotent where possible
-
DirectDatabaseSchemaManagerupdated if new tables are added (insert in FK dependency order)
Step 5: Rollback Considerations
- Can the migration be reversed manually if needed?
- Is the schema change backward compatible with the previous application version?
- Docker volume data survives container restarts — migration is permanent
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 55 lines · 47 tokens per session scan A 86081aa7398e
migration-review is a skill published in the GitHub repository jpicklyk/task-orchestrator (206 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 572 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
postgresql
PostgreSQL schema design, query optimization, indexing, and administration. Use when working with PostgreSQL, JSONB, partitioning, RLS, CTEs, window functions, or EXPLAIN ANALYZE.
data-storage-migrations
Use this capability for database schema design, SQL/NoSQL selection, migrations, indexing, query review, connection pooling, backups, object storage, event storage, data retention, and data lifecycle planning. Trigger on database, schema, migration, index, SQL, PostgreSQL, MySQL, MongoDB, Redis, S3, ORM, transaction…
multitenancy-rls-isolation
Use this capability whenever multi-tenancy, tenant isolation, Row-Level Security, shared-schema SaaS, organization-scoped data, tenantid, database policies, cross-tenant access, or tenant-aware caching appears. Trigger even if the user only says “orgs”, “workspaces”, “teams”, “customers”, or “B2B SaaS”.
performance-caching-rate-limits
Use this capability for performance optimization, load tests, k6/JMeter/Locust plans, caching, Redis, CDN, Cache-Control, invalidation, rate limiting, quotas, token bucket, sliding window, 429 behavior, abuse protection, and cost-based throttling.
database-design
Guides data-layer decisions for application backends, covering schema modeling, index strategy, ORM and database engine selection, query tuning, and migration planning. Applies when shaping a new schema, weighing storage engines or ORMs, planning safe migrations, diagnosing slow queries, or touching Prisma, Drizzle…
sqlite
Teaches SQLite development including WAL mode, FTS5 full-text search, JSON1 queries, and async Python integration with aiosqlite. USE WHEN the user asks to "set up a SQLite database", "use WAL mode", "add full-text search with FTS5", "store JSON in SQLite", "query SQLite with Python", "use better-sqlite3", "use…