New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Triage PRs

by uw-syfi in uw-syfi/vibesys

Triage the open pull requests of the VibeSys repository. An agent skill from uw-syfi/vibesys.

MITAuto-check passedDevelopment

Install Triage PRs

skills CLI
$ npx skills add uw-syfi/vibesys --skill triage-prs -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install uw-syfi/vibesys triage-prs --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/uw-syfi/vibesys.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/triage-prs .claude/skills/triage-prs && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
triage-prs
GitHub stars
108
Token cost
~1.2k tokens
SKILL.md length
600 words
Files
4 (incl. scripts, references)
Skills in repo
15
Repo updated
First seen
Licence
MIT

At a glance

Triage the open pull requests of the VibeSys repository. An agent skill from uw-syfi/vibesys.

  • Works in 7 steps: Resolve scope and write permissions. → Collect signals. → Classify. → …
  • A user asks to triage
  • SKILL.md covers Overview, Workflow and Boundaries
  • Runs Shell scripts from its folder; calls gh

What it does

Triage PRs is an agent skill from uw-syfi/vibesys. Triage the open pull requests of the VibeSys repository. Inventory them, classify each by readiness (CI, merge conflicts, draft state, review state, stack position, PR template compliance, staleness), decide whether the author or a reviewer acts next, optionally apply routine labels such as bug, and report a prioritized maintainer queue. Use when a user asks to triage, prioritize, sort, summarize, or check the status of open PRs, find what is ready to merge or review, what is stale or blocked, what needs author…

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts and reference files (for example `agents/openai.yaml`, `references/triage-signals.md` and `scripts/pr_inventory.sh`).

It sits in Development, covering Pull requests and Git workflow. The repository describes itself as: Can AI Agents Build Bespoke Systems? The licence is MIT.

When your agent uses it

  • A user asks to triage
  • Check the status of open PRs
  • Find what is ready to merge
  • What needs author action

Example prompts

  • “/triage-prs”

Requirements

  • A Bash shell

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Resolve scope and write permissions.
  2. Collect signals.
  3. Classify.
  4. Run the cross-PR checks: overlapping files between open PRs, shared
  5. Estimate review effort per PR from the logical change, not the diff
  6. Apply requested writes.
  7. Report using the template in the reference. Lead with the maintainer's

What it can do on your machine

Read from SKILL.md and the folder at commit 999938a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Triage PRs loads about 1.2k tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 139 tokens; SKILL.md has 600 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~139
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from uw-syfi/vibesys at commit 999938a, republished under its MIT licence (© uw-syfi). 600 words, ~1,187 tokens.

Download SKILL.mdSave it as .claude/skills/triage-prs/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
triage-prs
description
Triage the open pull requests of the VibeSys repository. Inventory them, classify each by readiness (CI, merge conflicts, draft state, review state, stack position, PR template compliance, staleness), decide whether the author or a reviewer acts next, optionally apply routine labels such as bug, and report a prioritized maintainer queue. Use when a user asks to triage, prioritize, sort, summarize, or check the status of open PRs, find what is ready to merge or review, what is stale or blocked, what needs author action, or to label open PRs.

Triage PRs

Overview

Produce a maintainer's action queue for the open pull requests, not a review of each one. Classify from GitHub signals and PR bodies, then delegate deep code review of individual PRs to the review-pr skill when the user selects them.

Workflow

  1. Resolve scope and write permissions.

    • Default to a read-only report. Labels, comments, review requests, closing, readiness changes, and project fields are writes and need an explicit user request. "Tag bug fixes with bug" or "label feature PRs" is such a request.
    • Confirm the repository with gh repo view --json nameWithOwner. Do not switch branches or fetch PR heads; triage never needs a checkout.
    • Restrict to a subset (author, label, path, PR list) when the user names one.

  2. Collect signals.

    • Run scripts/pr_inventory.sh from this skill directory. It prints one JSON object per open PR with CI, mergeability, review, stack, template, and closing-issue signals. Field meanings are in references/triage-signals.md.
    • Re-query PRs whose mergeable is UNKNOWN after a short wait. GitHub computes mergeability lazily.
    • For PRs whose bucket depends on review content, read the latest maintainer comment or review with gh pr view N --comments. Findings in this repository are often plain comments with [P0] to [P3] prefixes.
    • Read the Problem section of each PR body. Do not read diffs except to resolve a classification question, such as whether a change is a bug fix or a refactor.

  3. Classify.

    • Assign exactly one bucket per PR using the precedence in references/triage-signals.md: blocked, needs-author, draft, stale, ready-to-merge, needs-review.
    • Record the concrete blocker: failing check names, conflict, unanswered findings, missing template section, open predecessor PR.
    • Decide who acts next. Trust waiting_on unless the latest comment shows otherwise.

  4. Run the cross-PR checks: overlapping files between open PRs, shared commits, stacks that are claimed in the body but based on trunk, split series and their order, superseded work, and large PRs with no review.

  5. Estimate review effort per PR from the logical change, not the diff size. Use size, large_files, and bulk_lines from the inventory and the rules in the reference. A mechanical rename, a regenerated schema, a recorded fixture, or a vendored source tree inflates the diff without adding review work; say so in the report.

  6. Apply requested writes.

    • Labeling: follow the label rules in the reference. Ground bug in the PR's Problem section or a closing issue labeled bug; ground enhancement in a Solution that adds capability or a surface, and refactor in a stated absence of behavior change. Skip borderline cases and list them for the user.
    • Before any comment, close, or review request, restate exactly which PRs are affected. Never close or mark ready without a per-PR instruction.
    • Re-read each edited PR with gh pr view N --json labels and report the result.

  7. Report using the template in the reference. Lead with the maintainer's ordered actions, then the queue table, cross-PR notes, and writes made. End with the recommended review sequence: small targeted PRs first, then old PRs that need a close or follow-up decision, then stacks bottom-up, then larger work ordered by what it unblocks, with drafts and blocked PRs as a watch list. State anything not verified after the sequence.

Show full SKILL.md (71 more words)Show less

Boundaries

  • Triage judges readiness and ownership, not code quality. Say "needs review" rather than guessing whether the code is correct.
  • Do not count passing checks as evidence of correctness; the queue tells the maintainer where to spend review time.
  • Report unverified state (transient UNKNOWN mergeability, missing token scopes for the project board, CI that has not run) instead of filling it in.
  • Do not expose credentials, private logs, or sensitive paths.

© uw-syfi, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts, references) in .agents/skills/triage-prs of uw-syfi/vibesys.

  • SKILL.md
  • agents/openai.yaml
  • references/triage-signals.md
  • scripts/pr_inventory.sh

Open the folder on GitHubat commit 999938a

Compare with similar skills

Triage PRs next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Triage PRs compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Triage PRs this skilluw-syfi/vibesys108—~1.2kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Git Branch Namingmakeplane/plane61k—~594Automated safety check: PassAGPL-3.0
Create Pull Request with Work Item IDmakeplane/plane61k—~824Automated safety check: PassAGPL-3.0

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Git Branch Naming

    makeplane/plane

    Names a new Git branch with a type prefix, the lowercased work item ID and a short kebab-case description, so the ID can be extracted later from the branch name.

    61k GitHub stars~594 tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Create Pull Request with Work Item ID

    makeplane/plane

    Opens a pull request for the current branch using the repo's template, a work item ID in the title and a description filled in from the actual diff.

    61k GitHub stars~824 tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    105k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes

More from uw-syfi/vibesys

All 15 skills in this repo

  • Neuron Nki Profiling

    uw-syfi/vibesys

    This skill guides using the cli to generate NKI kernel profiles (NEFF + NTFF pairs) to analyze performance on Neuron hardware.

    108 GitHub stars~3.2k tokensUpdated today
    Auto-check passed

  • Neuron Nki Debugging

    uw-syfi/vibesys

    This skill guides debugging NKI compilation errors on Neuron hardware.

    108 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

  • Neuron Nki Docs

    uw-syfi/vibesys

    Research NKI documentation for API lookups, tutorials, error codes, architecture, and optimization guides.

    108 GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Neuron Nki Profile Querying

    uw-syfi/vibesys

    Query and analyze NKI kernel profile data from neuron-explorer parquet files.

    108 GitHub stars~4.3k tokensUpdated today
    Auto-check passed

  • Neuron Nki Writing

    uw-syfi/vibesys

    Guide for writing and modifying NKI kernels. An agent skill from uw-syfi/vibesys.

    108 GitHub stars~5k tokensUpdated today
    Auto-check passed

  • Open PR

    uw-syfi/vibesys

    Prepare and open VibeSys pull requests from local repo changes.

    108 GitHub stars~2.8k tokensUpdated today
    Auto-check passed

Categories

Questions about Triage PRs

What does Triage PRs do?

Triage the open pull requests of the VibeSys repository. An agent skill from uw-syfi/vibesys. Triage PRs is an agent skill from uw-syfi/vibesys. Triage the open pull requests of the VibeSys repository.

When should I use Triage PRs?

Triage PRs fits situations like: A user asks to triage; check the status of open PRs; find what is ready to merge; what needs author action.

How do I install Triage PRs in Claude Code?

Run `npx skills add uw-syfi/vibesys --skill triage-prs -a claude-code`. Or copy the skill folder (.agents/skills/triage-prs in uw-syfi/vibesys) into .claude/skills/triage-prs in your project. Claude Code loads it when a task matches its description.

How do I install Triage PRs in Codex?

Run `npx skills add uw-syfi/vibesys --skill triage-prs -a codex`. Or copy the skill folder (.agents/skills/triage-prs in uw-syfi/vibesys) into .agents/skills/triage-prs in your project. Codex loads it when a task matches its description.

Can I use Triage PRs in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add uw-syfi/vibesys --skill triage-prs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/triage-prs, .gemini/skills/triage-prs, .github/skills/triage-prs and .opencode/skills/triage-prs in your project.

What does Triage PRs need to run?

Going by SKILL.md and its folder, Triage PRs needs a shell for the scripts in its folder and the command-line tools its instructions call (gh). Our summary lists: A Bash shell.

Does Triage PRs access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Triage PRs safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Triage PRs use?

Triage PRs is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Triage PRs use?

About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.5k tokens, read only when the agent opens those files.

What are the alternatives to Triage PRs?

Skills that share tags, products or a category with Triage PRs: Finishing a Development Branch (obra/superpowers, 297k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars) and Git Branch Naming (makeplane/plane, 61k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Triage PRs?

uw-syfi (a GitHub organization) maintains it in uw-syfi/vibesys, which has 108 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 11, 2026.

Source: uw-syfi/vibesys on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.