linear-triage
Create an automation that triages new Linear issues. Inspects the issue title, description, team, customer, priority, and recent related issues via Linear MCP. Suggests labels, priority, likely owner, duplicates, and posts a clarifying comment.
来源信息
- 仓库
- OpenHands/extensions
- 最近来源活动
- 2026年10月2日 03:19
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 157
- 分支
- 102
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
文件资源管理器
6 个文件正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- linear-triage
- description
- Create an automation that triages new Linear issues. Inspects the issue title, description, team, customer, priority, and recent related issues via Linear MCP. Suggests labels, priority, likely owner, duplicates, and posts a clarifying comment.
- triggers
- ["/linear-triage:setup"]
# Linear Issue Triage Automation
Set up an automation that triages new Linear issues — classifying, labeling,
and suggesting owners automatically.
---
## Prerequisites
### Required integration
- **Linear MCP** must be installed in Settings → MCP.
### Information to collect
Ask the user for:
1. **Teams/projects** — which Linear teams or projects should be triaged (e.g. `Engineering`, `Support`)
2. **Label taxonomy** — what labels are used for classification? (e.g. `bug`, `feature`, `support`, `chore`)
3. **Priority conventions** — how does the team use priority levels? Any mapping rules?
4. **Auto-apply or suggest** — should the automation apply labels/priority/assignee directly, or post a triage comment with suggestions for human approval?
5. **Duplicate detection** — should it search for and flag potential duplicate issues?
---
## Setup Workflow
### Step 1 — Verify Linear MCP access
Confirm the Linear MCP integration is working:
```
Use the Linear MCP to list recent issues for one of the target teams.
```
If it fails, tell the user to install the Linear MCP integration first.
### Step 2 — Determine trigger type
**Event-based (recommended if publicly reachable):**
Check `<RUNTIME_SERVICES>` for deployment reachability. If public, recommend an event trigger on Linear `Issue` create events.
**Cron-based (local/private deployments):**
Poll for recently created issues on a schedule (e.g. every 5 minutes).
### Step 3 — Build the triage prompt
Construct a prompt that includes:
- Target teams/projects
- Label taxonomy and classification rules
- Priority mapping conventions
- Whether to auto-apply or suggest
- Duplicate detection preference
### Step 4 — Create the automation
Set `OPENHANDS_HOST` and `AUTH_HEADER` for the request below:
- **OpenHands Cloud or Enterprise** - a `<HOST>` value is in your system prompt: use it as `OPENHANDS_HOST`, with `AUTH_HEADER="Authorization: Bearer $OPENHANDS_API_KEY"`
- **Local Agent Canvas** - an **Automation backend** is listed in `<RUNTIME_SERVICES>`: use its `url_from_agent` as `OPENHANDS_HOST`, with `AUTH_HEADER="X-Session-API-Key: $OPENHANDS_AUTOMATION_API_KEY"`
Use the **prompt preset** endpoint:
```bash
curl -s -X POST "${OPENHANDS_HOST}/api/automation/v1/preset/prompt" \
-H "$AUTH_HEADER" \
-H "Content-Type: application/json" \
-d '{
"name": "Linear Issue Triage",
"prompt": "<constructed triage prompt>",
"trigger": <trigger config from step 2>
}'
```
PowerShell note: use `curl.exe` for this exact flag syntax, and replace `${OPENHANDS_HOST}` / `$AUTH_HEADER` with `$env:OPENHANDS_HOST` / `$env:AUTH_HEADER` if running it natively.
### Step 5 — Confirm
Tell the user:
> ✅ **Linear Issue Triage** is running!
>
> - Automation ID: `{id}`
> - Teams: `{team list}`
> - Mode: `{auto-apply or suggest}`
> - Trigger: `{trigger description}`
在 GitHub 查看