issue-tracker-linear

Manage Linear issue lifecycle, project boards, and automated PR-linked closures.

1|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/eric-sabe/engsys --skill issue-tracker-linear
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-tracker-linear
Source: https://github.com/eric-sabe/engsys/tree/main/stacks/tooling/issue-tracker-linear/skills/issue-tracker-linear
Command: npx skills add https://github.com/eric-sabe/engsys --skill issue-tracker-linear

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually managing Linear issues, projects, milestones, and linking pull requests to work items is time-consuming and error-prone, especially for engineering teams running sprint-based workflows.

Core Features & Use Cases

  • Full Issue Lifecycle Management: Create, list, retrieve, update, comment on, and close Linear issues using consistent operation names shared across issue tracker backends.
  • Project (Board) Administration: Create Linear projects as boards, organize issues by phase via milestones, set priority and assignees, and query board status grouped by work phase.
  • Automated PR Linking: Close Linear issues automatically when corresponding GitHub PRs merge, using Linear's native magic words without extra tooling.
  • Use Case: An engineering team using Linear for sprint tracking can use this skill to file bug reports, organize work by phase and priority, and automatically close issues when their fixes are merged, all without manual updates to the issue tracker.

Quick Start

Use the issue-tracker-linear skill to create a new high-priority bug report for the mobile app login flow, assign it to the frontend squad, and add it to the current Q4 sprint board.

Frequently Asked Questions about issue-tracker-linear

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

FAQPage Schema
How do I automatically close Linear issues when a GitHub pull request merges?

You can automatically close Linear issues by linking merged GitHub pull requests to work items using Linear's native GitHub integration magic words. This eliminates the need for extra tooling or manual updates to your issue tracker.

What's the best way to organize a Linear sprint board by work phase and priority?

Organize a Linear sprint board by creating projects as boards, setting priority levels and assignees, and grouping issue status by milestones to track distinct work phases across the sprint.

Can I manage the full Linear issue lifecycle without manual administrative work?

Yes, you can manage the full Linear issue lifecycle by creating, listing, retrieving, updating, commenting on, and closing issues through consistent operation names to eliminate manual project board management tasks.

Does Linear's native GitHub integration support automated PR linking for bug reports?

Yes, Linear's native GitHub integration supports automated PR linking. Engineering teams can file bug reports, assign them to squads, and automatically close issues when corresponding fixes are merged.

How do I create a high-priority bug report in Linear and assign it to a sprint board?

Create a high-priority bug report in Linear by filing the issue, assigning it to the appropriate squad, and adding it to the current sprint board project for phase-based milestone tracking.

Are there limitations to using Linear magic words for automated issue closure?

Automated issue closure via Linear magic words is limited to workflows using Linear's native GitHub integration, meaning it applies specifically to merged pull requests rather than external or manual workflow triggers.