This Claude skill provides a comprehensive integration with Linear, the purpose-built tool for modern software teams. It enables users to manage the entire issue lifecycle—from creation and assignment to status tracking and commenting—directly through natural language. By bridging the gap between AI-driven development and project tracking, it ensures that project backlogs remain accurate and up-to-date without manual context switching.

When should I use linear?

linear is useful in the following scenarios: • Instant Issue Creation: Quickly transform chat-based bug reports or feature ideas into structured Linear issues with defined priorities, teams, and labels. • Workflow Automation: Update issue statuses (e.g., moving a task to 'In Progress' or 'Done') and add progress comments automatically as work evolves. • Sprint & Cycle Management: Retrieve and list issues for specific cycles or teams to facilitate daily standups and sprint planning sessions. • Contextual Search: Search for existing tickets by keywords, assignees, or projects to avoid duplicates and gather historical context for current tasks. • Integrated Triage: Efficiently manage incoming bugs by assigning them to the correct team members and setting urgency levels via CLI-driven commands.

name	linear
description	Manage Linear issues and workflows. Use for viewing, creating, and updating Linear issues, and integrating with development workflow.

Linear Issue Manager

Manage Linear issues using the linearis CLI.

Prerequisites

Install linearis CLI:

bun add -g linearis

Set your API token:

export LINEAR_API_KEY=lin_api_xxxxx

Get your API key from: Linear Settings > API > Personal API keys

CLI Reference

List Issues

# List issues (default: 25)
linearis issues list

# Limit results
linearis issues list --limit 10

Search Issues

# Search by query
linearis issues search "bug"

# Filter by team
linearis issues search "authentication" --team ENG

# Filter by assignee
linearis issues search "feature" --assignee user-id

# Filter by project
linearis issues search "api" --project "Backend"

# Filter by status
linearis issues search "bug" --status "In Progress,Todo"

# Combined filters with limit
linearis issues search "urgent" --team ENG --limit 5

Get Issue Details

# Read issue by ID or identifier
linearis issues read ENG-123
linearis issues read abc123-uuid

Create Issues

# Basic issue (requires team)
linearis issues create "Fix login bug" --team ENG

# With description
linearis issues create "Add OAuth support" --team ENG -d "Implement Google OAuth"

# With priority (1=Urgent, 2=High, 3=Medium, 4=Low)
linearis issues create "Critical fix" --team ENG -p 1

# With assignee
linearis issues create "Review code" --team ENG --assignee user-id

# With labels
linearis issues create "Security issue" --team ENG --labels "bug,security"

# With project
linearis issues create "New feature" --team ENG --project "Q1 Roadmap"

# With status
linearis issues create "Started task" --team ENG --status "In Progress"

# Full example
linearis issues create "Implement caching" \
  --team ENG \
  -d "Add Redis caching for API responses" \
  -p 2 \
  --labels "feature,performance" \
  --project "Backend" \
  --status "Todo"

Update Issues

# Update title
linearis issues update ENG-123 -t "New title"

# Update description
linearis issues update ENG-123 -d "Updated description"

# Change status
linearis issues update ENG-123 -s "In Progress"
linearis issues update ENG-123 -s "Done"

# Change priority
linearis issues update ENG-123 -p 1

# Change assignee
linearis issues update ENG-123 --assignee user-id

# Add labels (default mode: adding)
linearis issues update ENG-123 --labels "urgent,blocked"

# Replace all labels
linearis issues update ENG-123 --labels "new-label" --label-by overwriting

# Clear all labels
linearis issues update ENG-123 --clear-labels

# Set parent issue
linearis issues update ENG-123 --parent-ticket ENG-100

# Clear parent
linearis issues update ENG-123 --clear-parent-ticket

# Set cycle
linearis issues update ENG-123 --cycle "Sprint 5"

# Clear cycle
linearis issues update ENG-123 --clear-cycle

Comments

# Add comment to issue
linearis comments create ENG-123 --body "Working on this now"

Teams

# List all teams
linearis teams list

Labels

# List all labels
linearis labels list

Projects

# List projects
linearis projects list

Cycles

# List cycles
linearis cycles list

Users

# List users
linearis users list

Workflow Patterns

Start Work on Issue

# 1. Find the issue
linearis issues search "feature name" --team ENG

# 2. Get details
linearis issues read ENG-123

# 3. Update status to In Progress
linearis issues update ENG-123 -s "In Progress"

# 4. Create branch (from issue identifier)
git checkout -b eng-123-feature-name

Complete an Issue

# 1. Update status
linearis issues update ENG-123 -s "Done"

# 2. Add completion comment
linearis comments create ENG-123 --body "Completed in PR #456"

Daily Standup View

# My in-progress issues
linearis issues search "assignee:me" --status "In Progress"

# Team's blocked issues
linearis issues search "" --team ENG --status "Blocked"

Bug Triage

# Find unassigned bugs
linearis issues search "label:bug" --team ENG

# Assign and prioritize
linearis issues update ENG-456 --assignee user-id -p 1

Git Integration

Link Commits

Mention issue ID in commit message:

git commit -m "feat: implement caching

Fixes ENG-123"

Create PR with Issue Link

ISSUE_ID="ENG-123"
gh pr create --title "feat: implement caching" --body "Closes $ISSUE_ID"

Priority Values

Value	Meaning
0	No priority
1	Urgent
2	High
3	Medium
4	Low

Best Practices

Use issue IDs - Reference ENG-123 in commits/PRs
Update status - Move issues through workflow with linearis issues update
Add comments - Track progress with linearis comments create
Use labels - Categorize for filtering
Link PRs - Connect code to issues
Search effectively - Combine filters for precise results

linear

When & Why to Use This Skill

Use Cases