Skip to content
SkillMixed5,700 tokens in use

github-triage

Triages a repository's open issues and pull requests with gh: gated merges, cited closes, cross-links and local-only priority scoring.

8,319 stars on the repository CC-BY-SA-4.0trailofbits/skills · plugins/github-triage/skills/github-triage
/plugin marketplace add trailofbits/skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing github-triage costs

109tokens idle
5,700tokens in use
6,494tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Mixed

Script-ledMixedModel-led

Scripts do part of the work and the model's judgement does the rest.

This describes the skill's structure, how much of it is scripts. It does not say how well it works. Scripts: .calcifier/recipe.py.

Touches

shelldeclared and detectednetworkdetectedwrites filesdeclared

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter12/15
  • Structure25/25
  • Examples12/15
  • Output15/15
  • Size13/15
  • Resources5/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Reaches the network−10

    does this on the machine, and the frontmatter does not say so

    .calcifier/recipe.py, line 56
  • Runs shell commands−2

    does this on the machine, as the frontmatter declares

    SKILL.md, line 50

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity100
  • Maintenance52
  • Community64
  • Maturity32
  • Momentum40

GitHub Triage grooms a repository’s backlog when you run it. It can merge passing bot PRs and maintainer-approved PRs one at a time, spawn review subagents for PRs nobody has reviewed, close issues that are already resolved with a comment citing the resolving PR or commit, link issues to the open PRs that fix them, and rate everything still outstanding.

Every write to GitHub is shown for approval first. Priority and change-size estimates stay on your machine and are never posted.

What You Get

  • A proposed list of issues to close, each with the merged PR or commit that resolves it
  • Proposed cross-links between issues and the open PRs that fix them
  • Priority (critical to low) and a size bucket from XS to XXL for every outstanding issue, with the basis of the estimate
  • Markdown reviews of never-reviewed PRs saved as local files
  • A saved triage report when more than 32 issues remain

Common Use Cases

  • Clearing a backlog where fixes landed without closing their issues
  • Merging a pile of green Dependabot or Renovate PRs in order
  • Getting a first review of PRs that sit unreviewed
  • Planning a sprint from sized and prioritized open issues

What Makes It Unique

It is built around safe writes. Nothing is closed, commented or merged until you approve the full set. Merges happen one at a time with the PR state re-checked before each, and never with force or auto-merge. Evidence is required for every close, fetched issue text is treated as data and not as instructions, and untrusted text never goes through shell interpolation. Priority and size are never posted to GitHub.

Under The Hood

The skill is prose with a reference file for PR review, and it must be invoked by you. The agent runs gh and git commands in the shell against the repository, reading issues and PRs through the GitHub API with your credentials. After you approve, it can merge PRs, close issues, post comments and edit PR bodies on GitHub. It also reads code to check whether an issue is resolved, dispatches review subagents in parallel, and writes review and report markdown files in the working directory.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers