linear

Synchronize Linear issue workflows with GitHub PR activity.

1|Updated May 9, 2026
One-click install
npx skills add https://github.com/duwenji/generative-ai-oss-tutorials --skill linear-duwenji
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linear
Source: https://github.com/duwenji/generative-ai-oss-tutorials/tree/main/sandbox/lobe-chat/.agents/skills/linear
Command: npx skills add https://github.com/duwenji/generative-ai-oss-tutorials --skill linear-duwenji

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Linear issue management breaks down when PRs are created without a complete, human-readable update in Linear, leaving teammates with no context and causing status fragmentation across systems.

Core Features & Use Cases

  • PR-to-Issue Auto-Linking: Use Linear’s magic keywords in the PR body (Fixes/Closes/Resolves) so merges reliably connect back to the correct LOBE-xxx issue.
  • Completion Comments for Human Context: Add a summary comment on the Linear issue so reviewers and teammates understand what changed without reading diffs.
  • Image-Aware Issue Reading: Extract screenshots from issue descriptions to avoid missing crucial visual details.
  • Sub-Issue Tree Planning: Create logical parent-child decomposition with ordering and dependency rules that fit Linear’s tooling limitations.

Quick Start

Retrieve the issue details in Linear, extract any images from the issue description, update the issue to In Progress, and then when your PR is ready include Fixes LOBE-xxx in the PR body and post a completion comment that summarizes the changes.

Frequently Asked Questions about linear

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

FAQPage Schema
How do I automatically update Linear issue status when a GitHub PR is merged?

You can automatically update Linear issue status by including magic keywords like Fixes, Closes, or Resolves followed by the LOBE-xxx issue ID in your GitHub PR body to trigger Linear's auto-link and auto-close features.

What is the best way to keep Linear issues synced with GitHub PR activity?

Keep Linear issues synced with GitHub PR activity by retrieving issue details, updating status to In Progress, and posting completion summary comments on the Linear issue to provide human-readable context for teammates.

How do I create ordered sub-issue trees in Linear for scoped delivery?

You create ordered sub-issue trees in Linear by using MCP tools to create or save issues with correct parent and blockedBy relations, establishing logical parent-child decomposition that fits Linear's tooling limitations.

Can I extract images from Linear issue descriptions when managing workflows?

Yes, you can extract screenshots and images from Linear issue descriptions during workflow management by using Linear MCP tools to retrieve issue details, ensuring crucial visual details are not missed.

Why should I post completion comments on Linear issues after creating a PR?

You should post completion comments on Linear issues after creating a PR so reviewers and teammates understand what changed without needing to read the code diffs, preventing status fragmentation across systems.

Does Linear workflow automation handle existing issues or only new ones?

Linear workflow automation handles existing LOBE-xxx issues by retrieving their details, extracting images, listing sub-issues, updating statuses, and creating ordered sub-issue trees with correct parent and blockedBy relations.