linear-triage

Verify and update Linear ticket statuses against GitHub PR states.

3|1|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/OmniNode-ai/omniclaude --skill linear-triage-omninode-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linear-triage
Source: https://github.com/OmniNode-ai/omniclaude/tree/main/plugins/onex/skills/linear-triage
Command: npx skills add https://github.com/OmniNode-ai/omniclaude --skill linear-triage-omninode-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of verifying the status of Linear tickets against their corresponding GitHub Pull Requests, ensuring that tickets are accurately updated and that no work falls through the cracks.

Core Features & Use Cases

  • Automated Status Verification: Compares Linear ticket status with PR merge/close status.
  • Ticket Cleanup: Automatically marks Linear tickets as 'Done' when their associated PR is merged.
  • Stale Ticket Identification: Flags tickets that have not been updated recently or whose PRs were closed without merging.
  • Orphan Ticket Detection: Identifies tickets without a parent epic, suggesting potential epic groupings.
  • Epic Completion Check: Automatically closes epics once all their child tickets are completed.

Quick Start

Run the linear-triage skill to scan and update your Linear tickets.

Frequently Asked Questions about linear-triage

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

FAQPage Schema
How do I automate Linear ticket status updates from GitHub PR merges?

Automate Linear ticket status updates by verifying ticket states against GitHub PR merges. The skill identifies completed tickets, marks them as 'Done' when PRs merge, and reduces manual project tracking efforts.

What is the best way to find stale Linear tickets linked to closed GitHub PRs?

Identify stale Linear tickets by flagging entries with closed but unmerged GitHub Pull Requests. The skill scans for outdated tickets, highlighting work that stalled without completion so nothing falls through the cracks.

Can I automatically detect Linear tickets without a parent epic?

Detect orphan Linear tickets without a parent epic by scanning your project workspace. The skill identifies unassigned tickets and suggests potential epic groupings to maintain proper project hierarchy.

How do I close Linear epics when all child tickets are completed?

Close Linear epics automatically once all child tickets reach completion. The skill performs epic completion checks by verifying every associated ticket status before safely closing the parent epic.

Do I need to connect both Linear and GitHub APIs to automate ticket triage?

You need both Linear and GitHub APIs connected to automate ticket triage. The skill integrates with both platforms to verify PR states, update ticket statuses, and ensure accurate project tracking.

Why does my Linear ticket remain open after the GitHub PR is merged?

Linear tickets remain open after GitHub PR merges due to missed manual updates. The skill solves this by automatically marking Linear tickets as 'Done' when their associated PRs are successfully merged.