update-issues

Find and update Linear issues by applying labels, metadata, and blocking relationships.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/jamesc/skills --skill update-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-issues
Source: https://github.com/jamesc/skills/tree/main/skills/update-issues
Command: npx skills add https://github.com/jamesc/skills --skill update-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the tedious process of finding and updating Linear issues, ensuring they have correct labels, assignments, and metadata, saving significant project management time.

Core Features & Use Cases

  • Automated Labeling: Automatically applies necessary labels (e.g., agent-ready, Feature, stdlib, M) based on issue content and predefined rules.
  • Metadata Updates: Updates issue fields like assignee, priority, and state.
  • Relationship Management: Sets up blocking relationships between issues.
  • Use Case: When you receive a batch of new issues, you can run this skill with a command like /update-issues for ones with no labels to automatically categorize and prepare them for development.

Quick Start

Use the update-issues skill to find and label all issues that are missing an agent-ready label.

Frequently Asked Questions about update-issues

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

FAQPage Schema
How do I automatically apply missing labels to Linear issues?

To automate Linear issue labeling, this skill parses issue content and user-defined criteria to infer missing metadata like agent-state, item-area, issue-type, and size, then applies the correct labels via batch GraphQL mutations.

Can I batch update Linear issue metadata like assignee and priority?

Yes, you can batch update Linear issue metadata such as assignee, priority, and state by running CLI commands with user-defined search criteria to find and modify matching issues efficiently.

How do I set up blocking relationships between Linear issues?

You can establish blocking relationships between Linear issues by defining criteria for the skill to search and match relevant issues, then applying the relationships through automated GraphQL mutations.

Does this Linear issue automation tool require any external dependencies?

No external dependencies are required to run this Linear issue automation skill, as it operates independently using built-in scripts and references to execute GraphQL mutations and CLI commands.

What is the best way to categorize untagged Linear issues for development?

The best way to categorize untagged Linear issues is using automated labeling rules that infer metadata from issue content, applying standard size and feature labels to prepare them for development.

How does automated issue labeling infer the correct size and type?

Automated issue labeling infers the correct size and type by parsing predefined rules and issue content, intelligently mapping the data to standard labels like size 'M' or issue type 'Feature'.