linear-multi-env-setup
Configure Linear across development, staging, and production environments. Use when setting up per-environment API keys, secret management, or environment-specific Linear configurations. Trigger: "linear environments", "linear staging", "linear dev prod", "linear environment setup", "multi-environment linear".
Best use case
linear-multi-env-setup is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Configure Linear across development, staging, and production environments. Use when setting up per-environment API keys, secret management, or environment-specific Linear configurations. Trigger: "linear environments", "linear staging", "linear dev prod", "linear environment setup", "multi-environment linear".
Teams using linear-multi-env-setup should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/linear-multi-env-setup/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How linear-multi-env-setup Compares
| Feature / Agent | linear-multi-env-setup | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Configure Linear across development, staging, and production environments. Use when setting up per-environment API keys, secret management, or environment-specific Linear configurations. Trigger: "linear environments", "linear staging", "linear dev prod", "linear environment setup", "multi-environment linear".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# Linear Multi-Environment Setup
## Overview
Configure Linear integrations across dev, staging, and production with isolated API keys, secret management, environment guards, and per-environment webhook routing. Use separate Linear workspaces or at minimum separate API keys per environment.
## Prerequisites
- Separate Linear API keys per environment (dev, staging, prod)
- Secret management (Vault, AWS Secrets Manager, GCP Secret Manager)
- CI/CD pipeline with environment support
- Node.js 18+
## Instructions
### Step 1: Environment Configuration
```typescript
// src/config/linear.ts
import { LinearClient } from "@linear/sdk";
interface LinearEnvConfig {
apiKey: string;
webhookSecret: string;
defaultTeamKey: string;
enableWebhooks: boolean;
enableDebugLogging: boolean;
cacheEnabled: boolean;
}
type Environment = "development" | "staging" | "production" | "test";
function getEnvironment(): Environment {
const env = process.env.NODE_ENV ?? "development";
if (!["development", "staging", "production", "test"].includes(env)) {
throw new Error(`Unknown NODE_ENV: ${env}`);
}
return env as Environment;
}
async function loadConfig(): Promise<LinearEnvConfig> {
const env = getEnvironment();
// In production, use secret manager instead of env vars
if (env === "production" || env === "staging") {
return {
apiKey: await getSecret(`linear-api-key-${env}`),
webhookSecret: await getSecret(`linear-webhook-secret-${env}`),
defaultTeamKey: process.env.LINEAR_DEFAULT_TEAM_KEY ?? "ENG",
enableWebhooks: true,
enableDebugLogging: env === "staging",
cacheEnabled: true,
};
}
// Dev/test: use environment variables
return {
apiKey: process.env.LINEAR_API_KEY ?? "",
webhookSecret: process.env.LINEAR_WEBHOOK_SECRET ?? "",
defaultTeamKey: process.env.LINEAR_DEV_TEAM_KEY ?? "DEV",
enableWebhooks: false, // No webhook server in local dev
enableDebugLogging: true,
cacheEnabled: false,
};
}
```
### Step 2: Secret Manager Integration
```typescript
// GCP Secret Manager
import { SecretManagerServiceClient } from "@google-cloud/secret-manager";
async function getSecret(name: string): Promise<string> {
const client = new SecretManagerServiceClient();
const projectId = process.env.GCP_PROJECT_ID!;
const [version] = await client.accessSecretVersion({
name: `projects/${projectId}/secrets/${name}/versions/latest`,
});
return version.payload?.data?.toString() ?? "";
}
// AWS Secrets Manager
import { SecretsManagerClient, GetSecretValueCommand } from "@aws-sdk/client-secrets-manager";
async function getSecretAWS(name: string): Promise<string> {
const client = new SecretsManagerClient({});
const result = await client.send(new GetSecretValueCommand({ SecretId: name }));
return result.SecretString ?? "";
}
// HashiCorp Vault
async function getSecretVault(path: string): Promise<string> {
const response = await fetch(`${process.env.VAULT_ADDR}/v1/${path}`, {
headers: { "X-Vault-Token": process.env.VAULT_TOKEN! },
});
const data = await response.json();
return data.data.data.value;
}
```
### Step 3: Environment-Aware Client Factory
```typescript
let _client: LinearClient | null = null;
let _config: LinearEnvConfig | null = null;
export async function getLinearClient(): Promise<LinearClient> {
if (!_client) {
_config = await loadConfig();
if (!_config.apiKey) {
throw new Error(`LINEAR_API_KEY not configured for ${getEnvironment()}`);
}
_client = new LinearClient({ apiKey: _config.apiKey });
}
return _client;
}
export async function getConfig(): Promise<LinearEnvConfig> {
if (!_config) await getLinearClient(); // Triggers config load
return _config!;
}
// For tests: inject a mock or test client
export function setTestClient(client: LinearClient) {
_client = client;
}
```
### Step 4: Environment Guards
Prevent dangerous operations from running in the wrong environment.
```typescript
function requireProduction(operation: string) {
if (getEnvironment() !== "production") {
throw new Error(`${operation} is production-only (current: ${getEnvironment()})`);
}
}
function preventProduction(operation: string) {
if (getEnvironment() === "production") {
throw new Error(`${operation} is forbidden in production`);
}
}
// Usage
async function deleteAllTestIssues(teamKey: string) {
preventProduction("deleteAllTestIssues"); // Safety guard
const client = await getLinearClient();
const issues = await client.issues({
filter: {
team: { key: { eq: teamKey } },
title: { startsWith: "[TEST]" },
},
});
for (const issue of issues.nodes) {
await issue.delete();
}
}
// Safe delete: archives in prod, deletes in dev
async function safeRemoveIssue(issueId: string) {
const client = await getLinearClient();
if (getEnvironment() === "production") {
await client.archiveIssue(issueId);
} else {
await client.deleteIssue(issueId);
}
}
```
### Step 5: Per-Environment Webhooks
```typescript
// Different webhook configs per environment
const webhookConfigs: Record<Environment, {
resourceTypes: string[];
enabled: boolean;
}> = {
development: {
resourceTypes: [], // No webhooks in dev — use polling/ngrok manually
enabled: false,
},
staging: {
resourceTypes: ["Issue", "Comment", "Project", "Cycle"],
enabled: true,
},
production: {
resourceTypes: ["Issue", "Comment", "Project", "Cycle", "IssueLabel", "ProjectUpdate"],
enabled: true,
},
test: {
resourceTypes: [],
enabled: false,
},
};
```
### Step 6: CI/CD with Environment Secrets
```yaml
# .github/workflows/deploy.yml
name: Deploy
on:
push:
branches: [main, release/*]
jobs:
deploy-staging:
if: github.ref == 'refs/heads/main'
runs-on: ubuntu-latest
environment: staging
steps:
- uses: actions/checkout@v4
- run: npm ci && npm run build
- run: npm run deploy:staging
env:
LINEAR_API_KEY: ${{ secrets.LINEAR_API_KEY }}
LINEAR_WEBHOOK_SECRET: ${{ secrets.LINEAR_WEBHOOK_SECRET }}
deploy-production:
if: startsWith(github.ref, 'refs/heads/release/')
runs-on: ubuntu-latest
environment: production
steps:
- uses: actions/checkout@v4
- run: npm ci && npm run build
- run: npm run deploy:production
env:
LINEAR_API_KEY: ${{ secrets.LINEAR_API_KEY }}
LINEAR_WEBHOOK_SECRET: ${{ secrets.LINEAR_WEBHOOK_SECRET }}
```
### Step 7: Environment Validation Script
```typescript
// scripts/validate-environment.ts
async function validateEnvironment() {
const env = getEnvironment();
console.log(`Validating Linear config for: ${env}\n`);
const config = await loadConfig();
const checks = [
{ name: "API Key", ok: config.apiKey.startsWith("lin_api_") },
{ name: "Webhook Secret", ok: !config.enableWebhooks || config.webhookSecret.length > 10 },
{ name: "Default Team", ok: config.defaultTeamKey.length > 0 },
];
// Test API connectivity
try {
const client = new LinearClient({ apiKey: config.apiKey });
const viewer = await client.viewer;
const teams = await client.teams();
const team = teams.nodes.find(t => t.key === config.defaultTeamKey);
checks.push({ name: "API Auth", ok: true });
checks.push({ name: "Default Team Exists", ok: !!team });
console.log(` User: ${viewer.name} (${viewer.email})`);
console.log(` Teams: ${teams.nodes.map(t => t.key).join(", ")}`);
} catch (e: any) {
checks.push({ name: "API Auth", ok: false });
console.error(` Auth failed: ${e.message}`);
}
for (const { name, ok } of checks) {
console.log(` ${ok ? "PASS" : "FAIL"}: ${name}`);
}
const failed = checks.filter(c => !c.ok).length;
if (failed > 0) process.exit(1);
}
validateEnvironment();
```
## Error Handling
| Error | Cause | Solution |
|-------|-------|----------|
| Wrong environment data | API key for wrong workspace | Verify secrets per environment |
| Secret not found | Missing in secret manager | Add secret for the target environment |
| Team not found | Wrong `defaultTeamKey` | Check team key matches the environment's workspace |
| Permission denied | Insufficient API key scope | Regenerate with correct scopes |
## Examples
### Quick Validation
```bash
NODE_ENV=staging npx tsx scripts/validate-environment.ts
# Output:
# Validating Linear config for: staging
# User: CI Bot (ci@company.com)
# Teams: ENG, PRODUCT, DESIGN
# PASS: API Key
# PASS: Webhook Secret
# PASS: Default Team
# PASS: API Auth
# PASS: Default Team Exists
```
## Resources
- [Linear API Authentication](https://linear.app/developers/graphql)
- [12-Factor Config](https://12factor.net/config)
- [GCP Secret Manager](https://cloud.google.com/secret-manager)
- [AWS Secrets Manager](https://docs.aws.amazon.com/secretsmanager/)Related Skills
windsurf-multi-env-setup
Configure Windsurf IDE and Cascade AI across team members and project environments. Use when onboarding teams to Windsurf, setting up per-project Cascade configuration, or managing Windsurf settings across development, staging, and production contexts. Trigger with phrases like "windsurf team setup", "windsurf environments", "windsurf multi-project", "windsurf team config", "cascade rules per env".
webflow-multi-env-setup
Configure Webflow across development, staging, and production environments with per-environment API tokens, site IDs, and secret management via Vault/AWS/GCP. Trigger with phrases like "webflow environments", "webflow staging", "webflow dev prod", "webflow environment setup", "webflow config by env".
vercel-multi-env-setup
Configure Vercel across development, preview, and production environments with scoped secrets. Use when setting up per-environment configuration, managing environment-specific variables, or implementing environment isolation on Vercel. Trigger with phrases like "vercel environments", "vercel staging", "vercel dev prod", "vercel environment setup", "vercel env scoping".
veeva-multi-env-setup
Veeva Vault multi env setup for enterprise operations. Use when implementing advanced Veeva Vault patterns. Trigger: "veeva multi env setup".
vastai-multi-env-setup
Configure Vast.ai GPU cloud across dev, staging, and production environments. Use when isolating GPU pools per team, managing API key separation by env, or implementing spending controls per deployment tier. Trigger with phrases like "vastai environments", "vastai staging", "vastai dev prod", "vastai multi-env".
supabase-multi-env-setup
Configure Supabase across development, staging, and production with separate projects, environment-specific secrets, and safe migration promotion. Use when setting up multi-environment deployments, isolating dev from prod data, configuring per-environment Supabase projects, or promoting migrations through environments. Trigger: "supabase environments", "supabase staging", "supabase dev prod", "supabase multi-project", "supabase env config", "database branching".
speak-multi-env-setup
Configure Speak across dev, staging, and production with separate API keys and mock modes. Use when implementing multi env setup, or managing Speak language learning platform operations. Trigger with phrases like "speak multi env setup", "speak multi env setup".
snowflake-multi-env-setup
Configure Snowflake across dev, staging, and production with account-level isolation, zero-copy clones, and environment-specific RBAC. Trigger with phrases like "snowflake environments", "snowflake staging", "snowflake dev prod", "snowflake clone", "snowflake environment setup".
windsurf-workspace-setup
Initialize Windsurf workspace with project-specific AI rules. Activate when users mention "create windsurfrules", "setup workspace", "configure project ai", "initialize windsurf workspace", or "migrate to windsurf". Handles workspace configuration and team standardization. Use when working with windsurf workspace setup functionality. Trigger with phrases like "windsurf workspace setup", "windsurf setup", "windsurf".
windsurf-multi-file-editing
Manage multi-file edits with Cascade coordination. Activate when users mention "multi-file edit", "edit multiple files", "cross-file changes", "refactor across files", or "batch modifications". Handles coordinated multi-file operations. Use when working with windsurf multi file editing functionality. Trigger with phrases like "windsurf multi file editing", "windsurf editing", "windsurf".
shopify-multi-env-setup
Configure Shopify apps across development, staging, and production environments with separate stores, API credentials, and app instances. Trigger with phrases like "shopify environments", "shopify staging", "shopify dev vs prod", "shopify multi-store", "shopify environment setup".
salesforce-multi-env-setup
Configure Salesforce across Developer, Sandbox, and Production environments with proper org management. Use when setting up multi-environment deployments, configuring per-environment credentials, or implementing sandbox-to-production promotion flows. Trigger with phrases like "salesforce environments", "salesforce sandbox", "salesforce dev prod", "salesforce org management", "salesforce sandbox types".