メニュー
Manage Linear projects — triage boards, create issues and epics, enforce labels and metadata, audit dependencies. Use when user wants to triage issues, create/review tickets, clean up a board, manage labels/priorities/milestones, or write epics with sub-issue decomposition.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | linear-triage |
| description | Manage Linear projects — triage boards, create issues and epics, enforce labels and metadata, audit dependencies. Use when user wants to triage issues, create/review tickets, clean up a board, manage labels/priorities/milestones, or write epics with sub-issue decomposition. |
Manage and triage issues in Linear using mcp__claude_ai_Linear__* MCP tools. All mutations follow prepare → confirm → execute: present proposed changes, wait for approval, then apply.
The user invokes /linear-triage then describes what they want.
Triage requests → follow TRIAGE.md:
Issue creation → follow ISSUE-WRITING.md:
Epic creation → follow EPIC-WRITING.md:
Label/metadata questions → follow LABELS.md:
ready).save_issue.epic label + category label, priority, milestone.Follow TRIAGE.md for board-level or single-issue triage.
When posting triage comments to Linear:
**Triage note** (generated by AI)
[content]
Mechanics for leaving a pull request review on GitHub - CLI scripts for fetching PR data, attaching comments to the right file/line, wording/tone/severity conventions, and posting a batched review. Use when the user has feedback to leave on a PR and needs to know how to post it correctly.
Principles for writing, refactoring, and reviewing React code so it stays maintainable — resisting premature abstraction (the "demon component"), keeping data flow obvious, and putting state and effects in the right place. Use when writing or refactoring a React component or hook, deciding whether to extract or reuse one, reviewing React for maintainability, reaching for useEffect, choosing where state lives, or untangling prop drilling and over-abstraction.
Comprehensive tool for creating D2 diagrams based on descriptions and requirements. This skill should be used when creating visual diagrams, system architectures, flowcharts, network topologies, data flows, or any visual representation that can be expressed as a diagram. Triggers include requests to "create a diagram," "visualize," "draw an architecture," "show relationships," or when converting textual descriptions into visual diagrams.
Enforces Effect-TS patterns for services, errors, layers, and atoms. Use when writing code with Effect.Service, Schema.TaggedError, Layer composition, or effect-atom React components.
Comprehensive testing patterns for Effect-TS services, errors, layers, and effects. Use this skill when writing tests for Effect-based code.
This skill should be used when the user asks about Effect-TS patterns, services, layers, error handling, service composition, or writing/refactoring code that imports from 'effect'. Also covers Effect + Next.js integration with @prb/effect-next.