linear-delivery-sync

Fetch Linear issue and project data to align code changes with task scope.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/lemessdavi/ia-prev --skill linear-delivery-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linear-delivery-sync
Source: https://github.com/lemessdavi/ia-prev/tree/main/skills/linear-delivery-sync
Command: npx skills add https://github.com/lemessdavi/ia-prev --skill linear-delivery-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Align development work with Linear as the source of truth for issues and projects, reducing drift between planning and delivery.

Core Features & Use Cases

  • Read canonical Linear URLs to fetch issue and project data and align scope with code changes.
  • Suggest concise, actionable progress updates for active cards.
  • Propose documentation updates when architecture or workflows change to keep Linear documentation in sync.

Quick Start

Synchronize your current branch changes with the corresponding Linear items to keep status aligned.

Frequently Asked Questions about linear-delivery-sync

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

FAQPage Schema
How do I sync code changes with Linear issues to update project status?

You can sync branch changes with Linear issues by providing canonical Linear URLs. The Skill fetches the corresponding issue and project data, maps the scope from your code changes, and suggests actionable progress updates for the active cards.

Can I use this to automatically update Linear documentation when architecture changes?

Yes, you can use it to propose documentation updates when architecture or workflows change. The Skill aligns development work with Linear as the source of truth and suggests documentation guidance to prevent drift between planning and delivery.

Does the Linear issue sync process modify project state automatically?

No, the Linear issue sync process does not modify project state automatically. It fetches issue and project data to suggest concise progress updates and documentation changes, ensuring no state is altered unless you explicitly request it.

What is the best way to map current task scope from code changes to Linear projects?

The best way to map task scope is by aligning development work with Linear as the source of truth. Read canonical Linear URLs to fetch project data, match your code changes and tests to the corresponding items, and suggest updates to reduce drift.

Why keep Linear as the source of truth for issue and project tracking?

Keep Linear as the source of truth for issue and project tracking to reduce drift between planning and delivery. It provides a canonical URL structure to fetch data, map code changes accurately, and keep status updates and documentation consistently aligned.