Menu
Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.
Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
npx skills add https://github.com/dotnet/docker-tools --skill triaging-pull-requestsLa commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.
Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.
Reviews or updates repository documentation as a dedicated task after implementation is complete. Use before submitting a pull request or when reviewing a pull request.
Reviews C# changes in the ImageBuilder codebase against the repo's modern C# conventions and invariants. Use when reviewing a C# diff, pull request, or staged/unstaged changes and you want anti-patterns caught before merge.
Diagnoses a single Azure Pipelines build. Shows the build timeline tree with stages, jobs, and task results, and retrieves task logs for debugging failures. Use when a user provides a build ID or Azure DevOps build URL and wants to understand what failed and why.
Basé sur la classification professionnelle SOC
Affichage de SKILL.md
| name | triaging-pull-requests |
| description | Triage open pull requests into actionable categories. |
List open pull requests by running gh pr list.
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:
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.
To check recent issues, run gh issue list --state all.
To check recently merged pull requests, run gh pr list --state merged.
Look for:
Using everything you've learned, place each pull request into one of these categories in this priority order:
Use your judgment when things are ambiguous. For example:
For "Needs Author Action" pull requests with CI failures, include the root cause diagnosis.
End with a recommended next action.
