Smithery is now a part of Arcade.dev! Read more in our announcement here
Production readiness checklist for Linear integrations. Use when preparing to deploy a Linear integration to production, reviewing production requirements, or auditing existing deployments. Trigger...
Produce an evidence-backed go, conditional-go, or no-go decision instead of a box-checking document detached from the deployed system.
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.
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: <API_KEY>; OAuth tokens use Authorization: Bearer <ACCESS_TOKEN>. 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.
Do not create, reveal, rotate, or revoke credentials; authorize an OAuth app; change scopes or team access; create, mutate, archive, or delete workspace data; configure or re-enable webhooks; import or export data; change roles, SCIM, or audit streaming; transmit diagnostics; change paid entitlements; or perform another production mutation without explicit approval from the accountable owner. Keep diagnosis read-only unless implementation was requested.
Return the workspace and team scope, auth mode without credential value, files and contracts inspected, exact operation names, evidence collected, validation result, sensitive fields redacted, remaining risk, accountable owner, approval state, and rollback or next action.
| Condition | Response |
|---|---|
| Evidence missing | Mark the gate incomplete; do not infer readiness from configuration. |
| Rollback untested | Return no-go for a material mutation path. |
| Shared quota unowned | Assign a workspace budget owner before launch. |
| Sensitive logs | Block launch until redaction and retained-data cleanup are verified. |
Use a compact handoff that makes scope, mutation authority, and verification evidence reviewable.
Input:
artifact=commit-sha; env=production; scope=two-teams; rollback=tested
Expected handoff:
decision=conditional-go; blockers=listed; approvers=required
