From logvalet
Triage a Backlog issue: the LLM analyzes triage materials (issue attributes, history, project statistics, similar issues) and suggests priority, assignee, and category assignments. Use this skill whenever someone needs help deciding how to prioritize or assign an issue. TRIGGER when: user says "トリアージ", "triage", "優先度を決めて", "アサイン提案", "課題を振り分けて", "誰に担当させる", "priority 提案", "担当者を決めて", "課題のカテゴリ分類", "issue triage", "優先度の見直し", "アサインの提案", "この課題の優先度は", "誰にアサインすべき", "振り分けて", "prioritize this issue", "who should handle this", "assign this task", "課題の優先順位", "タスクの振り分け", "課題を整理して". DO NOT TRIGGER when: user wants full issue context without recommendations (use context) or wants to create a new issue (use issue-create). Workflow: Automatically fetches triage-materials before analysis.
npx claudepluginhub youyo/claude-plugins --plugin logvaletThis skill uses the workspace's default tool permissions.
`lv issue triage-materials` を材料に、LLM が priority / assignee / category を提案する。
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
lv issue triage-materials を材料に、LLM が priority / assignee / category を提案する。
For full logvalet CLI documentation, see the
logvaletskill.
Use logvalet-triage when you need to:
If the user provides a Backlog issue key (e.g., PROJ-123, a URL like *.backlog.com/view/PROJ-123), extract and use it directly.
If no key is provided, ask for it.
lv issue triage-materials ISSUE_KEY -f json
This returns a structured set of triage signals including:
similar_issues.assignee_distribution)project_stats.by_assignee)Based on the triage materials, reason about each of the following:
Priority:
Assignee:
project_stats.by_assignee: current open issue counts per user (prefer users with fewer open issues)similar_issues.assignee_distribution: who has handled similar issues in the past (domain familiarity)lv watching list --user-id me -f json), check whether any team member is already watching this issue — watching indicates interest or domain knowledge, which can be a positive signal for assignee selectionCategory:
Present the triage proposal in a structured format:
## トリアージ提案 — ISSUE_KEY
### 現状
- ステータス: X | 優先度: Y | 担当者: Z
### 提案
| 項目 | 現在 | 提案 | 根拠 |
|------|------|------|------|
| 優先度 | 中 | 高 | 期限超過・高影響度 |
| 担当者 | 未設定 | UserName | 関連スキルあり、負荷余裕あり |
| カテゴリ | — | バグ | 再現手順・エラーログあり |
### 関連課題
- PROJ-100: 類似バグ（解決済み）
- PROJ-200: 同一コンポーネント（進行中）
### ウォッチ情報
- この課題をウォッチしているユーザーが特定できる場合、参考情報として表示する
- ウォッチしている ＝ 関心や知識がある可能性 → 担当候補の補助シグナル
---
適用しますか？ [優先度/担当者/カテゴリ/全て/キャンセル]
After the user confirms which items to apply, run lv issue update for each approved change:
lv issue update ISSUE_KEY --priority "高" --dry-run
lv issue update ISSUE_KEY --priority "高"
lv issue update ISSUE_KEY --assignee USER_ID --dry-run
lv issue update ISSUE_KEY --assignee USER_ID
lv issue update ISSUE_KEY --category "バグ" --dry-run
lv issue update ISSUE_KEY --category "バグ"
Always run --dry-run first before applying each change.
triage-materials is the authoritative source — do not fetch separate issue get / user workload calls; the materials contain everything neededproject_stats.by_assignee provides current open issue count per user — use it to avoid overloading busy memberssimilar_issues.assignee_distribution shows who has handled similar issues — use it for domain familiarity signalssimilar_issues list, rely on project_stats.by_assignee alone for assignee proposalsuser workload separately; triage-materials already includes workload signals via project_stats.by_assigneesimilar_issues.assignee_distribution