Agent skill · software engineering · jeremylongshore
linear-deploy-integration
Connect deployment evidence to Linear work without granting the deploy pipeline broad issue-edit authority. Use when linking releases, commits, pull requests, or rollback receipts to Linear issues. Trigger with "link deploys to Linear", "record Linear release evidence", or "update Linear after deployment".
Why this skill is useful
Adds executable scripts for deployment tracking and integration with Linear that are not available in public documentation.
What it needs
Requires aws, gcloud, vercel installed locally. Requires linear account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Linear Deployment Evidence Integration Overview Design deployment-to-work traceability around stable issue identifiers and owner-approved state changes, while preferring native source-control integration where it satisfies the requirement. 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 Linear's GraphQL API is the explicit mutation surface; branch names and commit text are conventions, not proof that a deployment occurred. OAuth or app-actor access should be scoped to the teams and operations the deployment reporter actually needs. Every mutation result must be checked for GraphQL errors and reconciled by issue ID. 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. Inspect deployment receipts, Linear's source-control integration, identifier conventions, and current issue-transition policy. 2. Choose the native integration, a read-only evidence link, or a custom mutation path based on the actual gap. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/linear-deploy-integration