linear-ticket-analysis

Included with Lifetime

$97 forever

Methodology for analyzing Linear tickets to find duplicates, check relevance, and determine if issues have been fixed.

General

What this skill does


# Linear Ticket Analysis Skill

Methodology for analyzing Linear tickets to find duplicates, check relevance, and determine if issues have been fixed.

## Analysis Steps

### 1. Extract Key Information

From each Linear ticket, identify:
- **Title and description** - Core problem statement
- **Keywords** - Component names, error messages, feature names
- **Labels** - Bug, Feature, product area
- **Created date** - Age of ticket
- **Status** - Current workflow state
- **Related tickets** - Already linked duplicates/relations
- **GitHub links** - Associated GitHub issues

### 2. Duplicate Detection

Search for potential duplicates:

```
mcp__claude_ai_Linear__list_issues with:
  query="{keywords}"
  team="{team_key}"
  limit=20
```

**Duplicate indicators:**
- Same error message or component
- Similar title (>70% word overlap)
- Same root cause described differently
- Created within days of each other
- Same reporter

**NOT duplicates:**
- Related but distinct issues
- Same component, different bugs
- Follow-up issues with new scope

### 3. Codebase Investigation

For bugs, search for fixes:

```bash
# 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:

```bash
# 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
```

### 4. Classification Criteria

#### CLOSE_DUPLICATE
- Another ticket covers same issue
- Original ticket is more complete/active
- Link to original before closing

#### CLOSE_FIXED
- Found PR/commit addressing the issue
- Error pattern no longer in codebase
- Feature has been implemented

#### CLOSE_OUTDATED
- Ticket is 6+ months old with no activity
- Component/feature no longer exists
- Requirements have fundamentally changed

#### KEEP_OPEN
- Issue still exists in codebase
- Feature not yet implemented
- Clear path to resolution

#### NEEDS_CLARIFICATION
- Insufficient detail to investigate
- Unclear requirements
- Add comment requesting more info

### 5. Status Transitions

When closing tickets, use appropriate status:
- `Done` - For fixed/implemented issues
- `Canceled` - For duplicates, outdated, won't fix

## Output Format

For 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}
```

## Integration

Used by:
- `linear-ticket-triager` agent
- `/linear-triage` command

Files: 1

Size: 3.0 KB

Complexity: 11/100

Category: General

Source: https://github.com/bradtaylorsf/alphaagent-team/tree/main/plugins/aai-pm-linear/skills/linear-ticket-analysis

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts