Linear Release Setup

Generates CI/CD configuration for Linear's release tracking system across GitHub Actions, GitLab CI, and CircleCI. The real value is in the interactive setup workflow that walks you through the pipeline vs. stage decision, which the docs call out as the most common mistake people make. It asks the right questions upfront: what do you ship independently, is each pipeline continuous or scheduled, what's your branching model, how do you version things. Then it fetches the latest README for current commands and flags before writing your config. Handles monorepo path filtering and reminds you about the Docker runtime gotchas on Alpine images. Saves you from setting up one giant pipeline when you actually need three smaller ones.

skills.sh installs: 15.3K
GitHub stars: 72
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add linear/linear-release --skill linear-release-setup --agent claude-code

Installs into .claude/skills of the current project.

Files

Linear Release Setup

The linear-release README is the source of truth for commands, flags, installation, environment variables, path filtering, and troubleshooting. Fetch it before generating any config — this skill focuses on the interactive setup workflow and the pipeline modeling decisions the README cannot make for the user.

Interactive Workflow

Step 1: Preflight

Before generating config, confirm:

Pipeline exists in Linear — the user must have created a release pipeline in Linear first (Settings → Releases). Each pipeline has its own access key.
Detect CI platform — look for .github/workflows/*.yml (GitHub Actions), .gitlab-ci.yml (GitLab CI), .circleci/config.yml (CircleCI), or other CI config.
Detect default branch — check git symbolic-ref refs/remotes/origin/HEAD or the CI config. Don't assume main.