linear-issues

Fetch Linear issues and export structured JSON for debugging context.

10|2|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/eveld/claude --skill linear-issues-eveld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linear-issues
Source: https://github.com/eveld/claude/tree/main/skills/linear-issues
Command: npx skills add https://github.com/eveld/claude --skill linear-issues-eveld

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Linear issues contain critical debugging context that is often scattered across tickets. This skill consolidates issue data (title, description, state, priority, and comments) from Linear to provide a centralized source of truth for debugging investigations.

Core Features & Use Cases

  • Issue discovery: List, search, and read issues by ID or query to understand scope and impact.
  • Context extraction: Retrieve titles, descriptions, states, priorities, and comments to guide triage and reproduction steps.
  • Export & analysis: Produce structured JSON outputs for analysis, dashboards, or chain-of-thought workflows. Use Case: Investigate ENG-1234 to gather context, reproduction steps, and related issues for faster debugging.

Quick Start

Fetch issue ENG-1234 from Linear and load its details into your context.

Frequently Asked Questions about linear-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fetch Linear issues to gather debugging context?

Fetch Linear issues by listing, searching, or reading tickets by ID to consolidate titles, descriptions, states, priorities, and comments into a centralized context for debugging investigations.

What debugging context can I extract from Linear issues?

Linear issues provide titles, descriptions, states, priorities, and comments to guide triage, identify reproduction steps, and understand the scope and impact of software defects.

Can I export Linear issue data for analysis and dashboards?

Linear issue data can be exported as structured JSON outputs, enabling integration with downstream tools, dashboards, and chain-of-thought workflows for debugging analysis.

Does this approach work for triaging issues across multiple Linear tickets?

Linear issue discovery supports searching and reading tickets by query or ID, allowing software engineers to quickly gather and interpret scattered data for triage and planning.

What is the best way to investigate a specific Linear ticket for reproduction steps?

Retrieve the specific Linear ticket by its ID to load its details, including comments and descriptions, directly into your context for faster debugging and reproduction.

Are there limitations when using Linear issues for debugging?

Linear issue debugging context relies on the data available in tickets; if reproduction steps or related issues are not documented in the comments or descriptions, the consolidated context will be incomplete.