Menu
Triage Linear inbox issues with AI classification. Triggers on "pm triage", "triage inbox", "classify issues", "process inbox", "处理反馈".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Analyze a blog article's structure to plan optimal image placement, then generate and insert AI images. This is the blog-specific image workflow — it reads a markdown article, identifies where images should go, creates a plan, and generates images that fit each section. Use when the user wants images added to an existing article — e.g., "analyze article images", "suggest images for this post", "generate article images", "分析文章配图", "生成文章配图", "插入文章配图". Do NOT use for standalone image generation (use yux-nano-banana instead). After generating, use yux-blog-oss to upload images to CDN.
Generate images via OpenRouter API with user-selected models. Supports any OpenRouter image model (Gemini, Flux, etc.), prompt optimization, text-to-image, and image editing. Triggers on "generate image", "create image", "draw", "nano banana", "image generation", "生成图片", "画图", "图像生成", "信息卡片".
Commit changes with conventional commit messages and sync to Linear. Triggers on "linear commit", "commit and sync", "save progress", "提交代码".
Start working on a Linear issue with worktree isolation. Triggers on "start task", "linear start", "work on LIN-123", "begin task", "开始任务".
Initialize Linear integration for current project. Triggers on "linear init", "初始化linear", "setup linear", "configure linear", "连接linear".
Linear project dashboard (task/backlog/tasks modes). Triggers on "linear status", "show my tasks", "show backlog", "project overview", "项目概览".
| name | yux-pm-triage |
| description | Triage Linear inbox issues with AI classification. Triggers on "pm triage", "triage inbox", "classify issues", "process inbox", "处理反馈". |
| allowed-tools | Read, Write, Glob, Grep, Bash(git:*), Bash(gh:*), mcp__linear__* |
Process inbox issues: classify type, set priority/effort, structure descriptions, and move to Backlog.
Prerequisite: .claude/linear-config.json must exist. If missing, show:
"Please run /yux-linear-init first."
Read .claude/linear-config.json
mcp__linear__list_issue_labels(team: "<team.id>")
Parse labels into categories:
mcp__linear__list_issues(
project: "<project.id>",
state: "Triage",
limit: 20,
orderBy: "createdAt"
)
If empty, report clean inbox and stop.
Display inbox summary table (ID, title, created date) and ask user to process all or select specific items.
For each selected issue, analyze these factors:
Type Detection (keyword-based):
If multiple types match, prefer: Bug > Feature > Improvement > Chore.
Priority Assessment:
Effort Estimation (T-shirt sizing):
For each issue, display:
Ask user to apply, reject, or edit before proceeding.
On confirmation, update the issue in Linear:
mcp__linear__update_issue(
id: "<issue_id>",
description: "<structured_description>",
priority: <priority_number>,
labels: ["<type_label_id>", "<func_label_id>"],
project: "<project.id>",
state: "Backlog"
)
After all items are processed, display summary:
=== Triage Complete ===
Processed: 5 issues
By Type: Bug: 2 | Feature: 2 | Improvement: 1
By Priority: High: 1 | Medium: 3 | Low: 1
Moved to Backlog:
WYX-120 [Bug/High] Login crash on iOS
WYX-121 [Feature/Med] Dark mode support
WYX-122 [Bug/Med] Typo in settings