github triage

Engineering Community

Skill notes

When to Use

When the user runs /github-triage to groom or review a repository's open issues and pull requests. When an issue backlog has drifted: resolved work left open, fixes landed without closing their issues, or PRs in flight that never linked their issue. When ready PRs have piled up (passing dependency bumps, approved-and-green PRs) or

When NOT to Use

Do not invoke automatically. This skill performs irreversible GitHub writes (merging PRs, closing issues, posting comments) and runs only on explicit invocation. Do not use to apply priority/effort labels on GitHub. Priority and size are presented locally only and are never posted (see Safety Rules). Do not use as a substitute for a human's final merge decision — every merge is

Core Principles

Writes are gated. Compute the full triage first, present every proposed write — merges included — for review, and execute nothing until the user approves. Evidence before closing. Never close an issue without a concrete, cited reason (a merged PR or a commit on the default branch). When evidence is weak or ambiguous, leave the issue outstanding and flag it for review.

Phase 0: Select the target repository

Determine the set of distinct GitHub-hosted repositories among the remotes. A remote is GitHub-hosted when its URL host is github.com, in any of these forms: https://github.com/OWNER/REPO(.git) git@github.com:OWNER/REPO(.git) ssh://git@github.com/OWNER/REPO(.git)

Phase 1: Gather issues and context

closingIssuesReferences lists the issues a PR is linked to close — populated by any of GitHub's closing keywords (close/closes/closed, fix/fixes/fixed, resolve/resolves/resolved) in the PR body, or by a manual UI link. It is the strongest available signal. For issues it does not cover, also search commit messages on the default branch. Resolve the default branch authoritatively from the selected

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@trailofbits · no license declared
Token usage
Heavy
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 0: Select the target repository

Determine the set of distinct GitHub-hosted repositories among the remotes. A remote is GitHub-hosted when its URL host is `github.com`, in any of these forms: `https://github.com/OWNER/REPO(.git)` `git@github.com:OWNER/REPO(.git)` `ssh://git@github.com/OWNER/REPO(.git)`

02
Phase 1: Gather issues and context

`closingIssuesReferences` lists the issues a PR is linked to close — populated by any of GitHub's closing keywords (`close`/`closes`/`closed`, `fix`/`fixes`/`fixed`, `resolve`/`resolves`/`resolved`) in the PR body, or by a manual UI link. It is the strongest available signal. For issues it does not cover, also search commit messages on the default branch. Resolve the default branch authoritatively from the selected

03
Phase 2: Triage open pull requests (optional)

Handle PRs before issues: merging ready PRs here means the "already resolved" check in the issue phase sees the work those merges just landed. If there are no open PRs, skip this phase. Otherwise summarize the open PRs and ask the user whether to handle PRs now (AskUserQuestion: handle PRs / skip to issues). If they skip, go straight to issue classification.

04
Phase 3: Classify each open issue

Sort every open issue into exactly one bucket. Bucket A — Already resolved (the work landed, the issue was left open). Requires concrete evidence; prefer corroboration over a single weak signal: A merged PR lists the issue in `closingIssuesReferences`, or its title/body references `#N` alongside a closing keyword. (Strongest.)

05
Phase 4: Score outstanding issues (LOCAL ONLY)

Priority — `Critical` / `High` / `Medium` / `Low`. Weigh: *Impact / severity* — security, data loss, crash, or correctness bugs rank above enhancements; docs/cosmetic rank lowest. Existing labels (`security`, `bug`, `crash`, `regression`) are strong signals. *Reach* — how many users/workflows are affected.

06
Phase 5: Execute approved issue writes

Run each approved write as a separate command so one failure does not block the rest. Report the outcome of each, and continue past failures.

07
Phase 6: Deliver the outstanding triage

Let `K` be the number of outstanding (Bucket C) issues. K ≤ 32 → render the outstanding table directly in the response. K > 32 → offer to save the results to disk instead of printing a large table. Use AskUserQuestion (save to file / print anyway). When saving, write a Markdown file with the Write tool:

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.