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

Official agent skill

Investigating Pull Request

by dotnet in dotnet/docker-tools

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

OfficialMITAuto-check passedDevelopment

Install Investigating Pull Request

skills CLI
$ npx skills add dotnet/docker-tools --skill investigating-pull-request -a claude-code

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

GitHub CLI
$ gh skill install dotnet/docker-tools investigating-pull-request --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/investigating-pull-request .claude/skills/investigating-pull-request && 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
investigating-pull-request
GitHub stars
181
Token cost
~318 tokens
SKILL.md length
89 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

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

  • The user wants to check the status of a pull request
  • SKILL.md covers How to view pull request context, How to view pull request… and How to read Azure Pipelines logs
  • Calls pwsh
  • Diagnose PR validation failures

What it does

Investigating Pull Request is an agent skill from dotnet/docker-tools, published by the product's own GitHub organization. Inspect GitHub pull request status, read review comments, and diagnose PR validation failures. Use when the user wants to check the status of a pull request or diagnose PR validation failures.

Its SKILL.md is about 320 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. It works with GitHub. 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

  • The user wants to check the status of a pull request
  • Diagnose PR validation failures

Example prompts

  • “/investigating-pull-request”

Requirements

  • Docker

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:

    • pwsh

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

  • Network

    No URLs in SKILL.md.

    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

Investigating Pull Request loads about 318 tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 89 words of instructions outside code blocks.

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

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). 89 words, ~318 tokens.

Download SKILL.mdSave it as .claude/skills/investigating-pull-request/SKILL.md (or your agent's skills folder).
name
investigating-pull-request
description
Inspect GitHub pull request status, read review comments, and diagnose PR validation failures. Use when the user wants to check the status of a pull request or diagnose PR validation failures.

Investigating GitHub pull requests

This document contains useful patterns for inspecting a single GitHub pull request.

How to view pull request context

Use Show-PullRequestComments.ps1 to view all pull request comments, review decisions, issue comments, review submissions, and inline review comments.

shell
pwsh ./eng/docker-tools/skill-helpers/Show-PullRequestComments.ps1 $prNumber [-Repo "$owner/$repo"]

How to view pull request checks and logs

Use Show-PullRequestBuilds.ps1 to view the GitHub status check summary, including a detailed view of Azure Pipelines build checks.

shell
pwsh ./eng/docker-tools/skill-helpers/Show-PullRequestBuilds.ps1 -PullRequest $prNumber [-Repo "$owner/$repo"]

How to read Azure Pipelines logs

First, get the log ID from the build timeline. Then, use Get-BuildLog.ps1 to print the full log:

shell
pwsh ./eng/docker-tools/skill-helpers/Get-BuildLog.ps1 -Organization dnceng-public -Project public -BuildId $buildId -LogId $logId

© 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/investigating-pull-request of dotnet/docker-tools.

Open the folder on GitHubat commit fa471a5

Compare with similar skills

Investigating Pull Request 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.

Investigating Pull Request compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Investigating Pull Request this skilldotnet/docker-tools181—~318Automated 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
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Pull Request Title and Body Writeropeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • 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

  • 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

  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed

  • GitHub Review Iteration

    prisma/orm

    Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated today
    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 today
    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 today
    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 today
    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 today
    Auto-check passed

  • Triaging Pull Requests

    dotnet/docker-tools

    Official

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

    181 GitHub stars~510 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Investigating Pull Request

What does Investigating Pull Request do?

Inspect GitHub pull request status, read review comments, and diagnose PR validation failures. Investigating Pull Request is an agent skill from dotnet/docker-tools, published by the product's own GitHub organization. Inspect GitHub pull request status, read review comments, and diagnose PR validation failures.

When should I use Investigating Pull Request?

Investigating Pull Request fits situations like: the user wants to check the status of a pull request; diagnose PR validation failures.

How do I install Investigating Pull Request in Claude Code?

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

How do I install Investigating Pull Request in Codex?

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

Can I use Investigating Pull Request 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 investigating-pull-request -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/investigating-pull-request, .gemini/skills/investigating-pull-request, .github/skills/investigating-pull-request and .opencode/skills/investigating-pull-request in your project.

What does Investigating Pull Request need to run?

Going by SKILL.md and its folder, Investigating Pull Request needs the command-line tools its instructions call (pwsh). Our summary lists: Docker.

Does Investigating Pull Request access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Investigating Pull Request 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 Investigating Pull Request use?

Investigating Pull Request 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 Investigating Pull Request use?

About 318 tokens (SKILL.md is roughly 1.3k 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 Investigating Pull Request?

Skills that share tags, products or a category with Investigating Pull Request: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Investigating Pull Request?

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.