linear

Manages Linear issues, sub-issue trees, and PR associations via Linear MCP tools.

74|11|Updated Jul 4, 2024
One-click install
npx skills add https://github.com/OpenSourceAGI/qwksearch-research-agent --skill linear-opensourceagi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linear
Source: https://github.com/OpenSourceAGI/qwksearch-research-agent/tree/main/apps/qwk-in-lobe/.agents/skills/linear
Command: npx skills add https://github.com/OpenSourceAGI/qwksearch-research-agent --skill linear-opensourceagi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating Linear issue tracking with GitHub pull requests is error-prone: issues get forgotten in "In Progress", completion context never reaches non-engineer stakeholders, and sub-issue trees lose their ordering. This Skill standardizes the full Linear workflow so issues, comments, and PRs stay synchronized. ## Core Features & Use Cases - Issue Lifecycle Management: Retrieve issues with images, mark In Progress, update status to In Review, and post structured completion comments. - Sub-issue Tree Creation: Build ordered, nested sub-issue hierarchies using title index prefixes and blockedBy dependency ordering to work around Linear MCP limitations. - PR Association: Link PRs to issues with magic keywords like "Fixes LOBE-123" for auto-linking and auto-closing on merge. - Use Case: When implementing a feature tracked as LOBE-456, retrieve the issue with its screenshots, break it into an ordered sub-issue tree, then close out each issue with a status update and completion comment as its PR ships. ## Quick Start Ask the agent to pick up Linear issue LOBE-123, mark it In Progress, implement the fix, and close it out with a PR and completion comment.

Frequently Asked Questions about linear

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

FAQPage Schema
How do I link a GitHub PR to a Linear issue?

Include magic keywords like "Fixes LOBE-123", "Closes LOBE-123", or "Resolves LOBE-123" in the PR body. Linear watches GitHub for these keywords, auto-links the PR, and auto-closes the issue when the PR merges.

How do I create ordered sub-issues in Linear with MCP tools?

The Linear MCP save_issue tool does not expose subIssueSortOrder, so encode execution order in titles using index prefixes like [1], [2], [4.1]. Create issues in topological order since blockedBy requires the blocker issue to exist first.

Does the Linear MCP integration support reading issue screenshots?

Yes, use the extract_images tool to view screenshots embedded in issue descriptions. Reading raw markdown alone misses visual context like mockups, error states, and before/after comparisons that reporters attach.

When should a Linear issue be marked Done versus In Review?

Set the status to In Review when the implementation and PR are complete, not Done. Done is reserved for after the PR actually merges, keeping the board accurate for teammates tracking progress.

What happens if the Linear MCP server is not installed?

The workflow first searches for linear MCP tools before proceeding. If none are found, the integration is treated as not installed and Linear operations should not be attempted.