triage
Triage examines GitHub issues and pull requests by gathering context, investigating the codebase, and estimating implementation difficulty. It generates structured reports covering issue classification, platform support status, existing feature overlap, and actionable recommendations for whether to address, defer, or decline each request.
Triage analyzes GitHub issues and pull requests to assess feasibility, priority, and implementation effort for decision-making.
AI-generated summary based on this skill's SKILL.md
Install
K9i-0/ccpocket/triage · repository language: Dart
git clone https://github.com/K9i-0/ccpocket
cp -r ccpocket/.claude/skills/triage ~/.claude/skills/triageFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What does Triage do for GitHub issue analysis?
Triage examines GitHub issues and pull requests by gathering context, investigating the codebase, and estimating implementation difficulty. It generates structured reports covering issue classification, platform support status, existing feature overlap, and actionable recommendations for whether to address, defer, or decline each request.
Can Triage help with automated issue triaging workflows?
Yes. Triage automates the core triaging workflow by analyzing issues and PRs to assess feasibility, priority, and implementation effort. It categorizes requests by type (bug, feature, prompt request), evaluates platform support status, and produces difficulty estimates to streamline your GitHub issue management process.
How does Triage evaluate external pull requests?
Triage evaluates external PRs for quality, compliance, and integration viability. It investigates codebase impact, identifies duplicate or existing features, and provides structured assessments to help you decide whether to merge, request changes, or decline contributions.
What kind of reports does Triage generate?
Triage generates structured triage reports with difficulty estimates and action recommendations. Reports include issue classification, severity assessment, workload estimation, existing feature overlap analysis, and clear guidance on next steps for each GitHub issue or pull request.
Does Triage identify duplicate issues or existing features?
Yes. Triage investigates codebase impact and identifies duplicate or existing features for a given issue. This helps prevent redundant work and ensures new requests align with your current feature set and development roadmap.
SKILL.md
rendered from the published skill — quoted content, verbatim
Issue / PR トリアージ
GitHub Issue または PR の番号を受け取り、コードベースを調査して対応判断に必要な情報をレポートする。
使い方
/triage 42
/triage #8
トリアージ手順
Phase 1: 情報収集
1-1. Issue/PR の取得
番号からIssueかPRかを自動判定する。
# まずIssueとして取得を試みる
gh issue view <番号> --json number,title,body,labels,state,comments,author,createdAt
# 404なら PRとして取得
gh pr view <番号> --json number,title,body,labels,state,files,comments,author,reviews,createdAt
1-2. コメント・議論の確認
# Issueのコメント
gh issue view <番号> --json comments --jq '.comments[].body'
# PRのレビューコメント
gh pr view <番号> --json reviews --jq '.reviews[].body'
1-3. 種別の判定
IssueテンプレートやラベルからIssueの種別を判定する:
| 種別 | 判定基準 |
|---|---|
| Bug Report | bug ラベル、テンプレートのフィールド |
| Feature Request | enhancement ラベル、Proposal セクション |
| Prompt Request | テンプレートに「プロンプト」「AI tool」セクション |
| Dependabot | author が dependabot[bot] |
| 外部PR | authorがリポジトリオーナー以外 |
1-4. プラットフォームサポート状況の判定
Issue / PR が以下に該当するかを確認する:
- 正式サポート環境: メンテナが普段利用・検証できる環境
- experimental / best-effort 環境:
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
.claude/skills/triage/SKILL.md