Skip to main content 首页 创作者 jeremylongshore tons-of-skills-marketplace linear-multi-env-setup
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".
跳到安装 Skills Marketplace 发现并探索由社区构建的 Agent Skills
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace --skill linear-multi-env-setup命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
下载 Zip 下载中... 同仓库更多 Skills langchain-deploy-integration Deploy a LangChain 1.0 / LangGraph 1.0 app to Cloud Run, Vercel, or LangServe correctly — with timeouts sized for chain length, cold-start mitigation, SSE anti-buffering headers, and Secret Manager over .env. Use when prepping a first production deploy, debugging a stream that hangs behind a proxy, or diagnosing p99 latency spikes. Trigger with "langchain deploy", "langchain cloud run", "langchain vercel python", "langchain langserve", or "langchain docker".
langchain-langgraph-agents Build a correct LangGraph 1.0 ReAct agent with create_react_agent — typed tools, error propagation, recursion caps, and stop conditions that actually stop. Use when writing a first tool-calling agent, migrating from AgentExecutor or initialize_agent, or diagnosing an agent that loops on vague prompts. Trigger with "langgraph agent", "create_react_agent", "langgraph tool calling", "AgentExecutor migration", or "agent loop cost".
langchain-langgraph-human-in-loop Build LangGraph 1.0 human-in-the-loop approval flows with interrupt_before /
interrupt_after and Command(resume=...) — JSON-serializable state, clean
resume semantics, and UI wiring for approval decisions. Use when adding an
approval gate before an expensive tool call, wiring a Slack/web UI for agent
approvals, or debugging a graph that crashes on interrupt.
Trigger with "langgraph human in loop", "langgraph interrupt_before",
"langgraph approval flow", "Command resume", "langgraph HITL".
jeremylongshore
jeremylongshore/tons-of-skills-marketplace
打开 GitHub 仓库 name linear-multi-env-setup description 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".
allowed-tools Read, Write, Edit, Bash(vault:*), Bash(gcloud:*), Bash(aws:*) version 1.12.0 license MIT author Jeremy Longshore <jeremy@intentsolutions.io> tags ["saas","linear","deployment","api"] compatibility Designed for Claude Code
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
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
as
Environment
async
function
loadConfig
Promise
LinearEnvConfig
const
getEnvironment
if
"production"
"staging"
return
apiKey
await
getSecret
`linear-api-key-${env} `
webhookSecret
await
getSecret
`linear-webhook-secret-${env} `
defaultTeamKey
env
LINEAR_DEFAULT_TEAM_KEY
"ENG"
enableWebhooks
true
enableDebugLogging
"staging"
cacheEnabled
true
return
apiKey
env
LINEAR_API_KEY
""
webhookSecret
env
LINEAR_WEBHOOK_SECRET
""
defaultTeamKey
env
LINEAR_DEV_TEAM_KEY
"DEV"
enableWebhooks
false
enableDebugLogging
true
cacheEnabled
false
Step 2: Secret Manager Integration
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 () ?? "" ;
}
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 ?? "" ;
}
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 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 ();
return _config!;
}
export function setTestClient (client : LinearClient
Step 4: Environment Guards Prevent dangerous operations from running in the wrong environment.
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` );
}
}
async function deleteAllTestIssues (teamKey : string preventProduction ("deleteAllTestIssues" );
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 ();
}
}
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
const webhookConfigs : Record <Environment , {
resourceTypes : string [];
enabled : boolean ;
}> = {
development : {
resourceTypes : [],
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
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
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 },
];
try {
const client = new LinearClient ({ apiKey : config.apiKey });
const viewer = await client.viewer ;
const teams = await client.teams ();
const team = teams.nodes .find (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 =>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 NODE_ENV=staging npx tsx scripts/validate-environment.ts
Resources 