一键在 Manus 中运行任何 Skill

linear-ticket-routing

星标1

分支0

更新时间2026年4月3日 02:01

Route a Linear ticket to the correct skill based on its action label (epic, research, prep, bug, execute, review — with or without

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

stepandel

stepandel/vera

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Linear Ticket Routing

Route a Linear ticket to the correct skill by reading its #-prefixed action labels.

Use this when picking up a ticket from a non-webhook entry point (e.g. Slack, manual prompt). The Linear webhook handler does this routing automatically — this skill is for all other paths.

Steps

Fetch the ticket using linear_issue (action: view).
Check the ticket's labels for action labels. Labels may appear with or without the # prefix — both #research and research are equivalent.
If multiple action labels are present, pick the highest priority from the table below.
Check for the #verbose modifier (see below).
Read and follow the corresponding skill.

Routing Table

Label	Priority	Skill	What it does
`#epic`	0 (highest)	`linear-epic`	Orchestrate an epic — break down, sequence, and drive sub-issues to completion.
`#bug`	1	`linear-bug`	Investigate bug, identify root cause, fix it, open a PR.
`#research`	2	`linear-research`	Deep-dive research, produce a written report. No code changes.
`#prep`	3	`linear-prep`	Size, research, enrich context, write implementation prompt. No code changes.
`#execute`	4	`linear-execute`	Implement the solution and open a PR.
`#review`	5 (lowest)	`linear-review`	Review the linked PR for correctness and style. No code changes.

Modifiers

Modifiers can be combined with any action label.

Modifier	Effect
`#verbose`	Be over-communicative. Before each phase, explain what you're about to do. Ask clarifying questions on the ticket before proceeding whenever there is any ambiguity. Surface all assumptions and ask for confirmation. Report progress at every step. When in doubt, ask.

同仓库更多 Skills

同仓库

vera-browser

stepandel/vera

Render pages with headless Chromium: screenshot, mobile/responsive layout review, viewport sweep, post-JS DOM, eval JS. Use for any visual/design/frontend QA task — see how a page actually looks rather than read its source. Triggers on: screenshot, render, mobile layout, responsive, viewport, breakpoint, design review, visual review, frontend QA, what does X look like, see the page, hydrated DOM, SPA, headless browser.

2026-04-091

linear-epic

stepandel/vera

Orchestrate an epic — assess readiness, sequence sub-issues, implement all on a single branch, open one PR, and deliver a completion summary. Handles fresh epics, partially-completed epics, and crash recovery.

2026-04-081

linear

stepandel/vera

Linear project management integration. Provides tools for managing issues, comments, teams, projects, and issue relations via the Linear GraphQL API.

2026-04-061

linear-bug

stepandel/vera

Investigate a bug or issue reported in a Linear ticket. Identify root cause, assess impact, implement the fix, and open a pull request.

2026-04-061

linear-execute

stepandel/vera

Implement the solution for a Linear ticket and open a pull request. Full coding workflow — plan, implement, test, PR.

2026-04-061

linear-prep

stepandel/vera

Prepare Linear tickets for the coding agent. Validates sizing (splits oversized tickets into sub-issues), researches tools/APIs involved, enriches context by scanning the codebase, and generates a focused implementation prompt.

2026-04-061

name	linear-ticket-routing
description	Route a Linear ticket to the correct skill based on its action label (epic, research, prep, bug, execute, review — with or without
scopes	["linear","slack"]

Linear Ticket Routing

Route a Linear ticket to the correct skill by reading its #-prefixed action labels.

Use this when picking up a ticket from a non-webhook entry point (e.g. Slack, manual prompt). The Linear webhook handler does this routing automatically — this skill is for all other paths.

Steps

Fetch the ticket using linear_issue (action: view).
Check the ticket's labels for action labels. Labels may appear with or without the # prefix — both #research and research are equivalent.
If multiple action labels are present, pick the highest priority from the table below.
Check for the #verbose modifier (see below).
Read and follow the corresponding skill.

Routing Table

Label	Priority	Skill	What it does
`#epic`	0 (highest)	`linear-epic`	Orchestrate an epic — break down, sequence, and drive sub-issues to completion.
`#bug`	1	`linear-bug`	Investigate bug, identify root cause, fix it, open a PR.
`#research`	2	`linear-research`	Deep-dive research, produce a written report. No code changes.
`#prep`	3	`linear-prep`	Size, research, enrich context, write implementation prompt. No code changes.
`#execute`	4	`linear-execute`	Implement the solution and open a PR.
`#review`	5 (lowest)	`linear-review`	Review the linked PR for correctness and style. No code changes.

Modifiers

Modifiers can be combined with any action label.

Modifier	Effect
`#verbose`	Be over-communicative. Before each phase, explain what you're about to do. Ask clarifying questions on the ticket before proceeding whenever there is any ambiguity. Surface all assumptions and ask for confirmation. Report progress at every step. When in doubt, ask.