Agent skill · software engineering · jeremylongshore
linear-upgrade-migration
Upgrade a Linear integration across SDK releases and GraphQL deprecations with typed inventory, staged verification, and rollback. Use when package updates or schema notices require code changes. Trigger with "upgrade Linear SDK", "migrate Linear API code", or "fix Linear deprecation".
Why this skill is useful
Adds executable scripts and a compatibility layer for handling breaking changes during Linear SDK upgrades, which the AI wouldn't reliably generate on its own.
What it needs
Requires jq, npm installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Linear SDK and Schema Upgrade Overview Derive the migration from the installed/current SDK diff and live schema instead of assuming every version change repeats the historical 1.x-to-2.x rename. Prerequisites The target repository, Linear workspace, environment, and accountable owner Current security, privacy, compliance, capacity, and change-control requirements An approved Linear credential only when a bounded live verification is necessary Tool Discipline Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current first-party Linear documentation and package metadata. Use Write or Edit only for requested implementation with known target files. Never write credentials, customer content, unrestricted environment output, or unredacted GraphQL variables. Current Contract The historical SDK 2.x migration changed mutations from model-first to verb-first names; modern upgrades must use actual release and type changes. Linear GraphQL has no conventional versioned API; deprecated fields use @deprecated, and API changes appear in the changelog with an [API] prefix. On 2026-09-11 npm reported @linear/sdk 95.0.0 requiring Node.js >=18.x; recheck before each upgrade. Authentication Use a personal API key only for owner-controlled scripts, OAuth with PKCE for user-delegated applications, or an enabled client-credentials grant for approved automation. Personal keys use Authorization: <APIKEY>; OAuth tokens use Authorization: Bearer <ACCESSTOKEN>. Store credentials server-side in an approved secret manager. Treat app approval, team access, scope changes, credential creation, rotation, revocation, and production access as owner-approved actions. Instructions 1. Record current Node, SDK, lockfile, generated types, GraphQL operations, custom raw queries, and deprecated-field usage. 2. Read the target package metadata, repository changes, generated schema/type diff, and applicable Linear API changelog entries. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/linear-upgrade-migration--d3ef2c