linear-issues-read
List and get Linear issues via CLI (read-only operations)
When & Why to Use This Skill
The linear-issues-read skill is a specialized CLI tool designed for Claude agents to interact with the Linear project management platform. It enables efficient, read-only access to issue tracking data, allowing users to list, filter, and retrieve detailed information about tasks, projects, and team progress directly within their workflow. By streamlining the data retrieval process from Linear, it enhances project visibility and provides essential context for AI-driven task management and reporting.
Use Cases
- Real-time Task Tracking: Quickly list all 'In Progress' issues for a specific engineering team to monitor current sprint velocity and identify potential bottlenecks.
- Contextual Development Support: Retrieve full issue descriptions and metadata (e.g., ENG-123) to provide an AI agent with the necessary background for coding, debugging, or documentation tasks.
- Automated Status Reporting: Filter issues by project or assignee to generate structured data for weekly stand-ups, stakeholder updates, or project health dashboards.
- Workload Analysis: Use the assignee and status filters to review the distribution of tasks across team members and ensure balanced resource allocation.
| name | linear-issues-read |
|---|---|
| description | List and get Linear issues via CLI (read-only operations) |
| version | 1.0.0 |
| license | MIT |
| compatibility | opencode |
Overview
CLI tools for reading Linear issues. Requires LINEAR_API_KEY set in <git-root>/.env or exported in the environment.
Prerequisites
- bun runtime installed
LINEAR_API_KEYset in<git-root>/.envor environment
Commands
List Issues
bun .opencode/skill/linear-issues-read/list-issues.js [options]
Options:
--team <name>- Filter by team (e.g., Engineering, Infrastructure, Product)--project <name>- Filter by project name--assignee <name>- Filter by assignee name--status <status>- Filter by status (e.g., "In Progress", "Todo", "Done")--limit <n>- Max results (default: 25)--json- Output as JSON
Examples:
bun .opencode/skill/linear-issues-read/list-issues.js --team Engineering --limit 10
bun .opencode/skill/linear-issues-read/list-issues.js --assignee "George Washington" --status "In Progress"
bun .opencode/skill/linear-issues-read/list-issues.js --project "Mount Vernon" --json
Get Issue
bun .opencode/skill/linear-issues-read/get-issue.js <issue-id> [options]
Arguments:
issue-id- Issue identifier (e.g., ENG-123) or UUID
Options:
--json- Output as JSON
Examples:
bun .opencode/skill/linear-issues-read/get-issue.js ENG-123
bun .opencode/skill/linear-issues-read/get-issue.js ENG-123 --json
Output Behavior
- Command output is displayed directly to the user in the terminal
- Do not re-summarize or reformat table output - the user can already see it
- Only provide additional commentary if the user explicitly requests analysis, filtering, or summarization
- When using
--jsonoutput with tools likejq, the processed results are already visible to the user
Notes
- Team, user, and label names are resolved automatically (case-insensitive)