Issue Triage

Issue Triage

Let: T := bun ${CLAUDE_PLUGIN_ROOT}/skills/issue-triage/triage.ts — triage CLI | κ := complexity score

Default: T or T list (no args = list).

Create GitHub issues, assign Size/Priority labels, manage blockedBy dependencies and parent/child relationships.

Companion of /R-dev: run before /R-dev. Not a STEPS entry — /R-dev does not invoke this skill.

Instructions

1. List all open issues: T / T list | List untriaged only: T list --untriaged
2. ∀ issue: determine Size, Priority, κ (see Complexity Scoring)
3. Set values: T set <number> --size <S> --priority <P>
4. Create issues: T create --title "Title" [--body "Body"] [--label "bug,frontend"] [--size M] [--priority High] [--type feat] [--lane b] [--parent 163]
5. → ask userif unsure about Size ∨ Priority.

Size Guidelines

Canonical labels written: size:S / size:F-lite / size:F-full. --size also accepts legacy XS / S / M / L / XL and aliases them (XS→S, M→F-lite, L/XL→F-full).

Priority Guidelines

Commands

list — Show open issues

set <num> — Update an existing issue

create — Create a new issue

Cross-repo create

Set GITHUB_REPO=<owner/repo> to retarget the CREATE to a different repo than the cwd's git remote:

# File a voiceCLI issue while cwd is lyra (or any other repo)
GITHUB_REPO=Roxabi/voiceCLI T create \
  --title 'STT: audio dropout at segment boundary' \
  --blocked-by Roxabi/lyra#728

Cross-repo relations (--blocked-by, --blocks, --parent, --add-child) accept OWNER/REPO#N natively — they work regardless of GITHUB_REPO.

Caveat — keep refs fully-qualified: GITHUB_REPO retargets the entire invocation. A bare #N in any ref resolves against the overridden repo, not the cwd repo → always use OWNER/REPO#N for any cross-repo ref when the env var is set.

Resolution order (detectGitHubRepo): (1) github_repo in dev-core config ∨ GITHUB_REPO env var (validated as owner/repo) → (2) fallback git remote get-url origin of the cwd.

Deferred Follow-Ups — Sibling Rule

Defer ≠ decomposition. When an issue A defers work to a new follow-up B (out-of-scope finding, post-merge gap, "do this later"), B is a sibling of A under their shared parent — NOT a child of A.

       Epic E
      ╱      ╲
     A ←—————— B     B.parent = A.parent (= E)
       blocked-by    B.blocked-by = A   (traceability of origin)

Why:

• gh issue view E shows the full fan-out flat (A + B + future C…) — true scope of the epic, ¬nested cascade
• /R-dev re-scan retombe correctement sur l'épic origin pour tout follow-up
• Multi-level deferrals (A→B→C) stay flat under E — ¬arbre profond ingérable

Decomposition vs deferral:

Recipe — defer A → create follow-up B:

# 1. Resolve A's parent (may be null if A is top-level)
A_PARENT=$(gh api graphql -f query="query{repository(owner:\"$OWNER\",name:\"$REPO\"){issue(number:$A){parent{number}}}}" \
  --jq '.data.repository.issue.parent.number // empty')

# 2. Create B as sibling: same parent as A, blocked-by A
T create \
  --title "{deferred title}" \
  --body "**Origin:** #${A} (deferred from ...)\n\n{details}" \
  --blocked-by "#${A}" \
  ${A_PARENT:+--parent "#${A_PARENT}"}

Edge cases:

• A has no parent → B has no parent either (both top-level). Consider whether A should be re-parented under a freshly-created epic if the fan-out grows.
• A is already top-level epic → defer creates child of A (epic decomposition pattern applies).
• Existing follow-up issue B mis-parented under A → fix retroactively:

  T set <B> --rm-parent
  T set <B> --parent "#${A_PARENT}"
  T set <B> --blocked-by "#${A}"  # ensure traceability link
  

Complexity Scoring

Assess κ ∈ [1,10] to inform tier (S / F-lite / F-full). Record by appending to issue body:

BODY=$(gh issue view <number> --json body --jq .body)
gh issue edit <number> --body "$BODY

<!-- complexity: <score> -->"

<!-- complexity: N --> is machine-parseable; downstream tools (e.g. /plan) read it.

Factors (each 1-10, weighted):

Formula: κ = round(files × 0.20 + risk × 0.25 + arch × 0.25 + unknowns × 0.15 + domains × 0.15)

Tier mapping:

κ is advisory. Human judgment overrides. → ask userif score ≠ intuition.

Example Workflow

T list
T list --untriaged
T set 42 --size M --priority High
T set 91 --blocked-by 117
T set 117 --blocks 91,118
T set 91 --rm-blocked-by 117
T set 164 --parent 163
T set 163 --add-child 164,165,166
T set 164 --rm-parent
T set 163 --rm-child 166

# Cross-repo dependencies (owner/repo#N format)
T set 42 --blocked-by Roxabi/lyra#728
T set 42 --blocks Roxabi/voiceCLI#94

T create \
  --title "research: compare against example/repo" \
  --body "Deep analysis of example/repo" \
  --label "research" \
  --size S --priority Medium \
  --parent 163
T create \
  --title "epic: improve CI pipeline" \
  --size L --priority High \
  --add-child 150,151,152

# Lane and type (additive, optional)
T set 42 --lane b
T set 42 --type feat
T set 42 --size M --priority High --lane c1 --type fix

Completion

• Success: print one line: Done. Next: /R-dev #N. Stop.
• Failure: return error.

$ARGUMENTS