From aai-pm-linear
Analyzes Linear tickets to detect duplicates, check relevance, verify fixes via git history/GitHub PRs/codebase searches, and recommend classifications like CLOSE_DUPLICATE or CLOSE_FIXED.
npx claudepluginhub bradtaylorsf/alphaagent-teamThis skill uses the workspace's default tool permissions.
Methodology for analyzing Linear tickets to find duplicates, check relevance, and determine if issues have been fixed.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Methodology for analyzing Linear tickets to find duplicates, check relevance, and determine if issues have been fixed.
From each Linear ticket, identify:
Search for potential duplicates:
mcp__claude_ai_Linear__list_issues with:
query="{keywords}"
team="{team_key}"
limit=20
Duplicate indicators:
NOT duplicates:
For bugs, search for fixes:
# Search git history for ticket references
git log --oneline --all --since="2025-01-01" --grep="{ticket_id}"
# Search for keyword-related commits
git log --oneline --all --since="2025-01-01" --grep="{keyword}"
# Check if error pattern still exists
rg "{error_pattern}" --type ts
For features, check implementation status:
# Search for component/feature implementation
rg "{feature_keyword}" --type ts
# Check for related PRs
gh pr list --state merged \
--search "{ticket_id}" --json number,title,mergedAt
When closing tickets, use appropriate status:
Done - For fixed/implemented issuesCanceled - For duplicates, outdated, won't fixFor each analyzed ticket:
TICKET: {ticket_id}
TITLE: {title}
AGE: {months} months
STATUS: {current_status}
LABELS: {labels}
ANALYSIS:
- Duplicate check: {result}
- Codebase check: {result}
- Relevance: {assessment}
RECOMMENDATION: {classification}
REASON: {brief explanation}
ACTION: {what to do}
Used by:
linear-ticket-triager agent/linear-triage command