Triage, GitHub Issue & PR Investigator

When to Use

Don't use when: fixing a specific already-diagnosed issue (use /marshal); monitoring a single PR's CI (use /pr-watch); reviewing code quality outside of GitHub issues (use /review).

• /triage, triage all open, unlabeled issues
• /triage 10, investigate issue #10 specifically
• /triage pr 13, review PR #13
• /triage prs, review all open PRs
• /triage --batch, pull all open issues, classify, investigate, report
• /triage --stale, find issues older than 14 days with no activity
• After the issue-monitor SessionStart hook reports new issues

Codex PR review integration

For Codex-visible PRs, decide whether to use native @codex review, local Citadel triage, or both:

node scripts/codex-pr-review.js plan --repo <owner/repo> --pr <number> --risk <low|medium|high|local-only> --write

Use native @codex review when the diff is GitHub-visible and the main need is a focused P0/P1 review. Use local Citadel triage when the answer depends on unpushed files, local generated artifacts, or hands-on edits. Use both for large or risky PRs.

After Codex posts a GitHub review, fetch and ingest the review comments before deciding merge readiness:

node scripts/codex-review-fetch.js --repo <owner/repo> --pr <number> --write

Use --file <review-comments.json> with the same script when working from exported/offline review data.

Treat ingested P0/P1 findings as blockers until local verification confirms they are fixed or not applicable.

Inputs

Input	Source	Required
Issue/PR number	Argument (e.g., /triage 10, /triage pr 13)	No, omit to triage all open
Mode	pr prefix for PRs	No, defaults to issues
Repo	Auto-detected from git remote	Yes (auto)
gh CLI	"/c/Program Files/GitHub CLI/gh.exe" on Windows, gh elsewhere	Yes (auto)

Execution Protocol

Phase 0, Environment Setup