القائمة
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 ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
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.
Linear project management integration. Provides tools for managing issues, comments, teams, projects, and issue relations via the Linear GraphQL API.
Investigate a bug or issue reported in a Linear ticket. Identify root cause, assess impact, implement the fix, and open a pull request.
Implement the solution for a Linear ticket and open a pull request. Full coding workflow — plan, implement, test, PR.
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.
| 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"] |
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.
linear_issue (action: view).# prefix — both #research and research are equivalent.#verbose modifier (see below).| 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 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. |