Help us improve
Share bugs, ideas, or general feedback.
From linear
Manages Linear issues via CLI: list by team/state, view details/comments, create/update title/desc/state/priority/labels/assign, start with git branch, delete.
How this skill is triggered — by the user, by Claude, or both
Slash command
/linear:linear-cliThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Command-line interface for managing Linear issues directly from the terminal.
Share bugs, ideas, or general feedback.
Command-line interface for managing Linear issues directly from the terminal.
# Install (npm)
npm install -g @anthropic/linear
# Authenticate
linear auth
List Issues:
# REQUIRED: Set sort via env var (--sort flag is broken)
LINEAR_ISSUE_SORT=priority linear issue list --team DEV -s unstarted
LINEAR_ISSUE_SORT=priority linear issue list --team DEV -s started
LINEAR_ISSUE_SORT=priority linear issue list --team DEV --all-states
LINEAR_ISSUE_SORT=priority linear issue list --team DEV -A # All assignees
LINEAR_ISSUE_SORT=priority linear issue list --team DEV -U # Unassigned only
LINEAR_ISSUE_SORT=priority linear issue list --team DEV --limit 100 # More results
View Issue:
linear issue view DEV-123 # Terminal view with comments
linear issue view DEV-123 -j # JSON output
linear issue view DEV-123 -w # Open in browser
linear issue view DEV-123 -a # Open in Linear.app
linear issue view --no-comments # Hide comments
Create Issue:
# --team flag is REQUIRED
linear issue create --team DEV -t "Title" -d "Description"
linear issue create --team DEV -t "Title" -p DEV-100 # With parent issue
linear issue create --team DEV -t "Title" -a self # Assign to self
linear issue create --team DEV -t "Title" -s "Todo" # Use workflow state name
linear issue create --team DEV -t "Title" -l "Bug" -l "Urgent" # Multiple labels
linear issue create --team DEV -t "Title" --priority 1 # 1=urgent, 4=low
linear issue create --team DEV -t "Title" --project "Network Agent"
linear issue create --team DEV --start # Start immediately
Update Issue:
linear issue update DEV-123 --state "In Progress"
linear issue update DEV-123 --state "Done" # Close issue
linear issue update DEV-123 -a self # Assign to self
linear issue update DEV-123 -a "username" # Assign to user
linear issue update DEV-123 -p DEV-100 # Set parent
linear issue update DEV-123 --priority 2
linear issue update DEV-123 -l "Label" # Add label
linear issue update DEV-123 -t "New Title"
IMPORTANT: The flag is
--state(or-s), NOT--status.--statusdoes not exist and will error.
Start Working:
linear issue start DEV-123 # Mark in-progress, create git branch
linear issue start DEV-123 -b custom-branch-name
linear issue start DEV-123 -f main # Branch from specific ref
Delete Issue:
linear issue delete DEV-123 # Prompts for confirmation
echo "y" | linear issue delete DEV-123 # Auto-confirm
Get Issue from Branch:
linear issue id # Print issue ID from current branch
linear issue title # Print issue title
linear issue url # Print Linear URL
linear issue describe # Title + Linear-issue trailer
Create PR with Issue:
linear issue pr DEV-123 # Create GitHub PR linked to issue
linear issue comment add DEV-123 -b "Comment text"
linear issue comment list DEV-123
linear issue comment update <commentId> -b "Updated text"
linear project list # List all projects
linear project view <projectId> # View project details
linear team list # List teams
linear team id # Print configured team ID
linear team members # List team members
For issue list - only these enum values work:
| State | Description |
|---|---|
triage | New, needs triage |
backlog | In backlog |
unstarted | Ready to start (default filter) — includes "Todo" |
started | In progress |
completed | Done |
canceled | Canceled |
For issue create and issue update - use your workspace's workflow state names:
| State Name | Description |
|---|---|
"Todo" | Ready to work on |
"In Progress" | Being worked on |
"In Review" | Under review |
"Done" | Completed |
"Canceled" | Canceled |
Use with --priority flag:
| Value | Meaning |
|---|---|
| 1 | Urgent |
| 2 | High |
| 3 | Medium |
| 4 | Low |
LINEAR_ISSUE_SORT=priority linear issue list --team DEV -U # Find unassigned
linear issue start DEV-123 # Claim and create branch
# ... do work ...
linear issue pr # Create PR linked to issue
linear issue create --team DEV -t "Add feature X" --start -a self
for id in DEV-60 DEV-61 DEV-62; do
linear issue update $id -s "In Progress" -a self
done
Config file is unreliable. Use explicit flags and env vars instead:
# Always use --team flag for create/update/list
# Always use LINEAR_ISSUE_SORT env var for list (--sort flag is broken)
LINEAR_ISSUE_SORT=priority linear issue list --team DEV -s unstarted
Get team key with linear team list (DEV, SAL, etc.).
TEAM-123 (e.g., DEV-123)-a self to assign to yourself--no-interactive skips prompts for scriptingjq for JSON: linear issue view DEV-123 -j | jq .titleSee references/api-patterns.md for advanced GraphQL API usage patterns.
npx claudepluginhub crouton-labs/crouton-kit --plugin linearManages Linear issues from the command line with git/jj integration. Supports issue CRUD, comments, teams, projects, and project updates via the linear CLI.
Manages Linear.app issues via Linearis CLI with JSON output: create, read, update, search issues; list teams/projects/cycles/labels/users; add comments.
Manages Linear issues, projects, and teams using MCP tools, linear CLI, and GraphQL API. Create, update, query issues; handle labels, status, references, and backlogs.