Write a migration guide between two SDK major versions by diffing exported symbols and reshaping common call patterns.
Diffs two SDK major versions, identifies removed/renamed/added exports, and writes a migration guide structured as: Highlights, Per-Symbol Changes, Common Call-Pattern Rewrites, and Rollout Strategy.
sdk_name: package name (npm, PyPI, or Maven coords).from_version: previous major (e.g., 5.x).to_version: new major (e.g., 6.x).repo_dir: optional consumer repo path, used to ground the call-pattern rewrites in real call sites.npm pack <sdk_name>@<from_version> and npm pack <sdk_name>@<to_version>. Extract to /tmp/sdk-old/ and /tmp/sdk-new/.api-extractor run --config api-extractor.json against the .d.ts; Python via pydoc -w <package>.<repo_dir> for call sites using rg -nN '<symbol>\b'. Record file:line counts.Old | New | Type | Note.migration-<sdk-name>-<from>-to-<to>.md.A single markdown migration guide with the four named sections plus a summary header (counts of removed/renamed/added). Includes runnable codemod commands when applicable (npx jscodeshift -t <transform> src/).
Re-run the API diff after the guide is written and verify the reported counts match the guide. For each "before" code block, grep the consumer repo to confirm at least one real call site with that pattern; remove patterns that are purely synthetic. If the diff shows zero removed exports, downgrade the doc to a Release Notes brief — a migration guide for an additive-only release is overkill.
Object.keys(require(<pkg>))); guide is approximate, mark accordingly.to_version (e.g., 6.0.0-beta.1): warn at the top of the guide that the API may shift before GA.Other publishers' experience with this skill. Self-rating is blocked.
Ratings are limited to publishers while the registry is small — sign in and publish a public skill to rate.
No ratings yet. Be the first.
Same domains or capabilities as amitte/sdk-migration-guide-writer.
Turn a discussion log plus a decision into an Architecture Decision Record with Context, Decision, Consequences, and Alternatives Considered.
Diff two OpenAPI YAML files and produce a backwards-compatibility changelog grouped into breaking, non-breaking, and additive changes.
Group a list of commit subjects into Keep-a-Changelog sections (Added, Changed, Fixed, Removed) using Conventional Commits prefixes and content heuristics.
Build a one-page cheatsheet for a CLI tool's 80% case by parsing the output of tool --help and grouping flags by intent.
Document every env var declared in .env.example and config files, cross-referenced to the code locations that read each one.
Audit a CORS configuration for over-permissive Origin, Methods, and Headers and propose a tightened policy keyed to actual cross-origin call patterns.