Use the skill to connect continuous integration to Linear Release

Install

npx skills add linear/linear-release

Who is it for?

If you already use Linear to manage releases and want continuous integration to maintain releases in Linear automatically after it finishes, this skill is a good fit. The official documentation presents it as a CLI that connects continuous integration with Linear release management. The product description is at

https://linear.app/docs/releases

The page does not name a specific coding agent. It only says that, after installation, you can run /linear-release-setup from your AI agent, or simply ask the agent to help set up Linear Release, and it will automatically pick up this skill. Therefore, do not interpret its support as exclusive to any one client.

It is better suited to people whose repository already has continuous integration and who want to generate a configuration they can inspect first, rather than immediately running the default sync in a production environment. The official documentation is at

https://github.com/linear/linear-release

Make your first attempt in 3 minutes

Use only this official installation path:

npx skills add linear/linear-release

Prerequisites: you already have an AI agent on the machine that can load this skill, and you can obtain the LINEAR_ACCESS_KEY provided by Linear. The command above determines the installation location; the page does not provide a second primary installer.

For the first task, choose a reversible setup and do not begin by running the default command that changes Linear data. In the agent, enter /linear-release-setup, or explicitly ask it to set up Linear Release. The official documentation says it generates continuous integration configuration for the project and supports GitHub Actions, GitLab CI, CircleCI, and other platforms. It also guides you through continuous or scheduled operation and monorepo path filtering. Generating the configuration writes files, so first ask it to explain which files it intends to change, then allow the write after you confirm.

A success signal is that the skill can be triggered by /linear-release-setup or natural language, the agent starts asking about the platform and continuous versus scheduled operation, and after your confirmation it provides an inspectable configuration draft instead of reporting that it is not installed. Until LINEAR_ACCESS_KEY has been placed in a secret store, do not let it create or update releases in Linear.

Use cases

Case one: generate continuous integration configuration suited to this repository first.

The official documentation describes the setup skill as generating configuration for the project, supporting platforms such as GitHub Actions, GitLab CI, and CircleCI, and covering continuous and scheduled operation as well as monorepo path filtering. For the first run, stop after generating the configuration and open the file for review. The page does not provide the complete template text for each platform or a syntax example for monorepo filtering. What can be confirmed is that these options exist and that the trigger is /linear-release-setup or asking the agent to pick up the skill automatically.

Case two: understand the default sync, but do not run it in production yet.

The official documentation states that the default command creates a release or adds issues to the current release. This changes Linear data. For the first run, ask the agent only to explain which commits or issues it will use, and confirm that LINEAR_ACCESS_KEY exists only in a secret store; execute it only after you explicitly agree. The page does not list all sync parameters or describe failure rollback. After continuous integration is connected, it runs automatically; the cited passage stops after “automatically:” and contains no further sentences.

Both paths use the same npx installation command.

Usage boundaries

The CI configuration must provide LINEAR_ACCESS_KEY. The official table marks it as required and identifies its source as Linear's pipeline access key. Do not write the key into the repository, and do not invent a placeholder key. The page does not describe a read-only demonstration mode without a key.

setup writes continuous integration files, while sync changes release and issue assignments in Linear. No client is named; the only instruction is to “run it from your AI agent.” GitHub Actions, GitLab CI, and CircleCI are configuration targets, not another skill installer.

For details of Linear release management, refer to