linear-workspace

Apply the same change to many Linear issues at once. Dry-run by default.

Audit Linear issues for problems (missing labels, stale, duplicates, wrong state, orphaned, unactionable) and propose fixes

Run the curator — collect signals from configured signal sources and report

List Linear issues assigned to you, grouped by state

Search Linear issues by keyword, team, assignee, or state

Create Linear issues from user descriptions. NOT for URLs — use linear-url-to-issues for that. Use when: "create issue", "new ticket", "log bug", "add task", "file issue", "report bug", "make ticket", "make issue", "add to linear", "create task", "new issue", "make new issue", "make new ticket", "make new linear ticket", "create linear ticket", "new linear issue", "new linear ticket", "open ticket", "open issue". <example>create issue for dark mode feature</example> <example>log bug: authentication not working</example> <example>new ticket for API optimization</example> <example>make new linear ticket: Stripe webhook retry logic</example> <example>add task to implement SSO</example>

Validate Done Criteria of an issue against its linked PR's diff and post a verdict comment. Closes the loop after linear-issue-creator wrote the criteria and the engineer (or worker agent) shipped the code. Use when: "review issue", "validate done criteria", "check issue completion", "review ENG-XXX", "is ENG-XXX done?", "verify the work on ENG-XXX". <example>review ENG-405</example> <example>validate done criteria of ENG-200</example> <example>check whether ENG-300 is actually done</example> <example>verify the work on ENG-645</example>

Update existing Linear issues. ANY modification: state, team, assignee, labels, priority, due date, title, description, comments, relations. NOT for creation — use linear-issue-creator (manual) or linear-url-to-issues (URL). Use when: "update issue", "move issue", "reassign", "change state", "change priority", "add label", "remove label", "add comment", "change team", "set due date", "edit issue", "close issue", "mark done", "link issues", "relate issues", "mark as duplicate", "mark as blocking", "add relation", "remove relation", "list relations". <example>move ENG-103 to Engineering team</example> <example>reassign ENG-405 to Alice</example> <example>change ENG-200 priority to urgent</example> <example>add comment to SEC-50 about the fix</example> <example>close ENG-300, it's done</example> <example>update the description of ENG-103</example> <example>link ENG-645 as related to ENG-555 and ENG-565</example> <example>mark ENG-300 as duplicate of ENG-295</example>

Autonomous Linear hygiene agent. Reads every open issue across configured teams, validates true state against signals from the configured signal_sources (commits in configured repos, GitHub PRs, Slack messages, Linear cross-references, plus any external_command sources), then auto-applies HIGH-confidence state changes, DMs the assignee in Slack for MEDIUM-confidence ambiguity, and reports LOW-confidence stale issues to an allow-listed channel. Used in conjunction with the `elnora-linear curator-run` command. Use when: "run linear curator", "validate linear issues", "linear hygiene", "review linear state", "check stale issues". <example>run linear curator</example> <example>which linear issues are actually done?</example> <example>linear hygiene check</example>

Extract actionable Linear issues from URLs (articles, blogs, designs, docs). Parallel-safe — dispatch one agent per URL when processing multiple. NOT for manual creation — use linear-issue-creator. Use when: "create issues from URL", "turn this article into tasks", "implement this design", "make issues from blog post", "extract tasks from", "read and create issues", "issues from this link", "create issues from this", "make tickets from". <example>create issues from this article about AI safety: <url></example> <example>turn this design into Linear tasks: <figma-link></example> <example>read this blog and make actionable issues: <url></example> <example>implement ideas from this URL</example>

Linear issue management — routes work to specialized agents and slash commands. Use when: creating, updating, searching, bulk-editing, cleaning up, syncing Linear. TRIGGERS: "linear", "ticket", "issue", "create issue", "update issue", "search issues", "my issues", "bulk", "cleanup", "sync", "log bug", "file issue", "report bug", "new ticket", "add task", "open ticket", "open issue", "throw this in linear", "track this in linear", "capture as issue", "put on the backlog".