無料GitHub で公開

triage

Triage GitHub issues by applying type, effort, priority, and area labels. Runs in an isolated context to avoid polluting the main conversation with issue details. Delegates to a specialized triage agent with label validation hooks.

coleam00/Archon

インストール方法を見る

含まれるファイル（2）

SKILL.md3.0 KB
workshop-guide.md8.6 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Triage GitHub Issues

Triage issues for this repository by applying appropriate labels.

Repository Context

Current repo: !gh repo view --json nameWithOwner -q .nameWithOwner 2>/dev/null || echo "unknown"
Open issues: !gh issue list --state open --json number --jq 'length' 2>/dev/null || echo "?"
Existing labels: !gh label list --json name -q '.[].name' 2>/dev/null | head -20 || echo "none found"

Scope

Determine which issues to triage based on the arguments: $ARGUMENTS

Argument	Behavior
(empty)	Only unlabeled issues (default)
`unlabeled`	Only issues without any labels
`all`	All open issues
`N`	Specific issue (e.g., `67`)
`N-M`	Range of issues inclusive (e.g., `60-67`)

Process

Fetch available labels — run gh label list --json name,description to understand the label taxonomy. Labels are organized into type, effort, priority, and area categories.
Fetch target issues — based on the scope above. For each issue, fetch the full body:
```
gh issue view {number} --json number,title,body,labels
```
For each issue:
- Read the title and full body carefully
- If needed, explore the codebase (Glob, Grep, Read) to understand the affected code
- Classify: one type, one effort, one priority, one or more areas
- Track relationships with other issues (duplicates, related, blocking)
- Apply labels:
```
gh issue edit {number} --add-label "type,effort/level,P#,area.domain"
```
- Skip issues that already have complete labeling (type + effort + priority + area)
- For partially labeled issues, only add missing label categories

Output a triage summary:

## Triage Summary

| Issue | Title | Labels Applied | Reasoning |
|-------|-------|----------------|-----------|
| #67 | ... | bug, effort/low, P1, core.config | ... |

**Totals:**
- Issues triaged: X
- Already labeled (skipped): Y
- By priority: P0(n), P1(n), P2(n), P3(n)

## Relationships Discovered

| Issues | Relationship | Notes |
|--------|--------------|-------|
| #61, #62 | Related | Both involve config/logging UX |

Rules

Don't hardcode labels — always fetch current labels first, they may change
Respect existing labels — don't remove labels, only add missing ones
Check issue body — titles alone aren't enough context
Use the codebase — if understanding a relationship requires seeing how modules connect, look
When uncertain, note it — flag ambiguous issues in the summary rather than guessing

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

archon-cli

無料

Drive Archon through its CLI: run AI workflows on a repo, manage those runs (inspect, approve, reject, cancel, resume), set up Archon or change its config, author new workflows, and improve workflow prompts. Use when the user says "use archon", "run archon", "archon workflow", "fix issue #N with archon", "have archon review this PR", "what's running / check run <id>", "approve/reject/cancel/resume that run", "set up archon", "configure archon", "change my archon config", "create a workflow", "author a workflow", or asks how to write a better Archon prompt. NOT for: doing the coding work yourself — Archon delegates it to isolated runs.

日本語の概要は準備中です。原文の説明を表示しています。