skills.rest
SmallAi-API
SmallAi-APICOMMUNITY
Explore all skills by this author →
WebsiteGitHub

linear

Manages Linear issues, sub-issue trees, status updates, and completion comments.

Updated Jan 27, 2026
Search Tags:#workflow#project management#issue tracking#status updates#task decomposition#linear#sub-issues
One-click install
npx skills add https://github.com/SmallAi-API/smaihub --skill linear-smallai-api
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: linear
Source: https://github.com/SmallAi-API/smaihub/tree/main/.agents/skills/linear
Command: npx skills add https://github.com/SmallAi-API/smaihub --skill linear-smallai-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Working with Linear issues manually leads to inconsistent statuses, missing completion comments, and messy sub-issue structures that teammates cannot follow. This Skill standardizes how AI agents retrieve, create, update, and close Linear issues so project tracking stays accurate. ## Core Features & Use Cases - Issue Lifecycle Management: Retrieve issue details, read embedded screenshots, mark issues In Progress, In Review, and Done at the right moments. - Sub-issue Tree Creation: Break parent issues into ordered, nested sub-issues with indexed titles, correct parent relations, and blockedBy dependency ordering. - Completion Comments & PR Linking: Post concise completion comments and link PRs with Fixes/Closes keywords so Linear auto-closes issues on merge. - Use Case: When implementing LOBE-1234, the agent reads the issue and its screenshots, marks it In Progress, creates a PR referencing the issue, moves it to In Review, and posts a completion comment after merge. ## Quick Start Use the linear skill to pick up LOBE-1234, mark it In Progress, and close it with a completion comment once the PR merges.

Frequently Asked Questions about linear

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

FAQPage Schema
How do I create sub-issues in Linear with dependencies?▼

Create sub-issues by topologically sorting the dependency graph so blockers exist first, then set parentId for nesting and blockedBy for dependencies. Prefix titles with ordering indexes like [1], [4.1] so the execution order stays readable even if the panel shuffles.

How to automatically close Linear issues from pull requests?▼

Include keywords like Fixes LOBE-123, Closes, or Resolves in the PR body so Linear links the PR and closes the issue on merge. Move the issue to In Review while the PR awaits merge, then Done after merging.

Does Linear support nested sub-issues beyond one level?▼

Yes, Linear supports unlimited sub-issue depth. Nest issues by logical parent-child relationships, such as core service to SDK to consumers, rather than creating flat sibling lists under one root.

Why is blockedBy not working when creating Linear issues?▼

blockedBy requires the blocker issue to already exist because you need its LOBE identifier. Create zero-dependency issues first, collect their IDs, then create dependent issues; blockedBy is append-only so re-running is safe.

When should a Linear issue be marked In Progress?▼

Mark an issue In Progress the moment you start planning or implementing it. This signals ownership to teammates so they do not pick up the same issue, and each issue should be fully closed out before starting the next.

Related Skills

Explore More Software Engineering Skills→
fcakyonfcakyon
1.0k

linear-usage

Standardize Linear issue creation with templates, labels, and triage workflows.

Community
Basic
Obsidian-OwlObsidian-Owl
4

speckit-pr

Create pull requests linked to Linear issues with generated descriptions.

Official
Advanced
evolution-foundationevolution-foundation
520

int-linear-review

Generate a Linear status report of blockers, stale issues, and assigned tasks.

Official
Intermediate
eric-sabeeric-sabe
1

issue-tracker-linear

Manage Linear issue lifecycle, project boards, and automated PR-linked closures.

Community
Intermediate