linear

Before using Linear workflows, search for linear MCP tools. If not found, treat as not installed.

lobehub/lobe-chatUpdated Apr 8, 2026

Works with

Claude CodeCursorClineWindsurfCodexGooseGitHub CopilotZed

0

total installs

0

this week

74.8K

GitHub stars

0

upvotes

Install Skill

Run in your terminal

$npx skills add https://github.com/lobehub/lobe-chat --skill linear

0

installs

0

this week

74.8K

stars

Installation Guide

How to use linear on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your machine
  • Node.js 16+ with npm — verify with node --version
  • Active project directory where you want to add linear
2

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/lobehub/lobe-chat --skill linear

Fetches linear from lobehub/lobe-chat and configures it for Cursor.

3

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/linear

Restart Cursor to activate linear. Access via /linear in your agent's command palette.

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

Documentation

Linear Issue Management

Before using Linear workflows, search for linear MCP tools. If not found, treat as not installed.

⚠️ CRITICAL: PR Creation with Linear Issues

When creating a PR that references Linear issues (LOBE-xxx), you MUST:

  1. Create the PR with magic keywords (Fixes LOBE-xxx)
  2. IMMEDIATELY after PR creation, add completion comments to ALL referenced Linear issues
  3. Do NOT consider the task complete until Linear comments are added

This is NON-NEGOTIABLE. Skipping Linear comments is a workflow violation.

Workflow

  1. Retrieve issue details before starting: mcp__linear-server__get_issue
  2. Check for sub-issues: Use mcp__linear-server__list_issues with parentId filter
  3. Update issue status when completing: mcp__linear-server__update_issue
  4. Add completion comment (REQUIRED): mcp__linear-server__create_comment

Creating Issues

When creating issues with mcp__linear-server__create_issue, MUST add the claude code label.

Completion Comment Format

Every completed issue MUST have a comment summarizing work done:

## Changes Summary

- **Feature**: Brief description of what was implemented
- **Files Changed**: List key files modified
- **PR**: #xxx or PR URL

### Key Changes

- Change 1
- Change 2
- ...

This is critical for:

  • Team visibility
  • Code review context
  • Future reference

PR Association (REQUIRED)

When creating PRs for Linear issues, include magic keywords in PR body:

  • Fixes LOBE-123
  • Closes LOBE-123
  • Resolves LOBE-123

Per-Issue Completion Rule

When working on multiple issues, update EACH issue IMMEDIATELY after completing it:

  1. Complete implementation
  2. Run bun run type-check
  3. Run related tests
  4. Create PR if needed
  5. Update status to "In Review" (NOT "Done")
  6. Add completion comment immediately
  7. Move to next issue

Note: Status → "In Review" when PR created. "Done" only after PR merged.

❌ Wrong: Complete all → Create PR → Forget Linear comments

✅ Correct: Complete → Create PR → Add Linear comments → Task done

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Steps

  1. 1Install product management skill
  2. 2Start with user story generation for known feature
  3. 3Progress to competitive analysis: research 2-3 competitors
  4. 4Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5Draft stakeholder communications and refine based on feedback
  6. 6Build template library for recurring PM tasks
  7. 7Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use when

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid when

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Related Skills

Reviews

4.644 reviews
  • E
    Emma SethiDec 12, 2024

    linear reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • L
    Liam PatelDec 4, 2024

    Registry listing for linear matched our evaluation — installs cleanly and behaves as described in the markdown.

  • L
    Liam RaoNov 27, 2024

    linear is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • X
    Xiao OkaforNov 23, 2024

    Useful defaults in linear — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • E
    Emma IyerNov 3, 2024

    I recommend linear for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • D
    Diya ChenOct 22, 2024

    Useful defaults in linear — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • A
    Aditi DialloOct 18, 2024

    Keeps context tight: linear is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • A
    Aditi AbebeOct 14, 2024

    I recommend linear for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • O
    OshnikdeepSep 21, 2024

    linear has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • E
    Evelyn MartinezSep 17, 2024

    linear fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 44

1 / 5

Discussion

Comments — not star reviews
  • No comments yet — start the thread.