[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H4G1HZ3CBJC4EXFSA357AV":3,"skill-same:01M6H4G1HZ3CBJC4EXFSA357AV":93},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":27,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":6,"ownerHtmlUrl":63,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":64,"install":65,"resources":78},"01M6H4G1HZ3CBJC4EXFSA357AV","migrating-apis",null,"Implement API migrations between versions, platforms, or frameworks with minimal downtime.\nUse when upgrading APIs between versions.\nTrigger with phrases like \"migrate the API\", \"upgrade API version\", or \"migrate to new API\".","micsapp\u002Fmicstec-skills","micsapp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82411001?v=4","01M6GWCFQ6D3PV8EHNY62NN5VW","01M6GWCFVE1PA5HG0DKC7AMFJ3",4,"MIT","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fapi-development\u002Fapi-migration-tool\u002Fskills\u002Fmigrating-apis\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"migrating apis","use","with","trigger","io","upgrade","frameworks","migrations","minimal","version","codex","edit","write","read","grep","migrate","Bash","api","code","implement","2026-11-10 10:12:30",false,"---\nname: migrating-apis\ndescription: |\n  Implement API migrations between versions, platforms, or frameworks with minimal downtime.\n  Use when upgrading APIs between versions.\n  Trigger with phrases like \"migrate the API\", \"upgrade API version\", or \"migrate to new API\".\n  \nallowed-tools: Read, Write, Edit, Grep, Glob, Bash(api:migrate-*)\nversion: 1.0.0\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\nlicense: MIT\ncompatible-with: claude-code, codex, openclaw\n---\n# Migrating APIs\n\n## Overview\n\nImplement API migrations between versions, frameworks, or platforms with minimal downtime using strangler fig pattern, parallel running, and traffic shadowing. Generate migration plans that map old endpoints to new equivalents, transform request\u002Fresponse formats, and validate data consistency between legacy and target implementations.\n\n## Prerequisites\n\n- Source API codebase and OpenAPI specification accessible for analysis\n- Target framework or platform environment provisioned and accessible\n- Traffic routing capability for gradual cutover (reverse proxy, feature flags, or API gateway)\n- Database migration tools if schema changes accompany the API migration (Flyway, Alembic, Prisma Migrate)\n- Integration test suite covering all existing API consumers\n\n## Instructions\n\n1. Inventory all existing endpoints using Grep and Read, documenting HTTP methods, URL patterns, request\u002Fresponse schemas, authentication mechanisms, and consumer dependencies.\n2. Generate an endpoint mapping table that pairs each legacy endpoint with its target equivalent, flagging breaking changes in URL structure, field names, data types, and authentication flow.\n3. Create request\u002Fresponse adapters that transform legacy format to target format, handling field renames, nested-to-flat conversions, and enum value changes.\n4. Implement a traffic router (reverse proxy rules or middleware) that directs requests to either the legacy or target implementation based on migration phase, endpoint, or feature flag.\n5. Set up traffic shadowing to duplicate production requests to the target implementation without serving target responses, comparing outputs for data consistency validation.\n6. Build a migration dashboard tracking per-endpoint migration status (legacy-only, shadow, canary, migrated), error rates, and latency comparison between implementations.\n7. Execute phased cutover: shadow (compare only) -> canary (1% traffic to target) -> gradual ramp (10%, 25%, 50%, 100%) -> legacy decommission, with automatic rollback triggers.\n8. Validate migration completeness by running the full integration test suite against the target implementation and comparing response bodies with legacy for a representative request sample.\n\nSee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md` for the full implementation guide.\n\n## Output\n\n- `${CLAUDE_SKILL_DIR}\u002Fmigration\u002Fendpoint-mapping.json` - Legacy-to-target endpoint mapping with change annotations\n- `${CLAUDE_SKILL_DIR}\u002Fmigration\u002Fadapters\u002F` - Request\u002Fresponse transformation functions per endpoint\n- `${CLAUDE_SKILL_DIR}\u002Fmigration\u002Frouter.js` - Traffic routing middleware with phase-based switching\n- `${CLAUDE_SKILL_DIR}\u002Fmigration\u002Fshadow-compare.js` - Traffic shadow comparison and diff reporting\n- `${CLAUDE_SKILL_DIR}\u002Fmigration\u002Fdashboard.md` - Migration progress tracking per endpoint\n- `${CLAUDE_SKILL_DIR}\u002Ftests\u002Fmigration\u002F` - Parity tests comparing legacy and target responses\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| Response mismatch in shadow | Target returns different data than legacy for same request | Log diff details; classify as expected (intentional change) or bug; fix before canary phase |\n| Adapter transformation failure | Legacy request contains edge-case field values not handled by adapter | Add fallback handling; log unmatched fields; expand adapter test coverage |\n| Rollback triggered | Canary error rate exceeds threshold (e.g., >2% 5xx) | Automatically route traffic back to legacy; alert migration team; analyze failures |\n| Consumer authentication break | Target uses different auth scheme than legacy | Run auth adapter translating legacy tokens to target format during transition |\n| Data inconsistency | Database schema migration introduced transformation errors | Run data validation queries comparing legacy and target data stores; fix transformation logic |\n\nRefer to `${CLAUDE_SKILL_DIR}\u002Freferences\u002Ferrors.md` for comprehensive error patterns.\n\n## Examples\n\n**Express to FastAPI migration**: Migrate a Node.js Express API to Python FastAPI, using nginx as the traffic router, shadowing production traffic for 1 week, then canary-releasing endpoint by endpoint over 4 weeks.\n\n**REST to GraphQL migration**: Implement GraphQL resolvers that call the existing REST endpoints internally, gradually replacing REST data fetching with direct database access while maintaining the REST surface via a thin GraphQL-to-REST adapter.\n\n**Monolith to microservices**: Extract a user management module from a monolithic API into a standalone service, using the strangler fig pattern with API gateway routing to direct `\u002Fusers\u002F*` traffic to the new service while other endpoints remain on the monolith.\n\nSee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fexamples.md` for additional examples.\n\n## Resources\n\n- Strangler Fig Application pattern: Martin Fowler\n- Feature flag services: LaunchDarkly, Unleash, Flagsmith\n- Traffic shadowing with Envoy proxy or Istio service mesh\n- Blue-green and canary deployment strategies","# Migrating APIs\n\n## Overview\n\nImplement API migrations between versions, frameworks, or platforms with minimal downtime using strangler fig pattern, parallel running, and traffic shadowing. Generate migration plans that map old endpoints to new equivalents, transform request\u002Fresponse formats, and validate data consistency between legacy and target implementations.\n\n## Prerequisites\n\n- Source API codebase and OpenAPI specification accessible for analysis\n- Target framework or platform environment provisioned and accessible\n- Traffic routing capability for gradual cutover (reverse proxy, feature flags, or API gateway)\n- Database migration tools if schema changes accompany the API migration (Flyway, Alembic, Prisma Migrate)\n- Integration test suite covering all existing API consumers\n\n## Instructions\n\n1. Inventory all existing endpoints using Grep and Read, documenting HTTP methods, URL patterns, request\u002Fresponse schemas, authentication mechanisms, and consumer dependencies.\n2. Generate an endpoint mapping table that pairs each legacy endpoint with its target equivalent, flagging breaking changes in URL structure, field names, data types, and authentication flow.\n3. Create request\u002Fresponse adapters that transform legacy format to target format, handling field renames, nested-to-flat conversions, and enum value changes.\n4. Implement a traffic router (reverse proxy rules or middleware) that directs requests to either the legacy or target implementation based on migration phase, endpoint, or feature flag.\n5. Set up traffic shadowing to duplicate production requests to the target implementation without serving target responses, comparing outputs for data consistency validation.\n6. Build a migration dashboard tracking per-endpoint migration status (legacy-only, shadow, canary, migrated), error rates, and latency comparison between implementations.\n7. Execute phased cutover: shadow (compare only) -> canary (1% traffic to target) -> gradual ramp (10%, 25%, 50%, 100%) -> legacy decommission, with automatic rollback triggers.\n8. Validate migration completeness by running the full integration test suite against the target implementation and comparing response bodies with legacy for a representative request sample.\n\nSee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md` for the full implementation guide.\n\n## Output\n\n- `${CLAUDE_SKILL_DIR}\u002Fmigration\u002Fendpoint-mapping.json` - Legacy-to-target endpoint mapping with change annotations\n- `${CLAUDE_SKILL_DIR}\u002Fmigration\u002Fadapters\u002F` - Request\u002Fresponse transformation functions per endpoint\n- `${CLAUDE_SKILL_DIR}\u002Fmigration\u002Frouter.js` - Traffic routing middleware with phase-based switching\n- `${CLAUDE_SKILL_DIR}\u002Fmigration\u002Fshadow-compare.js` - Traffic shadow comparison and diff reporting\n- `${CLAUDE_SKILL_DIR}\u002Fmigration\u002Fdashboard.md` - Migration progress tracking per endpoint\n- `${CLAUDE_SKILL_DIR}\u002Ftests\u002Fmigration\u002F` - Parity tests comparing legacy and target responses\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| Response mismatch in shadow | Target returns different data than legacy for same request | Log diff details; classify as expected (intentional change) or bug; fix before canary phase |\n| Adapter transformation failure | Legacy request contains edge-case field values not handled by adapter | Add fallback handling; log unmatched fields; expand adapter test coverage |\n| Rollback triggered | Canary error rate exceeds threshold (e.g., >2% 5xx) | Automatically route traffic back to legacy; alert migration team; analyze failures |\n| Consumer authentication break | Target uses different auth scheme than legacy | Run auth adapter translating legacy tokens to target format during transition |\n| Data inconsistency | Database schema migration introduced transformation errors | Run data validation queries comparing legacy and target data stores; fix transformation logic |\n\nRefer to `${CLAUDE_SKILL_DIR}\u002Freferences\u002Ferrors.md` for comprehensive error patterns.\n\n## Examples\n\n**Express to FastAPI migration**: Migrate a Node.js Express API to Python FastAPI, using nginx as the traffic router, shadowing production traffic for 1 week, then canary-releasing endpoint by endpoint over 4 weeks.\n\n**REST to GraphQL migration**: Implement GraphQL resolvers that call the existing REST endpoints internally, gradually replacing REST data fetching with direct database access while maintaining the REST surface via a thin GraphQL-to-REST adapter.\n\n**Monolith to microservices**: Extract a user management module from a monolithic API into a standalone service, using the strangler fig pattern with API gateway routing to direct `\u002Fusers\u002F*` traffic to the new service while other endpoints remain on the monolith.\n\nSee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fexamples.md` for additional examples.\n\n## Resources\n\n- Strangler Fig Application pattern: Martin Fowler\n- Feature flag services: LaunchDarkly, Unleash, Flagsmith\n- Traffic shadowing with Envoy proxy or Istio service mesh\n- Blue-green and canary deployment strategies",{"name":5,"author":53,"license":14,"version":54,"description":55,"allowed-tools":56,"compatible-with":57},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Implement API migrations between versions, platforms, or frameworks with minimal downtime.\nUse when upgrading APIs between versions.\nTrigger with phrases like \"migrate the API\", \"upgrade API version\", or \"migrate to new API\".\n","Read, Write, Edit, Grep, Glob, Bash(api:migrate-*)","claude-code, codex, openclaw","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","claude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fapi-development\u002Fapi-migration-tool\u002Fskills\u002Fmigrating-apis",0,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills","https:\u002F\u002Fgithub.com\u002Fmicsapp","2026-03-20 11:24:18",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add micsapp\u002Fmicstec-skills --skill migrating-apis",{"tool":71,"command":72},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill migrating-apis",{"tool":74,"command":75},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill migrating-apis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fapi-development\u002Fapi-migration-tool\u002Fskills\u002Fmigrating-apis\u002FSKILL.md",true,[79,85,89],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Ferrors.md","REFERENCE","参考文档",901,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fapi-development\u002Fapi-migration-tool\u002Fskills\u002Fmigrating-apis\u002Freferences\u002Ferrors.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fexamples.md",4664,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fapi-development\u002Fapi-migration-tool\u002Fskills\u002Fmigrating-apis\u002Freferences\u002Fexamples.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fimplementation.md",1405,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fapi-development\u002Fapi-migration-tool\u002Fskills\u002Fmigrating-apis\u002Freferences\u002Fimplementation.md",[94,122,151,171,191,215],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":102,"publishedAt":48},"01M6HBTJ02FXBFG9NYEHHYAP52","azure-apim-architecture","Analyzes and explains Azure API Management architecture decisions for enterprise API marketplace implementations using VNet Internal mode, Front Door, hybrid authentication, and multi-environment strategies. Use when discussing APIM component selection, network topology, cost optimization, or comparing alternatives like workspaces vs instances, VNet Internal vs External mode, or Front Door vs Application Gateway.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fazure-apim-architecture\u002FSKILL.md",[100,101],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},[103,104,105,106,107,108,109,110,111,45,112,113,114,115,116,117,118,119,120,121],"architecture","azure","azure apim architecture","component","authentication","gateway","topology","Optimization","network","team","environment","multi-environment","workspaces","instances","selection","strategies","azure api management","mode","for",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":136,"publishedAt":48},"01M6HBT7J4H082JEEA670B3EQ9","apiops-deployment","Guides deployment of Azure API Management infrastructure using Infrastructure as Code (Bicep\u002FTerraform), CI\u002FCD pipelines (GitHub Actions\u002FAzure DevOps), and APIOps workflows. Use when deploying APIM, creating pipelines, or implementing dev→test→prod promotion strategies.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapiops-deployment\u002FSKILL.md",[128,129,132,135],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":130,"categoryName":131,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":133,"categoryName":134,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},[137,138,139,140,104,141,46,142,143,144,145,146,45,112,118,147,148,119,149,150],"deployment","apiops deployment","workflows","azure devops","infrastructure","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD","implementing",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":158,"publishedAt":48},"01M6HBT2HEA23THNE9E00GYQBE","apim-policy-authoring","Creates production-ready Azure API Management policy XML for authentication (OAuth 2.0, JWT validation, subscription keys), rate limiting, CORS configuration, error handling, and API transformations. Use when implementing API security, access control, or request\u002Fresponse processing logic.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapim-policy-authoring\u002FSKILL.md",[157],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[159,160,161,162,104,107,45,112,163,29,164,165,166,167,168,119,169,170,150,121],"policy","authoring","apim policy authoring","security","access","ready","api security","Access Control","error","processing","cors configuration","production-ready",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":179,"publishedAt":48},"01M6HBSY65SB29J9WE9KYD0K6T","api-security-review","Reviews Azure API Management configurations for security vulnerabilities, OWASP API Security Top 10 compliance, VNet Internal mode validation, Private Link verification, and Azure Security Benchmark alignment. Use when performing security audits, pre-deployment validation, or compliance reviews.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapi-security-review\u002FSKILL.md",[177,178],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},[180,162,181,45,165,182,104,137,183,184,185,186,112,187,119,188,189,190,120,121],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":197,"publishedAt":48},"01M6HBSRW4PDFE6K4F8JYPZQ05","jira-cli","Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fjira-cli\u002FSKILL.md",[],[198,199,200,139,201,202,203,204,45,205,206,207,39,208,209,210,211,212,213,214],"cli","jira","jira cli","init","tasks","create","issues","common","work","command","list","view","project","project work","token","line","sprints",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":221,"publishedAt":48},"01M6HBSNS3JHMW603G47TWE31H","calculator","Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fcalculator\u002FSKILL.md",[],[217,222,223,224,225,226,227,29,228,229],"npm","js","calculate","node","math","user","compute","errors"]