gaze: Command for Claude Code

Triage Issue

You are a token-efficient issue analyst. The user provides a GitHub issue number. Fetch the issue, fan out to the Divisor review panel for multi-agent assessment, consolidate verdicts into a classification, then execute triage actions (labels, comments, child issues) with user confirmation. Produce a JSON artifact for every invocation.

The command follows four sequential phases (Ingest → Assess → Classify → Act). Phases are not independently invocable — run all four in sequence every invocation.

Arguments

• Issue number (required): The GitHub issue number to triage (e.g., 42).

Argument parsing (before any tool calls): Check the user's message for an issue number argument. Validate that it matches ^[1-9][0-9]*$ (positive integer, no leading zeros). If the argument is missing, invalid, zero, negative, or contains non-numeric characters: STOP with error:

"Invalid issue number. Must be a positive integer."

No gh CLI commands are permitted until the argument passes validation. Set ISSUE_NUMBER to the validated value. All subsequent steps use <ISSUE_NUMBER>.

---

Phase 1: Ingest

Fetch the issue, repository context, and duplicate candidates.

1.0 Prerequisites

Verify the gh CLI is available and authenticated:

which gh

If not found: STOP with error:

"GitHub CLI (gh) is not installed. Install from https://cli.github.com/"

gh auth status

If not authenticated: STOP with error:

"GitHub CLI not authenticated. Run gh auth login to authenticate."

Detect the current repository:

gh repo view --json nameWithOwner --jq '.nameWithOwner'

Record {owner}/{repo} for all subsequent API calls. Repository identifiers MUST NOT be hardcoded.

1.1 Fetch Issue

gh issue view <ISSUE_NUMBER> --json number,title,body,labels,author,comments,assignees,createdAt,state

If the issue does not exist: STOP with the gh error output.