linear-usage

Standardize Linear issue creation with templates, labels, and triage workflows.

1.0k|91|Updated Jul 9, 2025

Search Tags:#templates #linear #triage #sprint #labels #issue-tracking #project-management

Ready to run

npx skills add https://github.com/fcakyon/claude-codex-settings --skill linear-usage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: linear-usage
Source: https://github.com/fcakyon/claude-codex-settings/tree/main/plugins/linear-tools/skills/linear-usage
Command: npx skills add https://github.com/fcakyon/claude-codex-settings --skill linear-usage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides guidelines for writing clear Linear issues, organizing sprint planning, and maintaining a healthy Linear workflow to improve delivery speed and reduce context switching.

Core Features & Use Cases

Issue Writing Guidelines: Clear titles, structured descriptions, and templates for bugs and feature requests.
Templates: Provide ready-to-use templates for Bug report and Feature request.
Label Taxonomy: Type and area labels, and recommended planning labels.
Priority & Estimation: P0-P3, relative sizing, and planning tips.
Cycle & Planning: Sprint cycle practices, capacity planning, backlogs.
GitHub Integration: Linking PRs to Linear issues and automatic status updates.

Quick Start

Create a new Linear issue with title "Add export to CSV" and use bug report template to describe the issue; add labels following the taxonomy; set priority accordingly.

Frequently Asked Questions about linear-usage

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

FAQPage Schema

How do I write better Linear issues for bug reports and feature requests?▼

Use clear titles, structured descriptions, and standardized templates for bugs and features. The Skill provides ready-to-use templates that specify functional requirements, acceptance criteria, and consistent formatting to reduce ambiguity and context switching during triage and planning.

What's the best way to organize labels and priority in Linear for sprint planning?▼

Apply a label taxonomy with Type and Area labels, then set priorities using P0-P3 levels paired with relative sizing estimates. This structure streamlines sprint cycles, capacity planning, and backlogs while keeping workflows consistent across the team.

Can I link GitHub pull requests to Linear issues automatically?▼

Yes. The Skill covers GitHub integration patterns that link PRs to Linear issues with automatic status updates, reducing manual synchronization and keeping development velocity visible across both platforms.

How do I reduce context switching when triaging Linear issues?▼

Triage workflows using standardized templates, consistent label taxonomy, and clear acceptance criteria minimize the information-gathering overhead per issue. Combined with sprint planning guidelines, this maintains delivery speed and team focus.

What label structure should I use for organizing Linear issues?▼

Implement Type labels (bug, feature) and Area labels (component-based), supplemented by planning labels for priority and cycle assignment. This taxonomy keeps issues discoverable and reduces overhead during sprint planning and backlog refinement.