atomicinnovation Search Linear Issues
!accelerator config context --skill search-linear-issues --fail-safe
Configuration: Set
work.integration: linearin.accelerator/config.md. The team is fixed at/init-lineartime (single-team scoping) — there is no per-search--teamflag. See the### worksection ofconfigure/SKILL.mdfor the full reference.
Search the configured Linear team using structured flags that compose into a
Linear IssueFilter. Work through the steps below in order.
Step 1: Parse the flag set
Read the argument string and note each flag:
--state NAME— WorkflowState name. Resolved (case-insensitively) to its team-scoped UUID via the cached catalogue; an unknown state is an error.--assignee NAME— assignee display name.--label NAME— label name.--text STR— free-text match on the issue title.--limit N— page size (1..250, default 50). Pagination follows every page regardless;--limitonly sets the per-request page size.
Step 2: Run the search
Run the search subcommand, passing the flags through verbatim:
accelerator linear search [flags]
Run the bare launcher directly as an executable; never prefix it with
bash/sh/env and never pipe its output (a wrapper prefix or a pipe escapes
the skill's allowed-tools permission and forces an unnecessary prompt).
The subcommand echoes the composed IssueFilter to stderr (INFO:) for
auditability and emits a single merged JSON document with all pages under
.data.issues.nodes, plus a top-level outcome keyword — results, empty,
or truncated. When outcome is truncated (equivalently
.data.issues.truncated is true), more pages remained than were fetched —
say so.
Step 3: Render the results
Render a Markdown table with one row per issue:
| Identifier | Title | State | Assignee |
|---|
Read each row from .data.issues.nodes[]: .identifier, .title,
.state.name, .assignee.name (show — for an unassigned issue). Report the
total count and note if the result was truncated.
!accelerator config instructions search-linear-issues --fail-safe