linear-issue
Fetch a Linear issue by ID and display its details.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Menu
Fetch a Linear issue by ID and display its details.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Research products on amazon.com.au (Australia) and return options with title-verified links, indicative AUD prices, and stock status. Use when asked to research a product, "find me options for X", compare prices, or for help shopping or buying something on Amazon. Australian marketplace only — this skill does not cover amazon.com or other marketplaces.
Create a Git worktree for a new task. This skill should be used when the user asks to "start working on", "implement", "fix", "add", "refactor", "migrate", or otherwise begin a code task that requires a new branch. Do not use for trivial tasks like reading files, answering questions, or changes to the current dotfiles repo.
Drive Apple Reminders as a GTD system from the command line — capture to an inbox, read and search across lists, enrich items with notes, complete, delete, and triage with the 2-minute rule. Use when asked to add/capture a task or idea, "add to my inbox / Stuff list", reschedule or move an item, process/triage the inbox, find 2-minute items, or write research findings into a reminder's note. macOS + iCloud only, via the `reminders` CLI (keith/reminders-cli). Read/capture/enrich is fully supported; moving between lists and rescheduling due dates are not (see Gaps).
Append a timestamped, super-condensed summary of the current session — plus any open loops to close later — to today's dump file at ~/.me/quick-dumps/YYYY-MM-DD.md. Use when asked to "dump state", "dump the session", "jot this down", "save where we're at", or invokes /dump-state.
Review one or more GitHub PRs and write a per-PR findings file (with a go/no-go call at the top) into ~/Developer/ai-workspace/code-reviews/. Use when asked to "review this PR", "review my PRs", "write review notes", or given a PR URL / a search criteria for PRs to review. Produces documents for later human review or handoff to another agent that posts the comments — it does NOT post anything to GitHub.
Check CI status for PRs and Buildkite builds, diagnose failures, auto-fix when possible. Use when asked to "check CI", "check PR status", "how's the build", "monitor CI", "what's failing", or given a Buildkite build URL. Also use after pushing code when the user wants to track the build.
| name | linear-issue |
| description | Fetch a Linear issue by ID and display its details. |
| allowed-tools | Bash(curl *), Bash(python3 *) |
| user-invocable | true |
Fetch a Linear issue and display its title, description, state, and comments.
<issue-id> — the issue identifier (e.g., AINFRA-829).
If empty, ask the user for the issue ID.
If no issue ID is provided, ask the user.
curl -s -X POST https://api.linear.app/graphql \
-H "Content-Type: application/json" \
-H "Authorization: $LINEAR_API_KEY" \
-d '{"query": "{ issue(id: \"<ISSUE_ID>\") { identifier title description state { name } priority priorityLabel assignee { name } labels { nodes { name } } comments { nodes { body createdAt user { name } } } } }"}' \
| python3 -m json.tool
Replace <ISSUE_ID> with the provided issue identifier.
Format the output clearly:
If the API returns an error or null issue, report that the issue was not found and suggest checking the ID.