issue-analyzer

Analyze Linear, GitHub, and Jira issues to generate implementation plan files.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/lutzcc1/claude-skills --skill issue-analyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-analyzer
Source: https://github.com/lutzcc1/claude-skills/tree/main/project/issue-analyzer
Command: npx skills add https://github.com/lutzcc1/claude-skills --skill issue-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes issues from any tracking system (Linear, GitHub, Jira) in the context of the Sprout Rails codebase. It gathers all necessary context (issue details, comments, codebase patterns) and then invokes the implementation-plan-writer skill to create a standardized plan file.

Core Features & Use Cases

  • Cross-tracker issue analysis: fetches issue data (title, description, status, priority, labels) and comments from Linear, GitHub, Jira.
  • Context extraction: collects relevant codebase patterns and related objects to inform implementation.
  • Branch planning guidance: outlines a safe, consistent branch strategy aligned with the issue.
  • Codebase exploration: performs targeted searches to identify related components, services, and tests to inform the plan.
  • Plan generation: delegates plan creation to the implementation-plan-writer skill to produce an <ISSUE-ID>-IMPLEMENTATION-PLAN.md.

Quick Start

Provide an issue URL or ID (Linear, GitHub, or Jira). The Skill will detect the tracker, fetch issue details, assemble context, and invoke the implementation-plan-writer to generate the implementation plan file.

Frequently Asked Questions about issue-analyzer

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

FAQPage Schema
How do I generate an implementation plan from a Linear, GitHub, or Jira issue?

Implementation plan generation works by detecting the issue tracker from a provided URL or ID, fetching title and description data, extracting codebase context, and invoking a writer process to output a structured markdown plan file.

What context does issue analysis use to prepare an actionable implementation plan?

Issue analysis uses contextual signals including the issue title, description, status, priority, labels, comments, and targeted codebase searches to identify related components, services, and tests for the implementation plan.

Can I use issue analysis to plan a branching strategy for my codebase?

Issue analysis provides branching strategy guidance by outlining safe and consistent branch plans aligned with the specific issue and codebase context during the implementation plan generation process.

Does the implementation plan writer support cross-tracker issue sources like Linear and Jira?

Cross-tracker issue sources including Linear, GitHub, and Jira are supported; the system detects the tracker from the input, fetches relevant issue data, and assembles context before generating the implementation plan file.

What is the output format when turning an issue into an actionable implementation plan?

The output format is a standardized markdown file named with the issue ID followed by IMPLEMENTATION-PLAN.md, generated by delegating the assembled issue context and codebase relations to the plan writer.

Do I need to provide a specific tracker URL to start the issue analysis process?

Providing an issue URL or ID from Linear, GitHub, or Jira is required to start the issue analysis process, allowing the system to detect the tracker, fetch data, and extract codebase patterns for the plan.