linear-issues

Automates Linear issue listing, creating, updating, assigning, commenting, labeling via linear-cli with ndjson output and dry-run/id-only conventions.

Updated Jul 11, 2022
One-click install
npx skills add https://github.com/kvnxiao/.dotfiles --skill linear-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linear-issues
Source: https://github.com/kvnxiao/.dotfiles/tree/main/claude/skills/linear-issues
Command: npx skills add https://github.com/kvnxiao/.dotfiles --skill linear-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the repetitive management of Linear issues using the linear-cli, reducing time spent on manual updates and status changes.

Core Features & Use Cases

  • List, create, update, start/stop work, assign, and comment on Linear issues using the linear-cli.
  • Set priorities and labels, filter by team, status, or assignee to keep backlogs organized.
  • Use Case: When coordinating a cross-functional sprint, automatically fetch and modify issues to reflect current priorities.

Quick Start

Install and authenticate linear-cli, then try:

  • linear i list --output ndjson
  • linear i create "New task" -t Engineering -p 2
  • linear i update LIN-123 -s "In Progress"

Frequently Asked Questions about linear-issues

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

FAQPage Schema
How do I automate Linear issues management from the command line?

You can automate Linear issues management by using the linear-cli tool to list, create, update, start, stop, assign, comment, and label issues directly from your terminal.

Do I need to install linear-cli before managing Linear issues?

Yes, the linear-cli tool is required for all operations. You must install and authenticate it first to execute any commands for creating or updating Linear issues.

Can I list and filter Linear issues by team or status?

Yes, listing and filtering Linear issues by team, status, or assignee is supported. Query results use the --output ndjson format to keep backlogs organized.

How do I create and update Linear issues for a sprint?

Use linear-cli commands like create with a title and priority, then update the issue by ID to change its status to In Progress during your engineering workflows.

What's the best way to bulk update Linear issue statuses?

The best way to update Linear issues is by using ID-based actions with the linear-cli. It supports dry-run and id-only conventions to safely apply status changes across your backlog.

Are there limitations when using linear-cli for task management?

Operations are limited to ID-based actions within the linear-cli scope, meaning you must reference existing issue identifiers directly when updating, assigning, or commenting on Linear issues.