[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MDAN715SCPRS528A607N91":3,"skill-same:01M6MDAN715SCPRS528A607N91":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6MDAN715SCPRS528A607N91","data-migration",null,"Hard gate before any database schema change or data transformation in production. Requires a written migration plan with rollback strategy, dry run, and verification steps before execution. Prevents data loss, downtime, and irreversible schema changes.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1566,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002Fa-team\u002Fskills\u002Fdata-migration\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"data","data migration","migration","schema","changes","rollback strategy","with","dry","database schema","transformation","gate","change","strategy","rollback","plan","execution","Production","database","verification","run","2026-11-10 10:12:30",false,"---\nname: data-migration\ndescription: Hard gate before any database schema change or data transformation in production. Requires a written migration plan with rollback strategy, dry run, and verification steps before execution. Prevents data loss, downtime, and irreversible schema changes.\n---\n\n# Data Migration\n\n## The Law\n\n```\nEVERY MIGRATION NEEDS A ROLLBACK.\nA migration without a rollback plan is a one-way door.\nBefore you open it, know how to close it.\n```\n\n## When to Use\n\nUse this skill before:\n- Any `ALTER TABLE` in production\n- Any column rename, type change, or removal\n- Any large `UPDATE` or `DELETE` (more than 1000 rows)\n- Any index creation on a large table\n- Any data backfill or transformation script\n\n## The Migration Process\n\n### Step 1: Classify the Migration\n\n| Type | Risk | Strategy |\n|------|------|---------|\n| Additive (new table, new nullable column) | Low | Single deploy |\n| Non-breaking change (add index, add constraint) | Low–Medium | Verify impact first |\n| Column rename or type change | High | Multi-phase deploy |\n| Column or table removal | High | Multi-phase deploy |\n| Large data backfill (>100k rows) | Medium | Batched, off-peak |\n| Destructive (DROP TABLE, DELETE) | Critical | Backup + explicit approval |\n\n### Step 2: Write the Migration Plan\n\nSave to `docs\u002Fmigrations\u002FYYYY-MM-DD-description.md`:\n\n```markdown\n# Migration: [Title]\n\n## Summary\n[What changes and why]\n\n## Risk Level\n[Low \u002F Medium \u002F High \u002F Critical]\n\n## Migration Steps\n\n### UP (apply)\n\\```sql\n-- Step 1: Add new column (nullable — safe, no lock)\nALTER TABLE orders ADD COLUMN discount_amount NUMERIC(10,2);\n\n-- Step 2: Backfill (batched — see script)\n-- Run: scripts\u002Fmigrations\u002Fbackfill-discount.sql\n\n-- Step 3: Add NOT NULL constraint after backfill\nALTER TABLE orders ALTER COLUMN discount_amount SET NOT NULL;\n\\```\n\n### DOWN (rollback)\n\\```sql\nALTER TABLE orders DROP COLUMN IF EXISTS discount_amount;\n\\```\n\n## Rollback Plan\n[How to revert if something goes wrong — step by step]\n\n## Estimated Duration\n[How long will the migration take? Any locking risk?]\n\n## Verification\n- [ ] Row count before: SELECT COUNT(*) FROM orders;\n- [ ] Row count after matches\n- [ ] Sample rows spot-checked: SELECT * FROM orders LIMIT 10;\n- [ ] Application queries tested against migrated schema\n- [ ] No errors in application logs after deploy\n```\n\n### Step 3: Zero-Downtime Patterns\n\n**Column rename** — never rename directly; multi-phase:\n```\nPhase 1: Add new column (old and new both exist)\nPhase 2: Deploy app that writes to BOTH columns, reads from old\nPhase 3: Backfill new column from old\nPhase 4: Deploy app that writes to BOTH, reads from new\nPhase 5: Drop old column\n```\n\n**Type change** — same multi-phase approach; never `ALTER COLUMN TYPE` on large tables in production directly.\n\n**Index creation on large table** — always `CREATE INDEX CONCURRENTLY`:\n```sql\n-- [INVALID] — takes full table lock\nCREATE INDEX idx_orders_user ON orders(user_id);\n\n-- [VALID] — non-blocking on PostgreSQL\nCREATE INDEX CONCURRENTLY idx_orders_user ON orders(user_id);\n```\n\n**Large backfill** — never in one transaction; batch it:\n```sql\n-- Process in batches of 1000 rows until done\nDO $$\nDECLARE\n  batch_size INT := 1000;\n  rows_updated INT;\nBEGIN\n  LOOP\n    UPDATE orders\n    SET discount_amount = 0\n    WHERE discount_amount IS NULL\n    LIMIT batch_size;\n\n    GET DIAGNOSTICS rows_updated = ROW_COUNT;\n    EXIT WHEN rows_updated = 0;\n    PERFORM pg_sleep(0.1);  -- yield between batches\n  END LOOP;\nEND $$;\n```\n\n### Step 4: Pre-Migration Checklist\n\nBefore executing in production:\n\n- [ ] Migration tested in staging with production-sized dataset\n- [ ] DOWN migration tested — rollback actually works\n- [ ] Row counts recorded (before state documented)\n- [ ] Backup taken or verified recent backup exists\n- [ ] Maintenance window announced if locking is expected\n- [ ] Application can tolerate both old and new schema simultaneously (for multi-phase migrations)\n- [ ] Monitoring alerts active during migration\n\n### Step 5: Execute\n\n```bash\n# Dry run first (PostgreSQL)\npsql $DATABASE_URL --dry-run -f migration.sql\n\n# Real run with timing\npsql $DATABASE_URL -f migration.sql --echo-all\n\n# Check for locks during execution\nSELECT pid, query, state, wait_event_type, wait_event\nFROM pg_stat_activity\nWHERE state != 'idle';\n```\n\n### Step 6: Verify\n\n```sql\n-- Row count matches expectations\nSELECT COUNT(*) FROM affected_table;\n\n-- Sample spot-check\nSELECT * FROM affected_table LIMIT 20;\n\n-- No NULL where NOT NULL expected\nSELECT COUNT(*) FROM affected_table WHERE new_column IS NULL;\n\n-- No application errors in logs for 10 minutes post-migration\n```\n\n## Rollback Decision Tree\n\n```\nMigration complete?\n  └── No errors in monitoring for 10 minutes? → DONE\n  └── Errors found?\n      ├── Can app tolerate the error state? → Fix forward (hotfix)\n      └── Cannot tolerate? → ROLLBACK IMMEDIATELY\n          ├── Run DOWN migration\n          ├── Verify application recovers\n          └── Document in post-mortem\n```\n\n## Hard Rules\n\n- **Never DROP a column in the same deploy as the last code that reads it** — always separate by at least one deploy\n- **Never run destructive migrations (DROP TABLE, DELETE) without an explicit human approval step** — not just a code review\n- **Never skip the DOWN migration** — \"we can recreate it\" is not a rollback strategy\n- **Never migrate in peak traffic hours** — schedule for the lowest-traffic window\n","# Data Migration\n\n## The Law\n\n```\nEVERY MIGRATION NEEDS A ROLLBACK.\nA migration without a rollback plan is a one-way door.\nBefore you open it, know how to close it.\n```\n\n## When to Use\n\nUse this skill before:\n- Any `ALTER TABLE` in production\n- Any column rename, type change, or removal\n- Any large `UPDATE` or `DELETE` (more than 1000 rows)\n- Any index creation on a large table\n- Any data backfill or transformation script\n\n## The Migration Process\n\n### Step 1: Classify the Migration\n\n| Type | Risk | Strategy |\n|------|------|---------|\n| Additive (new table, new nullable column) | Low | Single deploy |\n| Non-breaking change (add index, add constraint) | Low–Medium | Verify impact first |\n| Column rename or type change | High | Multi-phase deploy |\n| Column or table removal | High | Multi-phase deploy |\n| Large data backfill (>100k rows) | Medium | Batched, off-peak |\n| Destructive (DROP TABLE, DELETE) | Critical | Backup + explicit approval |\n\n### Step 2: Write the Migration Plan\n\nSave to `docs\u002Fmigrations\u002FYYYY-MM-DD-description.md`:\n\n```markdown\n# Migration: [Title]\n\n## Summary\n[What changes and why]\n\n## Risk Level\n[Low \u002F Medium \u002F High \u002F Critical]\n\n## Migration Steps\n\n### UP (apply)\n\\```sql\n-- Step 1: Add new column (nullable — safe, no lock)\nALTER TABLE orders ADD COLUMN discount_amount NUMERIC(10,2);\n\n-- Step 2: Backfill (batched — see script)\n-- Run: scripts\u002Fmigrations\u002Fbackfill-discount.sql\n\n-- Step 3: Add NOT NULL constraint after backfill\nALTER TABLE orders ALTER COLUMN discount_amount SET NOT NULL;\n\\```\n\n### DOWN (rollback)\n\\```sql\nALTER TABLE orders DROP COLUMN IF EXISTS discount_amount;\n\\```\n\n## Rollback Plan\n[How to revert if something goes wrong — step by step]\n\n## Estimated Duration\n[How long will the migration take? Any locking risk?]\n\n## Verification\n- [ ] Row count before: SELECT COUNT(*) FROM orders;\n- [ ] Row count after matches\n- [ ] Sample rows spot-checked: SELECT * FROM orders LIMIT 10;\n- [ ] Application queries tested against migrated schema\n- [ ] No errors in application logs after deploy\n```\n\n### Step 3: Zero-Downtime Patterns\n\n**Column rename** — never rename directly; multi-phase:\n```\nPhase 1: Add new column (old and new both exist)\nPhase 2: Deploy app that writes to BOTH columns, reads from old\nPhase 3: Backfill new column from old\nPhase 4: Deploy app that writes to BOTH, reads from new\nPhase 5: Drop old column\n```\n\n**Type change** — same multi-phase approach; never `ALTER COLUMN TYPE` on large tables in production directly.\n\n**Index creation on large table** — always `CREATE INDEX CONCURRENTLY`:\n```sql\n-- [INVALID] — takes full table lock\nCREATE INDEX idx_orders_user ON orders(user_id);\n\n-- [VALID] — non-blocking on PostgreSQL\nCREATE INDEX CONCURRENTLY idx_orders_user ON orders(user_id);\n```\n\n**Large backfill** — never in one transaction; batch it:\n```sql\n-- Process in batches of 1000 rows until done\nDO $$\nDECLARE\n  batch_size INT := 1000;\n  rows_updated INT;\nBEGIN\n  LOOP\n    UPDATE orders\n    SET discount_amount = 0\n    WHERE discount_amount IS NULL\n    LIMIT batch_size;\n\n    GET DIAGNOSTICS rows_updated = ROW_COUNT;\n    EXIT WHEN rows_updated = 0;\n    PERFORM pg_sleep(0.1);  -- yield between batches\n  END LOOP;\nEND $$;\n```\n\n### Step 4: Pre-Migration Checklist\n\nBefore executing in production:\n\n- [ ] Migration tested in staging with production-sized dataset\n- [ ] DOWN migration tested — rollback actually works\n- [ ] Row counts recorded (before state documented)\n- [ ] Backup taken or verified recent backup exists\n- [ ] Maintenance window announced if locking is expected\n- [ ] Application can tolerate both old and new schema simultaneously (for multi-phase migrations)\n- [ ] Monitoring alerts active during migration\n\n### Step 5: Execute\n\n```bash\n# Dry run first (PostgreSQL)\npsql $DATABASE_URL --dry-run -f migration.sql\n\n# Real run with timing\npsql $DATABASE_URL -f migration.sql --echo-all\n\n# Check for locks during execution\nSELECT pid, query, state, wait_event_type, wait_event\nFROM pg_stat_activity\nWHERE state != 'idle';\n```\n\n### Step 6: Verify\n\n```sql\n-- Row count matches expectations\nSELECT COUNT(*) FROM affected_table;\n\n-- Sample spot-check\nSELECT * FROM affected_table LIMIT 20;\n\n-- No NULL where NOT NULL expected\nSELECT COUNT(*) FROM affected_table WHERE new_column IS NULL;\n\n-- No application errors in logs for 10 minutes post-migration\n```\n\n## Rollback Decision Tree\n\n```\nMigration complete?\n  └── No errors in monitoring for 10 minutes? → DONE\n  └── Errors found?\n      ├── Can app tolerate the error state? → Fix forward (hotfix)\n      └── Cannot tolerate? → ROLLBACK IMMEDIATELY\n          ├── Run DOWN migration\n          ├── Verify application recovers\n          └── Document in post-mortem\n```\n\n## Hard Rules\n\n- **Never DROP a column in the same deploy as the last code that reads it** — always separate by at least one deploy\n- **Never run destructive migrations (DROP TABLE, DELETE) without an explicit human approval step** — not just a code review\n- **Never skip the DOWN migration** — \"we can recreate it\" is not a rollback strategy\n- **Never migrate in peak traffic hours** — schedule for the lowest-traffic window\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FRBraga01\u002Fa-team\u002Fskills\u002Fdata-migration",483,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-13 02:16:32",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill data-migration",{"tool":65,"command":66},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill data-migration",{"tool":68,"command":69},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill data-migration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002Fa-team\u002Fskills\u002Fdata-migration\u002FSKILL.md",true,[],[74,82,89,96,122,146],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":81},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":81},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":81},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":44},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,35,119,120,121],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","when","you","done","reviewer","io","cli","merge","past",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":44},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[129,130,131,118,30,132,133,134,135,136,137,138,139,140,108,141,142,143,144,145],"deja reflect","reflect","review","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":163,"publishedAt":44},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[152,157,160],{"categoryNo":153,"categoryName":154,"taxonomyType":155,"taxonomyTypeDesc":156},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":158,"categoryName":159,"taxonomyType":155,"taxonomyTypeDesc":156},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":161,"categoryName":162,"taxonomyType":155,"taxonomyTypeDesc":156},"01JBSEEDCAT000000000000010","后端与接口",[148,164,165,166,167,168,169,142,170,109,171,172,173,174,114,175,176,177,178,179],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]