[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74GH50PM8Q3SA1915MM0ST4":3,"skill-same:01M74GH50PM8Q3SA1915MM0ST4":44},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M74GH50PM8Q3SA1915MM0ST4","migration-guide",null,"Write a consumer migration guide for a breaking change — before\u002Fafter examples, ordered steps, gotchas, rollback. Consumer upgrade steps, not the deprecation timeline (deprecation-plan).","MohammadBafkar\u002Fpolymath","MohammadBafkar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F34940462?v=4","01M74G540TQFZWK6KVAPKFVGNR","Mohammad Bafkar","01M74G541HG19QP9V5DQCJVKYE",0,"MIT","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-release\u002Fskills\u002Fmigration-guide\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: migration-guide\ndescription: Write a consumer migration guide for a breaking change — before\u002Fafter examples, ordered steps, gotchas, rollback. Consumer upgrade steps, not the deprecation timeline (deprecation-plan).\n---\n\n# migration-guide\n\n> A migration guide earns its keep when a consumer can follow it start to finish without asking a question. Show the diff, not the philosophy.\n\n**Mode:** analytical — judgment inside a fixed frame. Keep the output shape; every verdict cites its evidence; unknowns are marked `[TBD]` or `[VERIFY]`, never filled in.\n\n## When to use\n\n- You're deprecating or breaking something and consumers need concrete steps to move off it.\n- The user asks for an upgrade\u002Fmigration guide for an API\u002Flibrary\u002Fconfig change.\n- A workflow invokes `polymath-release:migration-guide`.\n\nThis writes the *consumer upgrade steps*. It is not the deprecation timeline\u002Fpolicy (`polymath-release:deprecation-plan`), the customer-facing sunset notice (`polymath-communication:write-sunset-notice`), or a runtime\u002Fversion migration of your own codebase (the `migrateLanguageVersion` workflow).\n\n## Inputs\n\n- The old and new way (API shape, config keys, behavior).\n- Who is migrating (audience skill level) and the most common usage patterns. Unknown patterns: derive them from the old API's call sites or docs, and mark any guessed pattern `[VERIFY]`.\n- Every before\u002Fafter example must be checked against the real old and new APIs (read the code or docs); an example you could not verify is marked `[VERIFY: untested]`.\n\n## Procedure\n\n1. **State the change in one line** and whether it's mechanical or requires judgment.\n2. **Before \u002F after** — for each common pattern, show the old code and the new code side by side. Lead with the 80% case.\n3. **Step order** — numbered, smallest safe steps; note which steps are reversible and where a checkpoint is safe.\n4. **Gotchas** — behavioral differences, defaults that changed, things that look equivalent but aren't.\n5. **Verify** — how the consumer confirms the migration worked (a test, an output, a log line).\n6. **Rollback** — how to revert if something breaks mid-migration.\n7. **Codemod** — if the change is mechanical at scale, provide or point to an automated codemod.\n8. **Slug** from the change (e.g. `v1-search-to-v2`): a workflow's `${workflow.slug}` wins; otherwise lowercase it, replace each run of characters outside `a-z0-9` with `-`, trim `-` at the ends, and cut to ≤ 60 characters at a `-`. An existing file at the target path is updated in place (show the diff), never duplicated.\n9. Write `docs\u002Fmigrations\u002F\u003Cslug>-guide.md`.\n\n## Output\n\n`docs\u002Fmigrations\u002F\u003Cslug>-guide.md`, in this shape:\n\n````markdown\n# Migrating from \u002Fv1\u002Fsearch to \u002Fv2\u002Fsearch\n\n**Change:** results are paginated with a cursor instead of `page=` — mechanical for most callers.\n\n## Before \u002F after (most common first)\n\n```diff\n- GET \u002Fv1\u002Fsearch?q=refund&page=2\n+ GET \u002Fv2\u002Fsearch?q=refund&cursor=\u003Cnext_cursor from the previous response>\n```\n\n## Steps\n1. Upgrade the SDK to ≥ 4.8 (reversible: pin back to 4.7).\n2. Replace `page` loops with `next_cursor` loops — checkpoint: tests pass on 4.8.\n3. Remove the v1 client config (irreversible once deployed; do it last).\n\n## Gotchas\n- `total_count` is no longer returned; it is expensive at scale — use `has_more`.\n\n## Verify\nRun `sdk-doctor search` — it prints `v2 OK`.\n\n## Rollback\nSteps 1–2 revert by pinning the SDK to 4.7; step 3 needs the v1 config restored before 2027-02-01.\n````\n\n## Quality bar\n\n- Every common usage pattern has a concrete before\u002Fafter, not prose.\n- Steps are ordered and each is independently verifiable; the happy path is followable without external help.\n- Behavioral gotchas (not just API renames) are called out.\n- A rollback is given for any step that isn't trivially reversible.\n","# migration-guide\n\n> A migration guide earns its keep when a consumer can follow it start to finish without asking a question. Show the diff, not the philosophy.\n\n**Mode:** analytical — judgment inside a fixed frame. Keep the output shape; every verdict cites its evidence; unknowns are marked `[TBD]` or `[VERIFY]`, never filled in.\n\n## When to use\n\n- You're deprecating or breaking something and consumers need concrete steps to move off it.\n- The user asks for an upgrade\u002Fmigration guide for an API\u002Flibrary\u002Fconfig change.\n- A workflow invokes `polymath-release:migration-guide`.\n\nThis writes the *consumer upgrade steps*. It is not the deprecation timeline\u002Fpolicy (`polymath-release:deprecation-plan`), the customer-facing sunset notice (`polymath-communication:write-sunset-notice`), or a runtime\u002Fversion migration of your own codebase (the `migrateLanguageVersion` workflow).\n\n## Inputs\n\n- The old and new way (API shape, config keys, behavior).\n- Who is migrating (audience skill level) and the most common usage patterns. Unknown patterns: derive them from the old API's call sites or docs, and mark any guessed pattern `[VERIFY]`.\n- Every before\u002Fafter example must be checked against the real old and new APIs (read the code or docs); an example you could not verify is marked `[VERIFY: untested]`.\n\n## Procedure\n\n1. **State the change in one line** and whether it's mechanical or requires judgment.\n2. **Before \u002F after** — for each common pattern, show the old code and the new code side by side. Lead with the 80% case.\n3. **Step order** — numbered, smallest safe steps; note which steps are reversible and where a checkpoint is safe.\n4. **Gotchas** — behavioral differences, defaults that changed, things that look equivalent but aren't.\n5. **Verify** — how the consumer confirms the migration worked (a test, an output, a log line).\n6. **Rollback** — how to revert if something breaks mid-migration.\n7. **Codemod** — if the change is mechanical at scale, provide or point to an automated codemod.\n8. **Slug** from the change (e.g. `v1-search-to-v2`): a workflow's `${workflow.slug}` wins; otherwise lowercase it, replace each run of characters outside `a-z0-9` with `-`, trim `-` at the ends, and cut to ≤ 60 characters at a `-`. An existing file at the target path is updated in place (show the diff), never duplicated.\n9. Write `docs\u002Fmigrations\u002F\u003Cslug>-guide.md`.\n\n## Output\n\n`docs\u002Fmigrations\u002F\u003Cslug>-guide.md`, in this shape:\n\n````markdown\n# Migrating from \u002Fv1\u002Fsearch to \u002Fv2\u002Fsearch\n\n**Change:** results are paginated with a cursor instead of `page=` — mechanical for most callers.\n\n## Before \u002F after (most common first)\n\n```diff\n- GET \u002Fv1\u002Fsearch?q=refund&page=2\n+ GET \u002Fv2\u002Fsearch?q=refund&cursor=\u003Cnext_cursor from the previous response>\n```\n\n## Steps\n1. Upgrade the SDK to ≥ 4.8 (reversible: pin back to 4.7).\n2. Replace `page` loops with `next_cursor` loops — checkpoint: tests pass on 4.8.\n3. Remove the v1 client config (irreversible once deployed; do it last).\n\n## Gotchas\n- `total_count` is no longer returned; it is expensive at scale — use `has_more`.\n\n## Verify\nRun `sdk-doctor search` — it prints `v2 OK`.\n\n## Rollback\nSteps 1–2 revert by pinning the SDK to 4.7; step 3 needs the v1 config restored before 2027-02-01.\n````\n\n## Quality bar\n\n- Every common usage pattern has a concrete before\u002Fafter, not prose.\n- Steps are ordered and each is independently verifiable; the happy path is followable without external help.\n- Behavioral gotchas (not just API renames) are called out.\n- A rollback is given for any step that isn't trivially reversible.\n",{"name":5,"description":7},"main","23f6e21841a39580c9da2b5ec941f39dda17cd86","plugins\u002Fpolymath-release\u002Fskills\u002Fmigration-guide","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath","https:\u002F\u002Fgithub.com\u002FMohammadBafkar","2026-10-29 18:34:59",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add MohammadBafkar\u002Fpolymath --skill migration-guide",{"tool":36,"command":37},"bunx","bunx skills add MohammadBafkar\u002Fpolymath --skill migration-guide",{"tool":39,"command":40},"pnpm","pnpm dlx skills add MohammadBafkar\u002Fpolymath --skill migration-guide","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-release\u002Fskills\u002Fmigration-guide\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M74GN87EBRHM9N87M7AP1HDD","runbook","Write or refresh an operational runbook for an alert\u002Fsymptom; structured as TL;DR + Pre-checks + Steps + Verification + Rollback + Escalation.","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Frunbook\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M74GN5GPKEC1JEKP2DFQNEQJ","rfc","Draft a lightweight design RFC to docs\u002Frfcs\u002F\u003Cslug>.md; Summary, Motivation, Detailed design, Drawbacks, Alternatives, Unresolved questions. A proposal to debate, not a recorded decision (adr).","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Frfc\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M74GN2F4CWPMV4X09TG4E304","editorial-pass","Review and tighten prose in a Markdown artifact for a target tone (terse, formal, friendly) without dropping information; preserve quotations and load-bearing constraints.","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Feditorial-pass\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M74GMZWGYMZ37C4DYGT6P23G","architecture-review-facilitation","Run an architecture review as a process — entry criteria, reviewer checklist, decision log, and follow-up actions — pairing the design artifact with a red-team pass.","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Farchitecture-review-facilitation\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M74GMXVX0YX3ETDXS527XDGM","architecture-doc","Write a C4-style architecture document; System Context + Containers (+ Components when interesting) with mermaid diagrams. Describes structure, not a decision (adr) or proposal (rfc).","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Farchitecture-doc\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M74GMVG1WSMCK066S3KE6V5K","adr","Write an Architecture Decision Record (Michael Nygard format) to docs\u002Fadrs\u002FNNNN-\u003Cslug>.md; frontmatter validated by the ADR artifact schema. Records a made decision, not a proposal to debate (rfc).","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Fadr\u002FSKILL.md",[],[]]