linear-sync

Syncs Linear issue states with code evidence from project-status repositories.

2|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/my-entourage/entourage-plugin --skill linear-sync-my-entourage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linear-sync
Source: https://github.com/my-entourage/entourage-plugin/tree/main/skills/linear-sync
Command: npx skills add https://github.com/my-entourage/entourage-plugin --skill linear-sync-my-entourage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bridges gaps between Linear issue states and real development progress by syncing issues with code evidence from project-status.

Core Features & Use Cases

  • Read evidence from local repos, GitHub, and transcripts using /project-status and repository sources.
  • Map evidence to Linear states, perform upgrade-only updates, and attach explanatory comments with sources.
  • Preview changes and require explicit confirmation before applying updates.

Quick Start

Run /linear-sync with optional component names to begin syncing Linear with your code evidence.

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 actual development progress in my code?

Syncing Linear issues with code evidence requires reading project status from local repos, GitHub, and transcripts, then mapping that evidence to Linear states. It previews changes and applies upgrade-only status updates after explicit confirmation.

Can I automatically update Linear tickets based on code commits and project status?

Yes, automatic Linear ticket updates are possible by mapping code evidence to Linear states. The system upgrades issue statuses only, never downgrades them, and requires explicit confirmation before applying any changes to your tickets.

Do I need a Linear API token or MCP to connect Linear issues with my repositories?

Connecting Linear issues with repositories requires Linear MCP or an API token fallback. Additionally, a valid .entourage/repos.json configuration file is required to locate teams, workspaces, and access sources for the sync process.

What is the best way to prevent Linear status downgrades when syncing with code evidence?

The best way to prevent downgrades is using an upgrade-only sync mechanism that maps code evidence to Linear states. This ensures issue statuses only advance forward, never regress, protecting your project tracking integrity.

Does linear-sync support previewing changes before updating Linear issue statuses?

Yes, linear-sync supports previewing changes before updating Linear issue statuses. It requires explicit confirmation for scoped updates per component, ensuring you review all status upgrades and explanatory comments before they are applied.

Why are my Linear issues not reflecting recent development progress from my repositories?

Linear issues may not reflect development progress if code evidence has not been mapped to Linear states. Syncing issues with project-status evidence bridges this gap by applying upgrade-only updates with explanatory source comments.