Agent skill

linear

Linear issue management. Use for LOBE-xxx issues, Linear links, PRs referencing Linear, retrieving issues, updating status, completion comments, or sub-issue trees.

LobeHub80,937★ · +310/wk · 1 repos on radarProfile →
claude-codeNOASSERTION
Install
npx skills add lobehub/lobehub --skill linear --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 7 KB
Bundled scripts: none
Path: .agents/skills/linear/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 81,252 · +315 this week
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Linear Issue Management Before using Linear workflows, search for `linear` MCP tools. If not found, treat as not installed. ## PR Creation with Linear Issues A PR that fixes a Linear issue has **two separate jobs to do**, and both matter: 1. **`Fixes LOBE-xxx` in the PR body** — Linear watches GitHub for these magic keywords and auto-links the PR and auto-closes the issue on merge. This is the machine-readable side. 2. **A completion comment on the Linear issue** — gives the reviewer/PM/teammate landing in Linear a human-readable summary of what changed and why, without forcing them to click through to GitHub and read a diff. If you only do step 1, Linear watchers (often non-engineers) hit the issue and see no context. So pair PR creation with the Linear comment as part of the same task — finish both before considering the work done. ## Workflow 1. **Retrieve issue details** before starting: `mcp__linear-server__get_issue` 2. **Read images** — issue descriptions often contain screenshots with critical context (mockups, error states, before/after). Use `mcp__linear-server__extract_images` so you actually see them; reading raw markdown alone misses what the reporter was looking at.

What's inside
Steps it walks through
  1. PR Creation with Linear Issues
  2. Workflow
  3. Creating Issues
  4. Language
  5. Creating Sub-issue Trees
  6. 1. Prefix titles with an ordering index
  7. 2. Nest sub-issues by logical parent-child, not flat under the root
  8. 3. Sub-issue creation order is dictated by blockedBy
  9. 4. Don't waste rounds trying to parallelize
  10. 5. Keep each sub-issue description self-contained
  11. Completion Comment Format
  12. PR Association
  13. Per-Issue Completion Rule
More from lobehub
All skills →
About this skill
What does the linear skill do?

Linear issue management. Use for LOBE-xxx issues, Linear links, PRs referencing Linear, retrieving issues, updating status, completion comments, or sub-issue trees.

How do I install it?

Run `npx skills add lobehub/lobehub --skill linear --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From lobehub/lobehub, a repository with 81,252 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going