Database Analysis
fossasia/eventyay-interpretation
A skill your agent uses to analyse, audit, or modify database models, migrations, and CRUD helpers.
SQLite migration assessment for items with the needs-migration-review trait.
Install Migration Review
$ npx skills add jpicklyk/task-orchestrator --skill migration-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jpicklyk/task-orchestrator migration-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jpicklyk/task-orchestrator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/migration-review .claude/skills/migration-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "migration-review" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/migration-review into .claude/skills/migration-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migration-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/migration-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jpicklyk/task-orchestrator --skill migration-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jpicklyk/task-orchestrator migration-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jpicklyk/task-orchestrator.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/migration-review .agents/skills/migration-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "migration-review" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/migration-review into .agents/skills/migration-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migration-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jpicklyk/task-orchestrator --skill migration-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jpicklyk/task-orchestrator migration-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jpicklyk/task-orchestrator.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/migration-review .cursor/skills/migration-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "migration-review" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/migration-review into .cursor/skills/migration-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migration-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jpicklyk/task-orchestrator.git --path .claude/skills/migration-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jpicklyk/task-orchestrator --skill migration-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jpicklyk/task-orchestrator migration-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jpicklyk/task-orchestrator.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/migration-review .gemini/skills/migration-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "migration-review" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/migration-review into .gemini/skills/migration-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migration-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jpicklyk/task-orchestrator migration-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jpicklyk/task-orchestrator --skill migration-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jpicklyk/task-orchestrator.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/migration-review .github/skills/migration-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "migration-review" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/migration-review into .github/skills/migration-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migration-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jpicklyk/task-orchestrator --skill migration-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jpicklyk/task-orchestrator migration-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jpicklyk/task-orchestrator.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/migration-review .opencode/skills/migration-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "migration-review" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/migration-review into .opencode/skills/migration-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migration-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
migration-review- GitHub stars
- 207
- Token cost
- ~886 tokens
- SKILL.md length
- 418 words
- Files
- 1
- Skills in repo
- 28
- Repo updated
- First seen
- Licence
- MIT
At a glance
SQLite migration assessment for items with the needs-migration-review trait.
- Works in 5 steps: Identify Schema Changes → SQLite Constraint Check → Data Migration Strategy → …
- Tasks that involve Database migrations
- SKILL.md covers Step 1: Identify Schema Changes, Step 2: SQLite Constraint Check, Step 3: Data Migration Strategy and Step 4: Flyway Integration, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Migration Review is an agent skill from jpicklyk/task-orchestrator. SQLite migration assessment for items with the needs-migration-review trait. Evaluates schema changes, table recreation patterns, data migration strategy, and Flyway migration correctness. Invoked via skillPointer when filling migration-assessment notes.
Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Databases, covering Database migrations. It works with SQLite. The repository describes itself as: Server-enforced workflow discipline for AI agents. An MCP server providing persistent work items, dependency graphs, quality gates, and actor attribution. Schemas define what… The licence is MIT.
When your agent uses it
- Tasks that involve Database migrations
Example prompts
- “/migration-review”
Requirements
- Docker
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit ed1b49b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Migration Review loads about 886 tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 418 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jpicklyk/task-orchestrator at commit ed1b49b, republished under its MIT licence (© jpicklyk). 418 words, ~886 tokens.
Download SKILL.mdSave it as
.claude/skills/migration-review/SKILL.md (or your agent's skills folder).- name
- migration-review
- description
- SQLite migration assessment for items with the needs-migration-review trait. Evaluates schema changes, table recreation patterns, data migration strategy, and Flyway migration correctness. Invoked via skillPointer when filling migration-assessment notes.
- user-invocable
- false
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
- Runtime-dependent guarantees are probed, not assumed — see below
Guarantees that rest on engine runtime behavior need a multi-row probe. When the assessment claims an at-rest, security, or data-integrity guarantee that depends on a specific runtime/engine behavior (e.g. SQLite PRAGMA secure_delete, VACUUM page reuse, WAL checkpoint timing, FTS5 shadow-table residue), the assessment MUST specify a multi-row/multi-write empirical probe as part of the required test strategy — not a single-row assertion, which can read clean whether or not the mechanism works. It MUST NOT phrase the guarantee as absolute ("scrubbed", "removed") when only a probabilistic or partial mechanism is available ("reduces residue", "partial scrub"); once the probe exists, state the measured bound (e.g. "3–14 of 200 rows survive with the pragma, 200+ without").
Show full SKILL.md (89 more words)Show less
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
Output
Compose the migration-assessment note with findings from each step. Flag any SQLite-specific risks. Reference .claude/skills/spec-quality/references/project-concerns.md for additional codebase constraints.
© jpicklyk, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/migration-review of jpicklyk/task-orchestrator.
Open the folder on GitHubat commit ed1b49b
Compare with similar skills
Migration Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Migration Review this skilljpicklyk/task-orchestrator | 207 | — | ~886 | Automated safety check: Pass | MIT | |
| Database Analysisfossasia/eventyay-interpretation | 1.6k | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Cognee Database Migrationstopoteretes/cognee | 32k | — | ~2.6k | Automated safety check: Notes | Apache-2.0 | |
| Cursor BYOK Database Schemaleookun/cursor-byok | 3.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Migrationgocronx-team/gocron | 808 | — | ~1.1k | Automated safety check: Pass | MIT | |
| DeepChat Data Import HelperThinkInAIXYZ/deepchat | 6.4k | — | ~738 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Cognee Database Migrations
topoteretes/cognee
Explains how cognee's two migration chains run, how to check and repair migration state with cognee-cli, and how to write new Alembic or graph and vector migrations.
Cursor BYOK Database Schema
leookun/cursor-byok
Guides SQLite schema changes in the Cursor BYOK server, keeping SQLx migrations, the Rust store, API contracts and fixtures aligned.
Migration
gocronx-team/gocron
Create, review, or verify gocron database migrations across SQLite, MySQL, and PostgreSQL.
DeepChat Data Import Helper
ThinkInAIXYZ/deepchat
Guides building a third-party importer for DeepChat's local SQLite data, covering schema, encryption and safe read-only access patterns.
- Official
Prisma 8 Contract-First ORM
prisma/orm
Routes Prisma 8 tasks such as contracts, migrations, queries and upgrades to the right reference files for projects on the contract-first @prisma/orm packages.
More from jpicklyk/task-orchestrator
All 28 skills in this repoTask Orchestrator Server Setup
jpicklyk/task-orchestrator
Walks through how to launch and reach the MCP Task Orchestrator server container: transport, REST API, port publishing, config mounts and config-sync.
Run Wave
jpicklyk/task-orchestrator
Resolves ready MCP work items into a run plan, shows it to you, then executes it through the Workflow tool or direct subagent dispatch, with post-run verification.
Adopt Project Scope Migration
jpicklyk/task-orchestrator
Migrates an existing unscoped Task Orchestrator database to the project-scoping convention in place, creating one project anchor root and re-parenting work trees under it after a mandatory dry run.
Bulk Task Completion
jpicklyk/task-orchestrator
Completes or cancels a whole feature subtree, a named list of items, or a batch of stale work items at once, previewing the impact and warning before force-completing anything active.
Task Orchestrator Item Creator
jpicklyk/task-orchestrator
Creates an MCP work item from conversation context, anchoring it under the right container, inferring type and priority and pre-filling the required notes.
Work Item Dependency Manager
jpicklyk/task-orchestrator
Views, creates, deletes and diagnoses BLOCKS, IS_BLOCKED_BY and RELATES_TO links between MCP work items, including why an item cannot start.
Related
Works with
Categories
Questions about Migration Review
What does Migration Review do?
SQLite migration assessment for items with the needs-migration-review trait. Migration Review is an agent skill from jpicklyk/task-orchestrator. SQLite migration assessment for items with the needs-migration-review trait.
When should I use Migration Review?
Migration Review fits situations like: tasks that involve Database migrations.
How do I install Migration Review in Claude Code?
Run `npx skills add jpicklyk/task-orchestrator --skill migration-review -a claude-code`. Or copy the skill folder (.claude/skills/migration-review in jpicklyk/task-orchestrator) into .claude/skills/migration-review in your project. Claude Code loads it when a task matches its description.
How do I install Migration Review in Codex?
Run `npx skills add jpicklyk/task-orchestrator --skill migration-review -a codex`. Or copy the skill folder (.claude/skills/migration-review in jpicklyk/task-orchestrator) into .agents/skills/migration-review in your project. Codex loads it when a task matches its description.
Can I use Migration Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jpicklyk/task-orchestrator --skill migration-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/migration-review, .gemini/skills/migration-review, .github/skills/migration-review and .opencode/skills/migration-review in your project.
What does Migration Review need to run?
SKILL.md names no scripts, command-line tools or credentials: Migration Review is instructions for the agent only. Our summary lists: Docker.
Does Migration Review access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Migration Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Migration Review use?
Migration Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Migration Review use?
About 886 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Migration Review?
Skills that share tags, products or a category with Migration Review: Database Analysis (fossasia/eventyay-interpretation, 1.6k stars), Cognee Database Migrations (topoteretes/cognee, 32k stars), Cursor BYOK Database Schema (leookun/cursor-byok, 3.2k stars) and Migration (gocronx-team/gocron, 808 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Migration Review?
jpicklyk (a GitHub user) maintains it in jpicklyk/task-orchestrator, which has 207 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 9, 2026.
Source: jpicklyk/task-orchestrator on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.