linear-deploy-integration
Deploy Linear-integrated applications and track deployments. Use when deploying to production, linking deploys to issues, or setting up deployment tracking with Vercel/Railway/Cloud Run. Trigger: "deploy linear integration", "linear deployment", "linear vercel", "track linear deployments", "linear deploy tracking".
Best use case
linear-deploy-integration is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Deploy Linear-integrated applications and track deployments. Use when deploying to production, linking deploys to issues, or setting up deployment tracking with Vercel/Railway/Cloud Run. Trigger: "deploy linear integration", "linear deployment", "linear vercel", "track linear deployments", "linear deploy tracking".
Teams using linear-deploy-integration 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-deploy-integration/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How linear-deploy-integration Compares
| Feature / Agent | linear-deploy-integration | 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?
Deploy Linear-integrated applications and track deployments. Use when deploying to production, linking deploys to issues, or setting up deployment tracking with Vercel/Railway/Cloud Run. Trigger: "deploy linear integration", "linear deployment", "linear vercel", "track linear deployments", "linear deploy tracking".
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
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 Deploy Integration
## Overview
Deploy Linear-integrated applications with automatic deployment tracking. Linear's GitHub integration links PRs to issues using magic words (`Fixes`, `Closes`, `Resolves`) and auto-detects Vercel preview links. This skill adds custom deployment comments, state transitions, and rollback tracking.
## Prerequisites
- Working Linear integration with API key or OAuth
- Deployment platform (Vercel, Railway, Cloud Run, etc.)
- GitHub integration enabled in Linear (Settings > Integrations > GitHub)
## Instructions
### Step 1: Deployment Workflow with Linear Tracking
```yaml
# .github/workflows/deploy.yml
name: Deploy and Track
on:
push:
branches: [main]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0 # Full history for commit scanning
- name: Deploy
id: deploy
run: |
# Replace with your deploy command
DEPLOY_URL=$(npx vercel deploy --prod --token=${{ secrets.VERCEL_TOKEN }} 2>&1 | tail -1)
echo "url=$DEPLOY_URL" >> $GITHUB_OUTPUT
- name: Track deployment in Linear
if: success()
env:
LINEAR_API_KEY: ${{ secrets.LINEAR_API_KEY }}
run: |
npx tsx scripts/track-deployment.ts \
--env production \
--url "${{ steps.deploy.outputs.url }}" \
--sha "${{ github.sha }}" \
--before "${{ github.event.before }}"
- name: Create failure issue
if: failure()
env:
LINEAR_API_KEY: ${{ secrets.LINEAR_API_KEY }}
run: |
curl -s -X POST https://api.linear.app/graphql \
-H "Authorization: $LINEAR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"query": "mutation($i: IssueCreateInput!) { issueCreate(input: $i) { success } }",
"variables": { "i": { "teamId": "${{ vars.LINEAR_TEAM_ID }}", "title": "[Deploy] Failed: ${{ github.sha }}", "priority": 1 } }
}'
```
### Step 2: Deployment Tracking Script
```typescript
// scripts/track-deployment.ts
import { LinearClient } from "@linear/sdk";
import { execSync } from "child_process";
import { parseArgs } from "util";
const { values } = parseArgs({
options: {
env: { type: "string" },
url: { type: "string" },
sha: { type: "string" },
before: { type: "string" },
},
});
async function trackDeployment() {
const client = new LinearClient({ apiKey: process.env.LINEAR_API_KEY! });
// Extract Linear issue IDs from commit messages since last deploy
const log = execSync(
`git log --oneline ${values.before}..${values.sha} 2>/dev/null || echo ""`
).toString();
const issueIds = [...new Set(log.match(/[A-Z]+-\d+/g) ?? [])];
console.log(`Found ${issueIds.length} Linear issues in commits: ${issueIds.join(", ")}`);
for (const identifier of issueIds) {
const results = await client.issueSearch(identifier);
const issue = results.nodes.find(i => i.identifier === identifier);
if (!issue) continue;
// Add deployment comment
await client.createComment({
issueId: issue.id,
body: `Deployed to **${values.env}**: [${values.url}](${values.url})\n\nCommit: \`${values.sha?.substring(0, 7)}\``,
});
// Auto-transition based on environment
const team = await issue.team;
const states = await team!.states();
if (values.env === "staging") {
const reviewState = states.nodes.find(s =>
s.name.toLowerCase().includes("review")
);
if (reviewState) await issue.update({ stateId: reviewState.id });
} else if (values.env === "production") {
const doneState = states.nodes.find(s => s.type === "completed");
if (doneState) await issue.update({ stateId: doneState.id });
}
console.log(`Updated ${identifier} — deployed to ${values.env}`);
}
}
trackDeployment().catch(console.error);
```
### Step 3: Rollback Tracking
```typescript
async function trackRollback(
client: LinearClient,
issueIdentifier: string,
reason: string
) {
const results = await client.issueSearch(issueIdentifier);
const issue = results.nodes[0];
if (!issue) return;
// Add rollback comment
await client.createComment({
issueId: issue.id,
body: `**Rolled back from production**\n\nReason: ${reason}\n\nIssue moved back to In Progress.`,
});
// Move back to In Progress with elevated priority
const team = await issue.team;
const states = await team!.states();
const inProgress = states.nodes.find(s =>
s.name.toLowerCase() === "in progress"
);
if (inProgress) {
await issue.update({ stateId: inProgress.id, priority: 1 });
}
}
```
### Step 4: PR Template for Deployment Tracking
```markdown
<!-- .github/PULL_REQUEST_TEMPLATE.md -->
## Linear Issues
<!-- Linear auto-links when you use magic words -->
Fixes ENG-XXX
## Deployment Notes
- [ ] Requires database migration
- [ ] Requires environment variable changes
- [ ] Requires Linear webhook reconfiguration
- [ ] Requires secret rotation
```
### Step 5: Deployment Dashboard Query
```typescript
// Query recently deployed issues
async function getDeploymentSummary(client: LinearClient, days = 14) {
const since = new Date(Date.now() - days * 24 * 60 * 60 * 1000).toISOString();
const completed = await client.issues({
filter: {
state: { type: { eq: "completed" } },
completedAt: { gte: since },
},
first: 100,
orderBy: "completedAt",
});
console.log(`${completed.nodes.length} issues completed in last ${days} days:`);
for (const issue of completed.nodes) {
const assignee = await issue.assignee;
console.log(` ${issue.identifier}: ${issue.title} (${assignee?.name ?? "unassigned"})`);
}
return completed.nodes;
}
```
## Error Handling
| Error | Cause | Solution |
|-------|-------|----------|
| `LINEAR_API_KEY` not set | Missing CI secret | Add to GitHub repo Settings > Secrets |
| Issue not found | Wrong workspace or deleted | Verify team key matches workspace |
| Preview links not appearing | GitHub integration off | Enable in Linear Settings > Integrations > GitHub |
| Deploy comment missing | Issue ID not in commits | Follow branch naming: `feature/ENG-123-desc` |
## Examples
### Multi-Environment Matrix
```yaml
strategy:
matrix:
include:
- env: staging
trigger: pull_request
- env: production
trigger: push
```
## Resources
- [Linear GitHub Integration](https://linear.app/docs/github)
- [Vercel Deploy Hooks](https://vercel.com/docs/deploy-hooks)
- [Linear API Authentication](https://linear.app/developers/graphql)Related Skills
running-integration-tests
Execute integration tests validating component interactions and system integration. Use when performing specialized testing. Trigger with phrases like "run integration tests", "test integration", or "validate component interactions".
research-to-deploy
Researches infrastructure best practices and generates deployment-ready configurations, Terraform modules, Dockerfiles, and CI/CD pipelines. Use when the user needs to deploy services, set up infrastructure, or create cloud configurations based on current best practices. Trigger with phrases like "research and deploy", "set up Cloud Run", "create Terraform for", "deploy this to AWS", or "generate infrastructure configs".
workhuman-deploy-integration
Workhuman deploy integration for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman deploy integration".
workhuman-ci-integration
Workhuman ci integration for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman ci integration".
wispr-deploy-integration
Wispr Flow deploy integration for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr deploy integration".
wispr-ci-integration
Wispr Flow ci integration for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr ci integration".
windsurf-ci-integration
Integrate Windsurf Cascade workflows into CI/CD pipelines and team automation. Use when automating Cascade tasks in GitHub Actions, enforcing AI code quality gates, or setting up Windsurf config validation in CI. Trigger with phrases like "windsurf CI", "windsurf GitHub Actions", "windsurf automation", "cascade CI", "windsurf pipeline".
webflow-deploy-integration
Deploy Webflow-powered applications to Vercel, Fly.io, and Google Cloud Run with proper secrets management and Webflow-specific health checks. Trigger with phrases like "deploy webflow", "webflow Vercel", "webflow production deploy", "webflow Cloud Run", "webflow Fly.io".
webflow-ci-integration
Configure Webflow CI/CD with GitHub Actions — automated CMS validation, integration tests with test tokens, and publish-on-merge workflows. Use when setting up automated testing or CI pipelines for Webflow integrations. Trigger with phrases like "webflow CI", "webflow GitHub Actions", "webflow automated tests", "CI webflow", "webflow pipeline".
vercel-deploy-preview
Create and manage Vercel preview deployments for branches and pull requests. Use when deploying a preview for a pull request, testing changes before production, or sharing preview URLs with stakeholders. Trigger with phrases like "vercel deploy preview", "vercel preview URL", "create preview deployment", "vercel PR preview".
vercel-deploy-integration
Deploy and manage Vercel production deployments with promotion, rollback, and multi-region strategies. Use when deploying to production, configuring deployment regions, or setting up blue-green deployment patterns on Vercel. Trigger with phrases like "deploy vercel", "vercel production deploy", "vercel promote", "vercel rollback", "vercel regions".
veeva-deploy-integration
Veeva Vault deploy integration for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva deploy integration".