Skip to main content
skill CX Codex

linear-prod-checklist — Claude Code skill: Linear in production

linear-prod-checklist audits a Linear integration before launch, covering access, data, quotas, webhooks, recovery, and ownership.

MIT 1 installs ★ 2,935 updated 2026-10-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add jeremylongshore/tons-of-skills-marketplace --skill linear-prod-checklist -a claude-code
Open on GitHub

What linear-prod-checklist does

This skill reviews a Linear integration before launch, a material permission change, or a production migration. It identifies the repository, commit, environment, workspace and team scope, data classes, owner, and rollback authority, then produces a go, conditional-go, or no-go decision backed by collected evidence.

The review covers OAuth and token type, scopes, secret storage, rotation, revocation, SDK compatibility, request limits, pagination, and error paths. For webhooks, it checks public HTTPS, raw-body signature validation, a response within five seconds, deduplication, and missed-event reconciliation. A webhook receiver without public HTTPS fails this gate.

The skill works with Read, Glob, Grep, WebFetch, Write, and Edit; writes are limited to requested changes with known target files. Live checks need network access and an approved Linear workspace credential. Credential, access, webhook, and data mutations require explicit owner approval.

What it helps with

  • assess a Linear integration before production launch
  • inspect OAuth scopes, token handling, and secret rotation
  • test webhook signatures, duplicates, and missed-event recovery
  • record blockers, approvers, ownership, and rollback authority

Example prompts for the agent

  • Review Linear readiness for the production environment.
  • Run linear-prod-checklist against <repository-path> and <environment>.
  • Assess this Linear integration before migration, including quotas, webhooks, and rollback paths.

How to install linear-prod-checklist

1Skills CLI (Vercel)

npx skills add jeremylongshore/tons-of-skills-marketplace --skill linear-prod-checklist -a claude-code

2Manually: put the files in place

~/.claude/skills/linear-prod-checklist/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/linear-prod-checklist/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about linear-prod-checklist

How do I install linear-prod-checklist in Claude Code?

Run npx skills add jeremylongshore/tons-of-skills-marketplace --skill linear-prod-checklist -a claude-code, then check ~/.claude/skills/linear-prod-checklist/SKILL.md.

What does linear-prod-checklist do?

It audits a Linear integration across authentication, data handling, quotas, webhooks, recovery, and ownership. The result is a go, conditional-go, or no-go decision with supporting evidence.

What is needed for a live Linear verification?

The check needs network access and an approved Linear workspace credential. Actions involving credentials, permissions, webhooks, or workspace data still require approval from the accountable owner.

Source text

SKILL.md · MIT
---
name: linear-prod-checklist
description: >-
  Analyze a Linear integration for production across auth, data, quotas, webhooks, recovery, and ownership. Use when preparing a launch, material permission change, or production migration. Trigger with "review Linear readiness", "launch Linear integration", or "Linear production checklist".
argument-hint: "[repository-path] [environment]"
allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit
version: 1.13.0
author: Jeremy Longshore <[email protected]>
license: MIT
tags:
- saas
- linear
- production-readiness
model: inherit
effort: high
compatibility: Designed for Claude Code; live verification requires network access and an approved Linear workspace credential
---
# Linear Production Readiness Gate

## Overview

Produce an evidence-backed go, conditional-go, or no-go decision instead of a box-checking document detached from the deployed system.

## 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

- OAuth is recommended for apps used by others, and app/team authorization, refresh behavior, and secret rotation must be tested.
- Webhook receivers require public HTTPS, raw-body signature verification, a 200 response within five seconds, deduplication, and reconciliation.
- Request and complexity limits vary by auth mode and can include lower endpoint-specific windows.

## 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: <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.

## Instructions

1. Identify the exact artifact, commit, environment, workspace/team scope, data classes, owner, and rollback authority.
2. Verify SDK/runtime compatibility, token type, exact scopes, secret storage, rotation, revocation, and access review.
3. Run offline tests plus approved read-only auth, error, rate-header, pagination, and webhook-signature probes.
4. Review data minimization, export/retention, observability redaction, idempotency, queue behavior, and missed-event reconciliation.
5. Exercise dependency outage, token failure, throttling, duplicate webhook, rollback, and disablement paths.
6. Record blockers, evidence, accountable approvers, decision, expiry, and post-launch checks.

## Approval Boundaries

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.

## Output

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.

## Error Handling

| 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. |

## Examples

Use a compact handoff that makes scope, mutation authority, and verification evidence reviewable.

Input:

```text
artifact=commit-sha; env=production; scope=two-teams; rollback=tested
```

Expected handoff:

```text
decision=conditional-go; blockers=listed; approvers=required
```

## Resources

- [Skill-specific official documentation](references/official-docs.md)
- [Linear developer documentation index](https://linear.app/llms.txt)
- [Linear GraphQL API](https://linear.app/developers/graphql.md)

© Jeremy Longshore · MIT · jeremylongshore/tons-of-skills-marketplace

Similar skills

All skills for Security →

From the same set139

The whole set →
granola-core-workflow-a granola-core-workflow-a configures meeting templates, chat recipes, and pre-call context inside Granola. Helps structure agendas and summaries for standups and customer calls. CX Codex +1 1installs monitoring-cross-chain-bridges monitoring-cross-chain-bridges tracks bridge TVL, volume, fees, and transfer status across networks. Use it to compare routes or inspect a cross-chain transaction. CX Codex +1 1installs vercel-cost-tuning vercel-cost-tuning reads Vercel billing and finds where money leaks: function time, bandwidth, middleware calls. Use it before the next invoice. CX Codex +1 1installs linear-cost-tuning linear-cost-tuning analyzes Linear API consumption, trims GraphQL query complexity, and shifts redundant polling loops to push webhooks. CX Codex +1 1installs linear-observability linear-observability collects metrics and alerts around a Linear integration: API calls, webhooks, queue, reconciliation. Tokens and issue text stay out of telemetry. CX Codex +1 1installs supabase-webhooks-events supabase-webhooks-events guides the setup of Supabase database webhooks, pg_net HTTP triggers, LISTEN/NOTIFY, and Edge Function handlers with HMAC signature verification. CX Codex +1 1installs supabase-cost-tuning The supabase-cost-tuning skill audits Supabase spending and points to waste in the database, storage, connections, and Edge Functions. CX Codex +1 1installs sql-query-optimizer Walks through SQL query optimization and writes the code for you. It turns on by itself when your prompt mentions sql query optimizer, sql optimizer, or just sql. CX Codex +1 1installs

Project sponsors

Companies that keep this analytics open