linear-sync

Automate Linear issue state transitions based on current branch workflow states.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/acme-skunkworks/changelog-core --skill linear-sync-acme-skunkworks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linear-sync
Source: https://github.com/acme-skunkworks/changelog-core/tree/main/.agents/skills/linear-sync
Command: npx skills add https://github.com/acme-skunkworks/changelog-core --skill linear-sync-acme-skunkworks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill synchronizes the state of Linear issues with the workflow states of the current branch, streamlining issue tracking and collaboration.

Core Features & Use Cases

  • Branch-based Issue Tracking: Automates state transitions for Linear issues based on the current branch name.
  • State Resolution by Team Name: Resolves state IDs using team names, ensuring stability across team renames.
  • Idempotent State Transitions: Ensures that only the necessary transitions are applied, avoiding unnecessary updates.
  • Use Case: Use this Skill to automatically move issues to 'In Progress' when a new branch is created, to 'In Review' when a pull request is opened, and to 'Done' during branch cleanup.

Quick Start

Sync the state of Linear issues for the current branch by running the 'linear-sync' command.

Frequently Asked Questions about linear-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync Linear issue states with branch workflow states automatically?

To sync Linear issue states with branch workflow states, you can use an automation tool that transitions issue statuses based on the current branch name. This requires the Linear MCP server and git CLI to map branch actions to specific Linear states.

What is the best way to automate Linear issue tracking based on git branches?

Automating Linear issue tracking based on git branches involves mapping branch workflow states to issue statuses. This ensures issues move to 'In Progress' on branch creation and 'In Review' when a PR opens, keeping project tracking aligned with development.

Do I need the Linear MCP server to automate issue state transitions?

Yes, the Linear MCP server is required to automate issue state transitions. Along with the git CLI, it provides the necessary integration to resolve team state IDs and apply idempotent updates to your Linear issues.

Can I test branch workflow state transitions before applying them to Linear?

Yes, you can test branch workflow state transitions using a dry-run mode. This allows you to verify which Linear issue states will be changed without actually applying the updates, preventing unnecessary or redundant modifications.

How does state resolution by team name work for Linear issues?

State resolution by team name works by mapping branch states to Linear state IDs using the team's name rather than hardcoded IDs. This ensures stability and prevents tracking errors even if your team is renamed in Linear.

Will syncing Linear states create redundant updates if the issue is already in the correct state?

No, syncing Linear states will not create redundant updates. The process checks the current issue status and only applies transitions when necessary, ensuring idempotent state changes and avoiding unnecessary API calls.