linear-triage

Solid

Triage Linear issues using bounded searches, duplicate checks, explicit team and project scope, and evidence-backed priority recommendations.

AI & Automation 6,691 stars 1288 forks Updated yesterday NOASSERTION

Install

View on GitHub

Quality Score: 84/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
28
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Linear Triage 1. Resolve the team and project before changing an issue. 2. Search for possible duplicates and related work using the reported behavior, component, and error text. 3. Separate confirmed facts, reproduction details, impact, and missing information. 4. Recommend priority, labels, status, and owner only from the team's current conventions and available evidence. 5. Preview material changes before applying them, then re-read the issue. Never invent a cycle, label, project, estimate, or assignee. Keep broad issue searches bounded.

Details

Author
Devin-AXIS
Repository
Devin-AXIS/iPolloWork
Created
1 years ago
Last Updated
yesterday
Language
TypeScript
License
NOASSERTION

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category