Respond To PR Comments
microsoft/PromptKit
Respond to pull request review comments on GitHub or Azure DevOps Services.
Triage recent Azure Pipelines runs and failures. An agent skill from dotnet/docker-tools.
Install Triaging Pipelines
$ npx skills add dotnet/docker-tools --skill triaging-pipelines -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dotnet/docker-tools triaging-pipelines --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/dotnet/docker-tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/triaging-pipelines .claude/skills/triaging-pipelines && rm -rf skills-srcUse ~/.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/
Install the "triaging-pipelines" agent skill from https://github.com/dotnet/docker-tools/tree/main/.github/skills/triaging-pipelines into .claude/skills/triaging-pipelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triaging-pipelines", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/dotnet/docker-tools/tree/main/.github/skills/triaging-pipelinesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add dotnet/docker-tools --skill triaging-pipelines -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dotnet/docker-tools triaging-pipelines --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dotnet/docker-tools.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/triaging-pipelines .agents/skills/triaging-pipelines && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "triaging-pipelines" agent skill from https://github.com/dotnet/docker-tools/tree/main/.github/skills/triaging-pipelines into .agents/skills/triaging-pipelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triaging-pipelines", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dotnet/docker-tools --skill triaging-pipelines -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dotnet/docker-tools triaging-pipelines --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dotnet/docker-tools.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/triaging-pipelines .cursor/skills/triaging-pipelines && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "triaging-pipelines" agent skill from https://github.com/dotnet/docker-tools/tree/main/.github/skills/triaging-pipelines into .cursor/skills/triaging-pipelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triaging-pipelines", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/dotnet/docker-tools.git --path .github/skills/triaging-pipelines--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add dotnet/docker-tools --skill triaging-pipelines -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dotnet/docker-tools triaging-pipelines --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dotnet/docker-tools.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/triaging-pipelines .gemini/skills/triaging-pipelines && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "triaging-pipelines" agent skill from https://github.com/dotnet/docker-tools/tree/main/.github/skills/triaging-pipelines into .gemini/skills/triaging-pipelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triaging-pipelines", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install dotnet/docker-tools triaging-pipelinesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add dotnet/docker-tools --skill triaging-pipelines -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dotnet/docker-tools.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/triaging-pipelines .github/skills/triaging-pipelines && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "triaging-pipelines" agent skill from https://github.com/dotnet/docker-tools/tree/main/.github/skills/triaging-pipelines into .github/skills/triaging-pipelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triaging-pipelines", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dotnet/docker-tools --skill triaging-pipelines -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dotnet/docker-tools triaging-pipelines --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dotnet/docker-tools.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/triaging-pipelines .opencode/skills/triaging-pipelines && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "triaging-pipelines" agent skill from https://github.com/dotnet/docker-tools/tree/main/.github/skills/triaging-pipelines into .opencode/skills/triaging-pipelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triaging-pipelines", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
triaging-pipelines- GitHub stars
- 181
- Token cost
- ~248 tokens
- SKILL.md length
- 116 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- MIT
At a glance
Triage recent Azure Pipelines runs and failures. An agent skill from dotnet/docker-tools.
- Works in 3 steps: List recent builds → Investigate failures → Correlate failures with recent pull…
- Tasks that involve Pull requests
- Calls gh and pwsh
What it does
Triaging Pipelines is an agent skill from dotnet/docker-tools, published by the product's own GitHub organization. Triage recent Azure Pipelines runs and failures.
Its SKILL.md is about 250 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 Azure DevOps. 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-pipelines”
Requirements
- Docker
Workflow steps
3 steps, taken from the step headings in SKILL.md.
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:
ghpwsh
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 Pipelines loads about 248 tokens when it runs. Until then it costs about 17 tokens; SKILL.md has 116 words of instructions outside code blocks.
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). 116 words, ~248 tokens.
Download SKILL.mdSave it as
.claude/skills/triaging-pipelines/SKILL.md (or your agent's skills folder).- name
- triaging-pipelines
- description
- Triage recent Azure Pipelines runs and failures.
Workflow
Step 1: List recent builds
pwsh ./eng/docker-tools/skill-helpers/Get-RecentBuilds.ps1 -Organization dnceng -Project internal -Folder dotnet/docker-tools -Hours 24Change the value of -Hours to list more or fewer builds.
Step 2: Investigate failures
For any build whose state is failed, partiallySucceeded, or canceled, use the investigating-pipeline skill to view the build timeline and read failing task logs.
Step 3: Correlate failures with recent pull requests and issues
To check recent issues, run gh issue list --state all.
To check recent pull requests, run gh pr list --state all.
Read the contents of issues and pull requests using the gh CLI if necessary.
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
© 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-pipelines of dotnet/docker-tools.
Open the folder on GitHubat commit fa471a5
Compare with similar skills
Triaging Pipelines 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Triaging Pipelines this skilldotnet/docker-tools | 181 | — | ~248 | Automated safety check: Pass | MIT | |
| Respond To PR Commentsmicrosoft/PromptKit | 110 | — | ~4.2k | Automated safety check: Pass | MIT | |
| PR ReviewJocysCom/FocusLogger | 213 | — | ~12k | Automated safety check: Warn | GPL-3.0 | |
| PR Screenshotsgithub/awesome-copilot | 40k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Create PR Azdooocx/tfplan2md | 174 | — | ~665 | Automated safety check: Pass | MIT | |
| Azure DevopsOpenHands/extensions | 158 | — | ~979 | Automated safety check: Pass | MIT |
Similar skills
- Official
PR Review
JocysCom/FocusLogger
AI-assisted pull request review workflow for Azure DevOps Git repositories.
- Official
PR Screenshots
github/awesome-copilot
Embed before/after screenshots and annotated images in pull request descriptions.
Create PR Azdo
oocx/tfplan2md
Create an Azure DevOps pull request using az devops tooling; include the repo’s linear-history merge preference and ask the Maintainer if merge options differ.
Azure Devops
OpenHands/extensions
Interact with Azure DevOps repositories, pull requests, and APIs using the AZUREDEVOPSTOKEN environment variable.
Pp Azure Devops
mvanhorn/printing-press-library
The fastest Azure DevOps CLI — offline-first, agent-native Trigger phrases: show my Azure DevOps work items, check my ADO pull requests, what's the sprint velocity, which PRs need my review, check…
More from dotnet/docker-tools
- Official
Investigating Pipeline
dotnet/docker-tools
Diagnoses a single Azure Pipelines build. An agent skill from dotnet/docker-tools.
- Official
Investigating Pull Request
dotnet/docker-tools
Inspect GitHub pull request status, read review comments, and diagnose PR validation failures.
- Official
Reviewing Csharp
dotnet/docker-tools
Reviews C changes in the ImageBuilder codebase against the repo's modern C conventions and invariants.
- Official
Docs Maintenance
dotnet/docker-tools
Reviews or updates repository documentation as a dedicated task after implementation is complete.
- Official
Triaging Pull Requests
dotnet/docker-tools
Triage open pull requests into actionable categories. An agent skill from dotnet/docker-tools.
Related
Works with
Categories
Questions about Triaging Pipelines
What does Triaging Pipelines do?
Triage recent Azure Pipelines runs and failures. An agent skill from dotnet/docker-tools. Triaging Pipelines is an agent skill from dotnet/docker-tools, published by the product's own GitHub organization. Triage recent Azure Pipelines runs and failures.
When should I use Triaging Pipelines?
Triaging Pipelines fits situations like: tasks that involve Pull requests.
How do I install Triaging Pipelines in Claude Code?
Run `npx skills add dotnet/docker-tools --skill triaging-pipelines -a claude-code`. Or copy the skill folder (.github/skills/triaging-pipelines in dotnet/docker-tools) into .claude/skills/triaging-pipelines in your project. Claude Code loads it when a task matches its description.
How do I install Triaging Pipelines in Codex?
Run `npx skills add dotnet/docker-tools --skill triaging-pipelines -a codex`. Or copy the skill folder (.github/skills/triaging-pipelines in dotnet/docker-tools) into .agents/skills/triaging-pipelines in your project. Codex loads it when a task matches its description.
Can I use Triaging Pipelines 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-pipelines -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-pipelines, .gemini/skills/triaging-pipelines, .github/skills/triaging-pipelines and .opencode/skills/triaging-pipelines in your project.
What does Triaging Pipelines need to run?
Going by SKILL.md and its folder, Triaging Pipelines needs the command-line tools its instructions call (gh and pwsh). Our summary lists: Docker.
Does Triaging Pipelines 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 Pipelines 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 Pipelines use?
Triaging Pipelines 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 Pipelines use?
About 248 tokens (SKILL.md is roughly 992 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 Pipelines?
Skills that share tags, products or a category with Triaging Pipelines: Respond To PR Comments (microsoft/PromptKit, 110 stars), PR Review (JocysCom/FocusLogger, 213 stars), PR Screenshots (github/awesome-copilot, 40k stars) and Create PR Azdo (oocx/tfplan2md, 174 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Triaging Pipelines?
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.