linear-sync

Syncs trAInR change-folder milestones to linked Linear issues via MCP comments and status transitions.

Updated May 20, 2026
One-click install
npx skills add https://github.com/ZawilecxD/trAInR --skill linear-sync-zawilecxd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linear-sync
Source: https://github.com/ZawilecxD/trAInR/tree/main/.cursor/skills/linear-sync
Command: npx skills add https://github.com/ZawilecxD/trAInR --skill linear-sync-zawilecxd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping Linear issues aligned with actual repository work requires manual status updates and comments at every milestone, which developers often forget. This Skill automates posting milestone comments and status transitions to a linked Linear issue as planning and implementation progress. ## Core Features & Use Cases - Milestone Comments: Posts idempotent, deduplicated comments for plan-drafted, implement-started, phase-complete, decision-log, implementation-reviewed, and implemented events. - Status Transitions: Moves issues to In Progress when implementation starts and closes per-phase child issues when phases complete, never regressing states. - Issue Resolution: Reads linear_issue and phase_issues mappings from change.md frontmatter, with user confirmation before the first write per session. - Use Case: While running an implementation workflow on a change folder linked to ZAW-42, the Skill automatically comments on the issue when the plan is drafted, moves it to In Progress when coding starts, and closes child phase issues as each phase commit lands. ## Quick Start Link a Linear issue by adding linear_issue: ZAW-42 to the change.md frontmatter and let the planning or implementation workflow sync milestones automatically.

Frequently Asked Questions about linear-sync

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

FAQPage Schema
How do I link a Linear issue to a change folder?

Add linear_issue: ZAW-N to the change.md frontmatter in context/changes/<change-id>/. Alternatively, pass the issue identifier in the current user message, such as /10x-implement foo ZAW-42.

How does Linear issue sync avoid duplicate comments?

Every sync comment starts with a level-2 heading like ## trAInR — plan-drafted that acts as a dedup key. Before posting, the skill lists existing comments and skips posting if a comment with the same event key already exists.

Can Linear sync update per-phase child issues automatically?

Yes, if change.md contains a phase_issues mapping of phase numbers to child issue identifiers. When a phase completes, the parent issue gets a milestone comment and the mapped child issue is moved to a done-like status.

What happens if no Linear issue is linked to a change?

The sync is skipped entirely and the user sees one line explaining that no linear_issue was found in change.md. The skill never guesses issue IDs from change-ids or branch names.

Why did my Linear issue not move to In Progress when implementation started?

The transition only happens if the current state is backlog or todo-like. Issues already In Progress, In Review, Done, or Canceled are left unchanged, and the skill never moves an issue backward.