Linear Release CI/CD setup assistant
Interactive setup for Linear Release tracking — pipeline modeling (stages vs pipelines), CI config generation for GitHub Actions, GitLab CI, CircleCI
- What
- Interactive setup for Linear Release tracking — pipeline modeling (stages vs pipelines), CI config generation for GitHub Actions, GitLab CI, CircleCI
- Cost
- Free
- Needs
- 💳 a Linear plan with the Releases feature (paid — free-tier eligibility unconfirmed); a release pipeline created in Linear (Settings → Releases) — each pipeline has its own access key to store as a CI secret; Docker-based CI must use a glibc image (no Alpine/musl)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
💳 Paid API required / API payante requise — Curated by Skill Harbor — Linear's official setup skill for the linear-release CLI: an interactive workflow that models your release pipelines before generating CI configuration. It walks through pipeline-vs-stage modeling with a concrete test (can two things be in-flight at the same time holding different commits? then separate pipelines, not stages), continuous vs scheduled releases, branch models, version sources, monorepo path filters, then generates the config for GitHub Actions (preferring the official action), GitLab CI or CircleCI with copy-paste example templates. Includes the Docker gotchas (glibc only — no Alpine, `git` and `curl` must be installed) and a pre-merge checklist (full clone, one access key per pipeline, correct binary platform, correct branch triggers). By @linear, listed here with credit to its creator. Honest caveats: requires a Linear plan with the Releases feature — paid service, free-tier eligibility unconfirmed; you must create a release pipeline in Linear first — each pipeline has its own access key stored as a CI secret; the skill explicitly defers to the official linear-release README as the source of truth for commands and flags (your agent fetches it at use time rather than trusting the skill's memory); the prebuilt binary needs glibc, so Docker-based CI must avoid Alpine/musl. Discovered via skills.sh. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Linear Release CI/CD setup assistant is a free listing for Linear's setup skill for the linear-release CLI. It interactively models release pipelines before generating CI configuration, with a pipeline-versus-stage test, continuous versus scheduled releases, branch models, version sources and monorepo filters. It then generates config for GitHub Actions, GitLab CI or CircleCI, and requires a paid API.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 28cdc75Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: 💳 a Linear plan with the Releases feature (paid — free-tier eligibility unconfirmed); a release pipeline created in Linear (Settings → Releases) — each pipeline has its own access key to store as a CI secret; Docker-based CI must use a glibc image (no Alpine/musl) Install "Linear Release CI/CD setup assistant" for me. Give my agent Linear's official interactive workflow for setting up release tracking — pipeline-vs-stage modeling, CI config generation for GitHub Actions, GitLab CI or CircleCI, Docker gotchas and the pre-merge checklist Repository: https://raw.githubusercontent.com/linear/linear-release/28cdc75530cf9667b410b685652cc0c3b7f0b50b/skills/linear-release-setup/SKILL.md Pinned version: install the code at commit 28cdc75530cf9667b410b685652cc0c3b7f0b50b exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the linear-linear-release-linear-release-setup skill from the repository into a temporary folder 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "linear-linear-release-linear-release-setup". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. create my release pipeline in Linear and add the access key as a CI secret). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 28cdc75 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: registry.npmjs.org
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.