issue

Investigate product issues and create implementation-ready Linear tickets from codebase context.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/davidsolheim/skills --skill issue-davidsolheim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue
Source: https://github.com/davidsolheim/skills/tree/main/issue
Command: npx skills add https://github.com/davidsolheim/skills --skill issue-davidsolheim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the friction of manual ticket creation by automating the investigation of bugs or feature requests and generating implementation-ready Linear issues directly from your codebase context.

Core Features & Use Cases

  • Automated Context Gathering: Deeply scans your repository to map routes, API endpoints, and relevant code symbols to provide a complete technical picture for the implementer.
  • Intelligent Linear Integration: Automatically resolves the correct team and project, checks for duplicates, and drafts detailed tickets with acceptance criteria and drift-check anchors.
  • Use Case: When a user reports a bug, use this skill to instantly generate a high-quality Linear ticket that includes the suspected root cause, relevant file paths, and verification steps, allowing developers to start coding immediately.

Quick Start

Use the issue skill to investigate the reported checkout failure and create a detailed Linear ticket for the engineering team.

Frequently Asked Questions about issue

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

FAQPage Schema
How do I automate Linear ticket creation from codebase analysis?

Automate Linear ticket creation by scanning your repository to map routes, API endpoints, and relevant code symbols, then generating implementation-ready issues with acceptance criteria and verification steps directly from your codebase context.

What is automated code-context mapping for bug reporting?

Automated code-context mapping for bug reporting deeply scans your repository to identify suspected root causes and relevant file paths, providing a complete technical picture to include in detailed Linear issues for developers.

Do I need Linear API access to generate implementation-ready issues from my repository?

Yes, you need Linear API access to generate implementation-ready issues. The integration requires API access and repository-level documentation to automatically resolve the correct team and project metadata for each ticket.

Can I check for duplicate Linear issues automatically when filing bug reports?

You can check for duplicate Linear issues automatically during the ticket creation process. The workflow intelligently resolves team and project metadata, checks for existing duplicates, and drafts detailed tickets to prevent redundant bug reports.

What's the best way to include suspected root cause and file paths in a Linear ticket?

The best way to include suspected root cause and file paths in a Linear ticket is using automated codebase investigation, which scans your repository and drafts detailed tickets with drift-check anchors and verification steps for immediate developer use.