@elnora-ai/linear 1.0.0

package/.claude-plugin/marketplace.json

@@ -0,0 +1,19 @@
+{
+  "name": "elnora-linear",
+  "description": "Linear workspace for Claude Code — single-plugin marketplace.",
+  "owner": {
+    "name": "Elnora AI",
+    "email": "opensource@elnora.ai",
+    "url": "https://github.com/Elnora-AI"
+  },
+  "plugins": [
+    {
+      "name": "linear-workspace",
+      "description": "Linear issue management for Claude Code — search, bulk operations, intelligent agents, config-driven curator.",
+      "source": "./",
+      "version": "0.0.0",
+      "category": "productivity",
+      "tags": ["linear", "issue-tracker", "workflow", "automation"]
+    }
+  ]
+}

package/.claude-plugin/plugin.json

@@ -0,0 +1,19 @@
+{
+  "name": "linear-workspace",
+  "version": "0.0.0",
+  "description": "Linear issue management for Claude Code — search, bulk operations, intelligent agents, config-driven curator. Backed by the elnora-linear CLI.",
+  "author": {
+    "name": "Elnora AI",
+    "email": "opensource@elnora.ai",
+    "url": "https://github.com/Elnora-AI"
+  },
+  "homepage": "https://github.com/Elnora-AI/elnora-linear",
+  "repository": "https://github.com/Elnora-AI/elnora-linear",
+  "license": "Apache-2.0",
+  "keywords": [
+    "linear",
+    "issue-tracker",
+    "workflow",
+    "automation"
+  ]
+}

package/CHANGELOG.md

@@ -0,0 +1,29 @@
+# Changelog
+
+## 1.0.0 (2026-05-16)
+
+
+### Features
+
+* agents + slash commands + linear-workspace skill ([#13](https://github.com/Elnora-AI/elnora-linear/issues/13)) ([cf350ac](https://github.com/Elnora-AI/elnora-linear/commit/cf350ace534de6a6658b9b2c801a42bbf9cc8ae0))
+* bulk + cleanup commands with dry-run safety ([#10](https://github.com/Elnora-AI/elnora-linear/issues/10)) ([1b9e332](https://github.com/Elnora-AI/elnora-linear/commit/1b9e33228dad92e78b732cf1d12a2226c2cd4c02))
+* **ci:** add release.yml — publish to npm via OIDC on GitHub release ([#15](https://github.com/Elnora-AI/elnora-linear/issues/15)) ([cb52372](https://github.com/Elnora-AI/elnora-linear/commit/cb52372d97d7088146edbc5d46937c97bd3bde5c))
+* config layer — types, loader, schema validation, tests ([#8](https://github.com/Elnora-AI/elnora-linear/issues/8)) ([40c4f7a](https://github.com/Elnora-AI/elnora-linear/commit/40c4f7a3f8cc8d990833c8eac1f7c09f6929a140))
+* curator-run + signal-source registry + external_command source ([#12](https://github.com/Elnora-AI/elnora-linear/issues/12)) ([6fccb47](https://github.com/Elnora-AI/elnora-linear/commit/6fccb476acf7a6904d8e69166fd8e736a84c4020))
+* scaffold reference data — schemas, placeholders, examples, no-populated-references CI check ([#7](https://github.com/Elnora-AI/elnora-linear/issues/7)) ([e2dcc15](https://github.com/Elnora-AI/elnora-linear/commit/e2dcc15c7ac3ea6b67527f23037af3ee22491a1c))
+* search + my-issues commands, Linear client, API key auth, output formatter ([#9](https://github.com/Elnora-AI/elnora-linear/issues/9)) ([f0893e4](https://github.com/Elnora-AI/elnora-linear/commit/f0893e47f1ee8ec9e04210369a6a23be7271973c))
+* sync command — auto-discover teams/projects/users/workflows from Linear ([#11](https://github.com/Elnora-AI/elnora-linear/issues/11)) ([9721027](https://github.com/Elnora-AI/elnora-linear/commit/9721027712a36af321c7609c7c0b36d545849295))
+
+
+### Bug Fixes
+
+* **ci:** switch release.yml from OIDC to NPM_TOKEN ([#18](https://github.com/Elnora-AI/elnora-linear/issues/18)) ([b67bcde](https://github.com/Elnora-AI/elnora-linear/commit/b67bcde6b59ba8919174d82c25494a70a7a97ce1))
+* **ci:** use org-level RELEASE_BOT_PAT for Release Please ([#14](https://github.com/Elnora-AI/elnora-linear/issues/14)) ([a83d6db](https://github.com/Elnora-AI/elnora-linear/commit/a83d6db75db141e2a6f81aff46574fac9f87628e))
+* **ci:** use per-repo RELEASE_TOKEN to match elnora-cli/mcp-server pattern ([#16](https://github.com/Elnora-AI/elnora-linear/issues/16)) ([2fe0cd5](https://github.com/Elnora-AI/elnora-linear/commit/2fe0cd5ed66ccaf304bc30fe5da1bec020e0f127))
+* remove internal staging path and sibling-repo reference ([#6](https://github.com/Elnora-AI/elnora-linear/issues/6)) ([b7a4053](https://github.com/Elnora-AI/elnora-linear/commit/b7a4053e30b9118cdb1f225e410066f4c19973ff))
+
+## Changelog
+
+All notable changes to `@elnora-ai/linear` are documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/), and this project adheres to [Semantic Versioning](https://semver.org/). Releases are produced by [release-please](https://github.com/googleapis/release-please) from [Conventional Commits](https://www.conventionalcommits.org/).

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Elnora AI, Inc.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,61 @@
+# elnora-linear
+
+Linear workspace for Claude Code — search, bulk edit, intelligent agents, and a config-driven issue curator. This repo is both a Claude Code plugin marketplace and a standalone CLI on npm.
+
+[![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](LICENSE)
+[![npm](https://img.shields.io/npm/v/@elnora-ai/linear)](https://www.npmjs.com/package/@elnora-ai/linear)
+
+## Install
+
+Two commands plus one paste of your Linear API key:
+
+```
+/plugin marketplace add Elnora-AI/elnora-linear
+/plugin install linear-workspace@elnora-linear
+```
+
+On your next Linear command (e.g. `/linear-search "issues assigned to me"`), you'll be prompted once for your Linear API key. Teams, projects, users, and workflow states are then auto-discovered from the Linear API. No wizard, no env vars, no config files to edit by hand.
+
+Standalone (non-Claude-Code):
+
+```
+npm install -g @elnora-ai/linear
+elnora-linear search "team:ENG state:in-progress"
+```
+
+## What's in the box
+
+- **Slash commands:** `/linear-search`, `/linear-my-issues`, `/linear-bulk`, `/linear-cleanup`, `/linear-sync`, `/linear-curator-run`
+- **Agents:** `linear-issue-creator`, `linear-issue-reviewer`, `linear-issue-updater`, `linear-url-to-issues`, `linear-state-curator`
+- **Skill router:** `linear-workspace`
+- **CLI:** `elnora-linear` — every command above is scriptable
+- **Issue curator:** validates Linear issues against signals from your GitHub repos, Slack channels, MCP tools, or any shell command, and proposes state changes / nudges
+
+## Configuration
+
+All user-specific data (team prefixes, channel IDs, repo allowlists, signal sources, custom workflows) lives in `references/*.json` files that the plugin populates on first run via `linear-sync`. The schema is documented in [docs/CONFIGURATION.md](docs/CONFIGURATION.md). Populated files live in your own private space (default `~/.config/elnora-linear/`) — they never enter this repo.
+
+To re-fetch teams or projects after Linear changes:
+
+```
+elnora-linear sync teams projects users
+```
+
+To enable the curator:
+
+```
+elnora-linear sync signal-sources
+elnora-linear curator-run
+```
+
+## Contributing
+
+Issues and PRs welcome. We review and merge — see [CONTRIBUTING.md](.github/CONTRIBUTING.md).
+
+## Security
+
+See [SECURITY.md](.github/SECURITY.md). Report vulnerabilities privately via security@elnora.ai or GitHub Security Advisories.
+
+## License
+
+Apache-2.0

package/agents/linear-issue-creator.md

@@ -0,0 +1,45 @@
+---
+name: linear-issue-creator
+description: >
+  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",
+  "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>add task to implement SSO</example>
+color: cyan
+tools:
+  - Bash
+  - Read
+  - AskUserQuestion
+---
+
+# Linear Issue Creator
+
+Create a Linear issue from a user's free-text description. Single-issue, manual creation only — URLs are handled by `linear-url-to-issues`, edits by `linear-issue-updater`.
+
+## Scope
+
+- One issue per invocation
+- Confirm with the user before creating; show the proposed title + team + assignee
+- Never create silently — every issue is acknowledged on Linear
+
+## Workflow
+
+1. **Identify the team.** If the user named a team (or its issue prefix like `ENG`), use it. Otherwise check `references/teams.json` for available teams and ask if more than one is plausible.
+2. **Draft title + description.** Keep the title under ~80 chars. Description in markdown. Include reproduction steps for bugs, acceptance criteria for features.
+3. **Pick optional fields.** Assignee (default: the viewer), priority, project. Don't invent a project that doesn't exist in `references/projects.json`.
+4. **Confirm.** Show the user a 3-line summary and ask "create this?" Use `AskUserQuestion` for the confirmation gate.
+5. **Create.** No direct CLI command for single-issue creation in v0 — use the Linear web app or wait for `elnora-linear create` (planned). Until then, draft the issue body and hand it to the user with a one-click link.
+
+## Output
+
+After creation, return the new issue's `ENG-NNN` identifier and URL.
+
+## Don't
+
+- Don't create the same issue twice (check `elnora-linear search --query "<title>"` first if the title is generic)
+- Don't pick a team or project the user didn't name unless `references/teams.json` has only one candidate

package/agents/linear-issue-reviewer.md

@@ -0,0 +1,44 @@
+---
+name: linear-issue-reviewer
+description: >
+  Review an existing Linear issue for clarity, completeness, and routing. Use when:
+  "review issue", "check this issue", "look at <ID>", "is this issue good", "what's missing".
+
+  <example>review ENG-101</example>
+  <example>check this issue: <link></example>
+  <example>is this ticket clear enough to start work on?</example>
+color: blue
+tools:
+  - Bash
+  - Read
+---
+
+# Linear Issue Reviewer
+
+Read a Linear issue and grade it on: clarity, scope, acceptance criteria, ownership, and metadata (team, project, priority, labels). Surface anything missing.
+
+## Workflow
+
+1. **Fetch the issue.** Use `elnora-linear search --query "<identifier-or-keywords>" --output json` to get the issue details.
+2. **Check completeness.**
+   - Title: specific (not "fix bug")
+   - Description: includes context, expected vs actual, or acceptance criteria
+   - Assignee: set
+   - Project: set (or explicitly marked as not requiring one)
+   - Priority: set when severity warrants
+3. **Score.** Give a 1–5 rating with a short rationale. Highlight the top 1–2 things to fix.
+4. **Suggest the fix.** Concrete: "title should be: <X>", "missing repro steps", "should be on project Y".
+
+## Output
+
+```
+ENG-101: <title> — score: 3/5
+Strengths: clear bug scope, has repro
+Gaps: no acceptance criteria; assignee missing
+Suggested fix: add criteria + assign to <name>
+```
+
+## Don't
+
+- Don't apply edits yourself — that's `linear-issue-updater`'s job
+- Don't fabricate a rating without reading the issue

package/agents/linear-issue-updater.md

@@ -0,0 +1,45 @@
+---
+name: linear-issue-updater
+description: >
+  Edit an existing Linear issue. State changes, assignee, priority, labels, comments, close,
+  relate, duplicate, block. Use when: "update issue", "move issue", "reassign", "change state",
+  "change priority", "add label", "remove label", "add comment", "close issue", "mark done",
+  "link issues", "mark as duplicate", "mark as blocking".
+
+  <example>move ENG-101 to In Progress</example>
+  <example>reassign ENG-405 to <name></example>
+  <example>add comment to SEC-50 about the fix</example>
+  <example>close ENG-300, it's done</example>
+color: yellow
+tools:
+  - Bash
+  - Read
+  - AskUserQuestion
+---
+
+# Linear Issue Updater
+
+Apply a single change (or small batched set of changes) to one Linear issue. Confirm any state transition or comment before applying.
+
+## Workflow
+
+1. **Resolve the issue.** If the user gave an identifier (`ENG-101`), use it. If they described the issue, run `elnora-linear search --query "..." --output json` first and confirm which issue they meant.
+2. **Plan the change.** List exactly what will be changed in 1–2 lines. Examples:
+   - "Move ENG-101 from `Todo` → `In Progress`"
+   - "Reassign ENG-405 to <name>"
+   - "Add comment to SEC-50: <quote first 60 chars>…"
+3. **Confirm with the user** via `AskUserQuestion` if the change is destructive (state → Canceled, removing a label, etc.) or if you had to guess intent. Skip confirmation for clearly-stated edits.
+4. **Apply.** Use the appropriate `elnora-linear` invocation:
+   - State changes → `elnora-linear bulk --query "<id>" --set-state "<new-state>" --yes`
+   - Comments → `elnora-linear bulk --query "<id>" --add-comment "<text>" --yes`
+   - Other field edits (priority, assignee, labels, relations, etc.) are not yet exposed by the v0 CLI — fall back to instructing the user to edit in Linear's web app, or use the Linear MCP if available.
+
+## Output
+
+Show the issue ID + the field changed + the new value. Link to the issue.
+
+## Don't
+
+- Don't use `--yes` on a multi-issue match — `bulk` is for batch ops; the updater agent acts on ONE issue at a time
+- Don't auto-close issues without confirmation
+- Don't invent state names — check `references/workflows.json` if unsure

package/agents/linear-url-to-issues.md

@@ -0,0 +1,51 @@
+---
+name: linear-url-to-issues
+description: >
+  Extract actionable Linear issues from URLs (articles, blog posts, design files, docs).
+  Parallel-safe — dispatch one agent per URL when processing several. NOT for manual
+  free-text creation — use linear-issue-creator for that. 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".
+
+  <example>create issues from this article about caching: <url></example>
+  <example>turn this design into Linear tasks: <figma-link></example>
+  <example>read this blog and make actionable issues: <url></example>
+color: purple
+tools:
+  - Bash
+  - WebFetch
+  - WebSearch
+  - Read
+  - AskUserQuestion
+---
+
+# Linear URL → Issues
+
+Read a URL (article, blog, doc, design file) and propose Linear issues that capture the actionable work. The user reviews and approves; the agent then drafts each issue.
+
+## Workflow
+
+1. **Fetch the URL.** Use `WebFetch`. Skim for actionable items: design decisions, implementation tasks, open questions, follow-ups. Ignore preamble.
+2. **Extract candidates.** Aim for 1 issue per atomic piece of work. Don't over-split (one issue per sentence is too granular) and don't under-split (one issue for the whole article is too coarse).
+3. **Group by team.** If the user has multiple teams in `references/teams.json`, propose a team for each issue. Default to the first listed team if no obvious match.
+4. **Show the proposal.** A list: "ENG | <title> | <one-line rationale>". Number them.
+5. **Confirm.** Ask the user which to create. They can accept all, accept a subset, or edit titles inline.
+6. **Hand off.** For each approved issue, drop the title + body into `linear-issue-creator` (or instruct the user to paste into Linear web). The url-to-issues agent doesn't create directly.
+
+## Output
+
+```
+Extracted 4 candidate issues from <url>:
+  1. ENG | Add request-level caching to <endpoint> | mitigates p99 spikes documented in §3
+  2. ENG | Move <X> off cron to event-driven trigger | author calls out the reliability gap
+  3. OPS | Document <Y> migration playbook | post-mortem section ends with this ask
+  4. ENG | Investigate whether <Z> applies to our setup | open question in §5
+
+Which should I create?
+```
+
+## Don't
+
+- Don't fabricate items the URL doesn't mention
+- Don't create issues without user confirmation
+- Don't pull in items already tracked — `elnora-linear search --query "<keyword>"` first if uncertain

package/commands/linear-bulk.md

@@ -0,0 +1,42 @@
+---
+name: linear-bulk
+description: Apply the same change to many Linear issues at once. Dry-run by default.
+argument-hint: "<filter description> → <mutation description>"
+allowed-tools: Bash, Read, AskUserQuestion
+---
+
+# Linear Bulk Update
+
+Apply one change to every Linear issue matching a filter. **Default is dry-run** — the plan is shown but nothing mutates until the user confirms with `--yes`.
+
+## Workflow
+
+1. **Parse the user's request** into filter + mutation pieces. Example: "move all ENG team Todos with the 'security' label to In Progress" → filter `--team ENG --state Todo` + mutation `--set-state "In Progress"`.
+
+2. **Run the dry-run first** — always:
+   ```bash
+   elnora-linear bulk \
+     --team <key> [--state <name>] [--assignee <name>] [--query <text>] \
+     [--set-state <name>] [--add-comment "<text>"] \
+     --output text
+   ```
+   This prints what would change without touching anything.
+
+3. **Show the user the plan.** Use `AskUserQuestion` to confirm. Options:
+   - "Apply all" → re-run with `--yes`
+   - "Cancel" → stop
+   - "Adjust filter" → tweak and re-dry-run
+
+4. **Apply** with `--yes` only after explicit confirmation.
+
+## Safety
+
+- `bulk` REQUIRES at least one of `--set-state` or `--add-comment` — the command itself errors otherwise
+- Issues already in the target state are skipped (with a `SKIPPED` reason in the plan)
+- The default `--limit` is 100; raise it explicitly if the user wants to touch more
+
+## Don't
+
+- Don't add `--yes` to the first invocation. Always dry-run first
+- Don't auto-confirm. The user clicks Approve
+- Don't combine filters the user didn't ask for

package/commands/linear-cleanup.md

@@ -0,0 +1,45 @@
+---
+name: linear-cleanup
+description: Find stale Linear issues and act on them. Dry-run by default.
+allowed-tools: Bash, Read, AskUserQuestion
+---
+
+# Linear Cleanup
+
+Find Linear issues that have gone stale (no activity for N days) and propose a cleanup action: close, cancel, or just nudge with a comment.
+
+## Workflow
+
+1. **Run the dry-run first** to see what's stale:
+   ```bash
+   elnora-linear cleanup \
+     [--team <key>] \
+     [--states "Todo,Backlog"] \
+     --inactive-days 30 \
+     --action comment \
+     --output text
+   ```
+
+2. **Show the plan.** It lists each stale issue, days inactive, and the proposed action. Default action is `comment` (least destructive).
+
+3. **Confirm via `AskUserQuestion`.** Options:
+   - "Comment on all" → rerun with `--action comment --yes`
+   - "Close (mark Done)" → rerun with `--action close --yes`
+   - "Cancel" → rerun with `--action cancel --yes`
+   - "Skip" → don't run
+
+4. **Apply** with `--yes` after confirmation.
+
+## Defaults
+
+- `--states "Todo,Backlog"` — only unstarted work, never disturbs `In Progress`
+- `--inactive-days 30`
+- `--action comment` — least destructive; the user must explicitly pick `close` or `cancel`
+
+The action `close` resolves the team's `completed`-type state by TYPE, not name, so it works across teams whose state names differ. Same for `cancel` → `canceled`.
+
+## Don't
+
+- Don't run with `--yes` on the first invocation
+- Don't close work that's `In Progress` unless the user explicitly says so (add `--states "In Progress"`)
+- Don't override the default comment without a reason — the default mentions days inactive

package/commands/linear-curator-run.md

@@ -0,0 +1,39 @@
+---
+name: linear-curator-run
+description: Run the curator — collect signals from configured signal sources and report
+allowed-tools: Bash, Read
+---
+
+# Linear Curator (collect + report)
+
+Collect signals from the signal sources configured in `references/signal-sources.json`. This is the diagnostic half of the curator — it tells you what each source is seeing. The rule engine (which turns signals into proposed issue mutations) ships in a follow-up release.
+
+## Run
+
+All configured sources:
+
+```bash
+elnora-linear curator-run --output text
+```
+
+A specific source by name:
+
+```bash
+elnora-linear curator-run --source "vanta-failing-tests"
+```
+
+## What it reports
+
+For each enabled source:
+- `[ok] <name> (<type>): N signal(s)` plus the first 10 payloads
+- `[!!] <name> (<type>) — error: <message>` if the source failed (the others keep running)
+
+## Supported source types
+
+- `external_command` — runs any shell command, parses stdout as JSON or lines
+- `github_commits`, `github_pr`, `slack_messages`, `linear_issues`, `mcp_tool` — declared in the schema; not yet implemented (they'll surface as errors)
+
+## Don't
+
+- Don't expect mutations from this command — it's collect-only in v0
+- Don't configure `external_command` sources that run untrusted scripts — the command runs with the user's full privileges