linear-ticket-analysis

Analyze Linear tickets to detect duplicates and investigate Git history for fixes.

8|2|Updated Jan 15, 2026

Search Tags:#issue management #linear #duplicate detection #codebase investigation #bug triage #ticket analysis

Ready to run

npx skills add https://github.com/bradtaylorsf/alphaagent-team --skill linear-ticket-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: linear-ticket-analysis
Source: https://github.com/bradtaylorsf/alphaagent-team/tree/main/plugins/aai-pm-linear/skills/linear-ticket-analysis
Command: npx skills add https://github.com/bradtaylorsf/alphaagent-team --skill linear-ticket-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of managing Linear tickets by automatically identifying duplicates, checking for relevance, and determining if reported issues have already been fixed in the codebase.

Core Features & Use Cases

Duplicate Detection: Searches for and flags potential duplicate tickets based on keywords, titles, and descriptions.
Codebase Investigation: Scans Git history and codebase for commit messages or code patterns related to ticket issues or feature implementations.
Classification: Recommends actions like closing as duplicate, fixed, outdated, or keeping open based on analysis.
Use Case: When a new bug report comes in, this Skill can quickly check if a similar issue has already been reported and closed as fixed, preventing redundant work.

Quick Start

Analyze the Linear ticket with ID 'PROJ-123' to check for duplicates and fixes.

Frequently Asked Questions about linear-ticket-analysis

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

FAQPage Schema

How do I detect duplicate Linear tickets automatically?▼

You can detect duplicate Linear tickets by running an analysis that searches existing issues for matching keywords, titles, and descriptions. This automated classification recommends closing redundant tickets to streamline bug triage.

Can I check if a reported bug is already fixed in my Git repository?▼

Yes, you can check if a reported bug is fixed by scanning Git history and the codebase for related commit messages or code patterns. This investigation links Linear tickets directly to relevant codebase resolutions.

What is the best way to triage Linear tickets and classify them for action?▼

Triage Linear tickets by analyzing issue details and Git history to classify tickets for appropriate action. The analysis recommends closing tickets as duplicate, fixed, or outdated, or keeping them open for further work.

Do I need a Linear API integration to analyze tickets for duplicates?▼

Yes, Linear API integration is required to access and analyze ticket data for duplicate detection and classification. A Git repository connection is also necessary to investigate codebase history for related fixes.

How do I prevent redundant work when managing duplicate bug reports in Linear?▼

Prevent redundant work by analyzing incoming bug reports to identify if similar issues exist or have already been fixed in the codebase. This automated investigation recommends closing duplicate or resolved tickets immediately.