Organize GitHub issues by reading their full descriptions and adding labels for type, effort, priority, and affected area. Preserve existing labels, fill missing categories, and summarize the reasoning alongside duplicate, related, or blocking issue relationships.
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.
Review the instructions the agent will receive before you install.
Triage issues for this repository by applying appropriate labels.
gh repo view --json nameWithOwner -q .nameWithOwner 2>/dev/null || echo "unknown"gh issue list --state open --json number --jq 'length' 2>/dev/null || echo "?"gh label list --json name -q '.[].name' 2>/dev/null | head -20 || echo "none found"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) |
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:
Glob, Grep, Read) to understand the affected codegh issue edit {number} --add-label "type,effort/level,P#,area.domain"
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 |
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use the Archon CLI to launch AI workflows on projects, inspect their results, and approve, reject, cancel, or resume runs. The skill also guides setup, configuration changes, workflow creation, and improvements to workflow prompts.
Customize a project's Docker environment with personal tools such as vim, ripgrep, or jq. The skill prepares user override files, adds requested packages, and provides rebuild commands while keeping personal configuration out of Git.
Automate browser actions such as filling forms, clicking buttons, and switching tabs. Inspect page snapshots, network requests, and console messages to check website behavior, record interactions, and support work on Playwright tests.
Prepare a software release from the dev branch by turning commits into a changelog, updating the version, and creating a pull request to main. The workflow also covers release tags, branch synchronization, and Homebrew package updates.
Delegate checks for AGENTS.md rule violations to a dedicated agent. It scans the codebase, fixes high-impact issues in a separate working copy, runs full validation, and creates a pull request, tracking progress across runs through memory.
Test a released archon binary through Homebrew or curl installation on macOS or a Linux VPS. Check version information, bundled workflows, Claude execution, and sensitive environment key removal, then clean up and report the results.