linear_skill

This skill lets your AI agent read, create, update, and triage Linear issues via the GraphQL API and a bash CLI.

Shell

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill mikeygonz/skills --skill linear

SKILL.md8.9 KB

Overview

This skill lets the AI agent manage Linear tickets via the Linear GraphQL API and a lightweight bash CLI wrapper. Use it to read, create, update, comment on, and triage issues without leaving the conversation. It includes commands for team, project, and standup views and supports branch name generation for git workflows.

How this skill works

The skill calls Linear's GraphQL API using an environment-mounted LINEAR_API_KEY and exposes common operations via a bash script (linear.sh). The agent fetches full issue details before acting, can download ticket images and follow linked Notion pages for extra context, and runs create/update commands through the CLI wrapper. It can also integrate with an MCP server when available for richer tooling.

When to use it

User mentions a Linear ticket ID (e.g., "ENG-123").
User asks to see their board, assigned issues, or a standup summary ("what's on my board", "show my tickets").
User requests creating a new issue or drafting a ticket description.
User asks to change status, priority, assignment, or add a comment to a ticket.
User needs branch name suggestions or a quick team/project issue listing.

Best practices

Always fetch full issue details before making changes to avoid stale data.
Check ticket descriptions for images and download them; Linear image URLs expire so refetch if you get a 401.
Draft ticket edits or comments and ask for user approval before posting any write operations.
Use the CLI's branch command to generate consistent git branch names from ticket IDs.
Follow the provided issue templates (feature, bug, spike, polish) to keep titles short and actionable.

Example use cases

Show my open issues: run my-issues and summarize todos and in-progress work for a standup.
Create a new bug report: create <TEAM_KEY> "title" "description" with the recommended bug template.
Move a ticket to In Progress: status ENG-123 progress and confirm with the user before updating.
Add a comment to a ticket after drafting: comment ENG-123 "text" (agent drafts then requests approval).
Fetch full ticket plus linked Notion research and images to assemble design context for an implementation plan.

FAQ

You must set the LINEAR_API_KEY environment variable and have curl and jq installed. Optionally set LINEAR_DEFAULT_TEAM for convenience.

Can the agent fetch images from tickets?

Yes. The agent looks for markdown image URLs in descriptions and downloads them. Because Linear image URLs expire, refetch the ticket if downloads fail with 401.

Will the agent post changes without asking?

No. The agent will draft changes or comments and request explicit user approval before performing write operations like create, update, assign, or comment.