DB Migrations
kurealnum/dotfiles
A skill your agent uses when generating or regenerating Drizzle migration files, changing database schema tables or columns, resolving migration sequence conflicts after rebase, reviewing migration…
A skill your agent uses when the user says 'migration', 'schema change', 'database migration', 'alter table', 'add column', 'change type', 'rollback plan', or needs safe database schema evolution…
Install Memstack Development Migration Planner
$ npx skills add cwinvestments/memstack --skill memstack-development-migration-planner -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cwinvestments/memstack memstack-development-migration-planner --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/cwinvestments/memstack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/development/migration-planner .claude/skills/memstack-development-migration-planner && 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 "memstack-development-migration-planner" agent skill from https://github.com/cwinvestments/memstack/tree/master/skills/development/migration-planner into .claude/skills/memstack-development-migration-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memstack-development-migration-planner", 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/cwinvestments/memstack/tree/master/skills/development/migration-plannerType 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 cwinvestments/memstack --skill memstack-development-migration-planner -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cwinvestments/memstack memstack-development-migration-planner --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cwinvestments/memstack.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/development/migration-planner .agents/skills/memstack-development-migration-planner && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "memstack-development-migration-planner" agent skill from https://github.com/cwinvestments/memstack/tree/master/skills/development/migration-planner into .agents/skills/memstack-development-migration-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memstack-development-migration-planner", 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 cwinvestments/memstack --skill memstack-development-migration-planner -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cwinvestments/memstack memstack-development-migration-planner --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cwinvestments/memstack.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/development/migration-planner .cursor/skills/memstack-development-migration-planner && 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 "memstack-development-migration-planner" agent skill from https://github.com/cwinvestments/memstack/tree/master/skills/development/migration-planner into .cursor/skills/memstack-development-migration-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memstack-development-migration-planner", 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/cwinvestments/memstack.git --path skills/development/migration-planner--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 cwinvestments/memstack --skill memstack-development-migration-planner -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cwinvestments/memstack memstack-development-migration-planner --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cwinvestments/memstack.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/development/migration-planner .gemini/skills/memstack-development-migration-planner && 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 "memstack-development-migration-planner" agent skill from https://github.com/cwinvestments/memstack/tree/master/skills/development/migration-planner into .gemini/skills/memstack-development-migration-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memstack-development-migration-planner", 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 cwinvestments/memstack memstack-development-migration-plannerInstalls 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 cwinvestments/memstack --skill memstack-development-migration-planner -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cwinvestments/memstack.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/development/migration-planner .github/skills/memstack-development-migration-planner && 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 "memstack-development-migration-planner" agent skill from https://github.com/cwinvestments/memstack/tree/master/skills/development/migration-planner into .github/skills/memstack-development-migration-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memstack-development-migration-planner", 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 cwinvestments/memstack --skill memstack-development-migration-planner -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cwinvestments/memstack memstack-development-migration-planner --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cwinvestments/memstack.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/development/migration-planner .opencode/skills/memstack-development-migration-planner && 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 "memstack-development-migration-planner" agent skill from https://github.com/cwinvestments/memstack/tree/master/skills/development/migration-planner into .opencode/skills/memstack-development-migration-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memstack-development-migration-planner", 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
memstack-development-migration-planner- GitHub stars
- 423
- Token cost
- ~3.7k tokens
- SKILL.md length
- 716 words
- Files
- 1
- Skills in repo
- 87
- Repo updated
- First seen
- Licence
- Proprietary
At a glance
A skill your agent uses when the user says 'migration', 'schema change', 'database migration', 'alter table', 'add column', 'change type', 'rollback plan', or needs safe database schema evolution…
- Works in 8 steps: Gather Migration Requirements → Classify the Migration → Design the Migration → …
- The user says migration
- SKILL.md covers Activation, Context Guard, Common Mistakes and Protocol, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Memstack Development Migration Planner is an agent skill from cwinvestments/memstack. Use this skill when the user says 'migration', 'schema change', 'database migration', 'alter table', 'add column', 'change type', 'rollback plan', or needs safe database schema evolution with zero-downtime strategies. Do NOT use for initial database design (use database-architect) or code refactoring.
Its SKILL.md is about 3.7k 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 schema design, Database migrations and Refactoring. The repository describes itself as: Structured skill framework for Claude Code. 130 skills, persistent memory, TokenStack compression, localhost dashboard with 3-agent runner, real-time streaming, MCP tools.
When your agent uses it
- The user says migration
- Database migration
- Needs safe database schema evolution with zero-downtime strategies
- Initial database design (use database-architect)
Example prompts
- “migration”
- “schema change”
- “database migration”
- “/memstack-development-migration-planner”
Requirements
- Node.js
Workflow steps
8 steps, taken from the step headings in SKILL.md.
- Gather Migration Requirements
- Classify the Migration
- Design the Migration
- Data Backfill Strategy
- Write Rollback Procedures
- Validation Checkpoints
- Build Migration Plan
- Version Tracking
What it can do on your machine
Read from SKILL.md and the folder at commit 00370ce. 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 (its code samples are sql and markdown).
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
Memstack Development Migration Planner loads about 3.7k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 716 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
Its licence (Proprietary) doesn't allow us to republish the file, so here is its outline and opening line. It has 716 words (~3,654 tokens).
“Plans safe database schema migrations with zero-downtime strategies, rollback procedures, data validation checkpoints, and version tracking for PostgreSQL, MySQL, and SQLite.”
- name
- memstack-development-migration-planner
- version
- 1.0.0
- license
- Proprietary, MemStack™ Pro by CW Affiliate Investments LLC. See LICENSE.txt
Files
Just SKILL.md in skills/development/migration-planner of cwinvestments/memstack.
Open the folder on GitHubat commit 00370ce
Compare with similar skills
Memstack Development Migration Planner 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 |
|---|---|---|---|---|---|---|
| Memstack Development Migration Planner this skillcwinvestments/memstack | 423 | — | ~3.7k | Automated safety check: Pass | Proprietary | |
| DB Migrationskurealnum/dotfiles | 290 | — | ~820 | Automated safety check: Pass | None | |
| Change Database Schemamartin-ueding/geo-activity-playground | 100 | — | ~225 | Automated safety check: Pass | Custom licence | |
| Drizzlekurealnum/dotfiles | 290 | — | ~1.3k | Automated safety check: Pass | None | |
| Database Testingproffesor-for-testing/agentic-qe | 494 | 1 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Migrationkortix-ai/suna | 20k | — | ~1.2k | Automated safety check: Pass | Custom licence |
Similar skills
Change Database Schema
martin-ueding/geo-activity-playground
How to change the SQLAlchemy data model and generate the matching Alembic migration.
Drizzle
kurealnum/dotfiles
Drizzle ORM schema and database guide. An agent skill from kurealnum/dotfiles.
Database Testing
proffesor-for-testing/agentic-qe
Database schema validation, data integrity testing, migration testing, transaction isolation, and query performance.
Migration
kortix-ai/suna
How to change the database schema in this repo. An agent skill from kortix-ai/suna.
- Official
Content Modeling Best Practices
sanity-io/agent-toolkit
Structured content modeling guidance for schema design, content architecture, content reuse, references versus embedded objects, separation of concerns, and taxonomies across Sanity and other…
More from cwinvestments/memstack
All 87 skills in this repoMemstack SEO Site Audit
cwinvestments/memstack
A skill your agent uses when the user says 'SEO audit', 'site audit', 'check SEO', 'audit my site', 'SEO check', 'technical SEO', or is evaluating a website's search engine optimization health, meta…
Memstack SEO Schema Markup
cwinvestments/memstack
A skill your agent uses when the user says 'add schema', 'schema markup', 'JSON-LD', 'structured data', 'rich results', 'rich snippets', or is adding or fixing schema.org structured data for better…
Compress
cwinvestments/memstack
A skill your agent uses when the user says 'tokenstack', 'compression', 'token savings', 'proxy status', or asks about context window usage.
Diary
cwinvestments/memstack
A skill your agent uses when the user says 'save diary', 'log session', 'wrapping up', or at end of a productive session.
Echo
cwinvestments/memstack
A skill your agent uses when the user references past sessions, asks 'what did we do', 'do you remember', 'last session', 'recall', or 'continue from'.
Familiar
cwinvestments/memstack
A skill your agent uses when the user says 'dispatch', 'send familiar', 'split task', or needs work split across parallel CC sessions.
Related
Categories
Questions about Memstack Development Migration Planner
What does Memstack Development Migration Planner do?
A skill your agent uses when the user says 'migration', 'schema change', 'database migration', 'alter table', 'add column', 'change type', 'rollback plan', or needs safe database schema evolution…. Memstack Development Migration Planner is an agent skill from cwinvestments/memstack. Use this skill when the user says 'migration', 'schema change', 'database migration', 'alter table', 'add column', 'change type', 'rollback plan', or needs safe database schema evolution with zero-downtime strategies.
When should I use Memstack Development Migration Planner?
Memstack Development Migration Planner fits situations like: the user says migration; database migration; needs safe database schema evolution with zero-downtime strategies; initial database design (use database-architect).
How do I install Memstack Development Migration Planner in Claude Code?
Run `npx skills add cwinvestments/memstack --skill memstack-development-migration-planner -a claude-code`. Or copy the skill folder (skills/development/migration-planner in cwinvestments/memstack) into .claude/skills/memstack-development-migration-planner in your project. Claude Code loads it when a task matches its description.
How do I install Memstack Development Migration Planner in Codex?
Run `npx skills add cwinvestments/memstack --skill memstack-development-migration-planner -a codex`. Or copy the skill folder (skills/development/migration-planner in cwinvestments/memstack) into .agents/skills/memstack-development-migration-planner in your project. Codex loads it when a task matches its description.
Can I use Memstack Development Migration Planner 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 cwinvestments/memstack --skill memstack-development-migration-planner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/memstack-development-migration-planner, .gemini/skills/memstack-development-migration-planner, .github/skills/memstack-development-migration-planner and .opencode/skills/memstack-development-migration-planner in your project.
What does Memstack Development Migration Planner need to run?
SKILL.md names no scripts, command-line tools or credentials: Memstack Development Migration Planner is instructions for the agent only. Our summary lists: Node.js.
Does Memstack Development Migration Planner 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 Memstack Development Migration Planner 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 Memstack Development Migration Planner use?
Memstack Development Migration Planner carries a proprietary licence (declared in SKILL.md). It is published on GitHub, but it is not open source: read the licence file before using or sharing it.
How many tokens does Memstack Development Migration Planner use?
About 3.7k tokens (SKILL.md is roughly 15k 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 Memstack Development Migration Planner?
Skills that share tags, products or a category with Memstack Development Migration Planner: DB Migrations (kurealnum/dotfiles, 290 stars), Change Database Schema (martin-ueding/geo-activity-playground, 100 stars), Drizzle (kurealnum/dotfiles, 290 stars) and Database Testing (proffesor-for-testing/agentic-qe, 494 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Memstack Development Migration Planner?
cwinvestments (a GitHub user) maintains it in cwinvestments/memstack, which has 423 GitHub stars. The repository holds 87 skills in this directory. The repository was last updated on September 26, 2026.
Source: cwinvestments/memstack on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.