New: 97,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

Official agent skill

Triaging Pull Requests

by dotnet in dotnet/docker-tools

Triage open pull requests into actionable categories. An agent skill from dotnet/docker-tools.

OfficialMITAuto-check passedDevelopment

Install Triaging Pull Requests

skills CLI
$ npx skills add dotnet/docker-tools --skill triaging-pull-requests -a claude-code

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

GitHub CLI
$ gh skill install dotnet/docker-tools triaging-pull-requests --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/dotnet/docker-tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/triaging-pull-requests .claude/skills/triaging-pull-requests && 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
triaging-pull-requests
GitHub stars
181
Token cost
~510 tokens
SKILL.md length
300 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

Triage open pull requests into actionable categories. An agent skill from dotnet/docker-tools.

  • Works in 5 steps: List open pull requests → Categorize pull requests → Investigate failures → …
  • Tasks that involve Pull requests
  • Calls gh

What it does

Triaging Pull Requests is an agent skill from dotnet/docker-tools, published by the product's own GitHub organization. Triage open pull requests into actionable categories.

Its SKILL.md is about 510 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. The repository describes itself as: This is a repo to house some common tools for our various docker repos. The licence is MIT.

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “/triaging-pull-requests”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. List open pull requests
  2. Categorize pull requests
  3. Investigate failures
  4. Correlate failures with recent pull requests and issues
  5. Categorize and present results

What it can do on your machine

Read from SKILL.md and the folder at commit fa471a5. 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

    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

Triaging Pull Requests loads about 510 tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 300 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~19
When it runs · the whole SKILL.md, loaded when a task matches
~510

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from dotnet/docker-tools at commit fa471a5, republished under its MIT licence (© dotnet). 300 words, ~510 tokens.

Download SKILL.mdSave it as .claude/skills/triaging-pull-requests/SKILL.md (or your agent's skills folder).
name
triaging-pull-requests
description
Triage open pull requests into actionable categories.

Workflow

Step 1: List open pull requests

List open pull requests by running gh pr list.

Step 2: Categorize pull requests

Read the contents of pull requests using gh pr view. For any pull request that needs deeper status, review, comment, or CI context, use the investigating-pull-request skill.

Categorize each pull request into one of the following buckets:

  • Ready to merge
  • Needs review
  • PR validation failing
  • Needs follow-up
  • Draft
Step 3: Investigate failures

For failing pull requests, use the investigating-pull-request skill to gather their full context and check their CI status.

For pull requests with CI failures, use the investigating-pipeline skill with the failing build ID to read task logs and identify root causes.

Step 4: Correlate failures with recent pull requests and issues

To check recent issues, run gh issue list --state all. To check recently merged pull requests, run gh pr list --state merged.

Look for:

  • A recent change that obviously caused the failure
  • An existing known issue tracking this failure
  • An open pull request that already addresses the failure
Step 5: Categorize and present results

Using everything you've learned, place each pull request into one of these categories in this priority order:

  1. Ready to Merge — Approved, CI passing, no merge conflicts
  2. Needs Review — The current user is a requested reviewer
  3. Needs Author Action — Changes requested, CI failing, or merge conflicts
  4. Stale — No updates in 7+ days and not ready to merge

Use your judgment when things are ambiguous. For example:

  • A pull request with only flaky-test failures might still be ready to merge
  • A draft pull request from the user that hasn't been touched in weeks is stale even if CI is green

For "Needs Author Action" pull requests with CI failures, include the root cause diagnosis.

End with a recommended next action.

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

Files

Just SKILL.md in .github/skills/triaging-pull-requests of dotnet/docker-tools.

Open the folder on GitHubat commit fa471a5

Compare with similar skills

Triaging Pull Requests 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.

Triaging Pull Requests compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Triaging Pull Requests this skilldotnet/docker-tools181—~510Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Understand Diff AnalysisEgonex-AI/Understand-Anything85k1 repos~1.4kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT

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.

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

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    85k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed

  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    90k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

More from dotnet/docker-tools

  • Investigating Pipeline

    dotnet/docker-tools

    Official

    Diagnoses a single Azure Pipelines build. An agent skill from dotnet/docker-tools.

    181 GitHub stars~259 tokensUpdated yesterday
    Auto-check passed

  • Investigating Pull Request

    dotnet/docker-tools

    Official

    Inspect GitHub pull request status, read review comments, and diagnose PR validation failures.

    181 GitHub stars~318 tokensUpdated yesterday
    Auto-check passed

  • Reviewing Csharp

    dotnet/docker-tools

    Official

    Reviews C changes in the ImageBuilder codebase against the repo's modern C conventions and invariants.

    181 GitHub stars~793 tokensUpdated yesterday
    Auto-check passed

  • Triaging Pipelines

    dotnet/docker-tools

    Official

    Triage recent Azure Pipelines runs and failures. An agent skill from dotnet/docker-tools.

    181 GitHub stars~248 tokensUpdated yesterday
    Auto-check passed

  • Docs Maintenance

    dotnet/docker-tools

    Official

    Reviews or updates repository documentation as a dedicated task after implementation is complete.

    181 GitHub stars~1k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Triaging Pull Requests

What does Triaging Pull Requests do?

Triage open pull requests into actionable categories. An agent skill from dotnet/docker-tools. Triaging Pull Requests is an agent skill from dotnet/docker-tools, published by the product's own GitHub organization. Triage open pull requests into actionable categories.

When should I use Triaging Pull Requests?

Triaging Pull Requests fits situations like: tasks that involve Pull requests.

How do I install Triaging Pull Requests in Claude Code?

Run `npx skills add dotnet/docker-tools --skill triaging-pull-requests -a claude-code`. Or copy the skill folder (.github/skills/triaging-pull-requests in dotnet/docker-tools) into .claude/skills/triaging-pull-requests in your project. Claude Code loads it when a task matches its description.

How do I install Triaging Pull Requests in Codex?

Run `npx skills add dotnet/docker-tools --skill triaging-pull-requests -a codex`. Or copy the skill folder (.github/skills/triaging-pull-requests in dotnet/docker-tools) into .agents/skills/triaging-pull-requests in your project. Codex loads it when a task matches its description.

Can I use Triaging Pull Requests 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 dotnet/docker-tools --skill triaging-pull-requests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/triaging-pull-requests, .gemini/skills/triaging-pull-requests, .github/skills/triaging-pull-requests and .opencode/skills/triaging-pull-requests in your project.

What does Triaging Pull Requests need to run?

Going by SKILL.md and its folder, Triaging Pull Requests needs the command-line tools its instructions call (gh).

Does Triaging Pull Requests 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 Triaging Pull Requests 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. Review the folder before installing.

What licence does Triaging Pull Requests use?

Triaging Pull Requests 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 Triaging Pull Requests use?

About 510 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Triaging Pull Requests?

Skills that share tags, products or a category with Triaging Pull Requests: Finishing a Development Branch (obra/superpowers, 296k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 85k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Triaging Pull Requests?

dotnet (a GitHub organization, an official publisher) maintains it in dotnet/docker-tools, which has 181 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 7, 2026.

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