build-health Skill
Analyze VS Code rolling build health on Azure DevOps. Use when: the rolling build is red right now, you need a report for the last 100 builds, you need to identify the commit range that broke the build, you are on build champ duty, or you need a build health report. Published by microsoft in vscode-team-kit.
What is build-health Skill?
Analyze VS Code rolling build health on Azure DevOps. Use when: the rolling build is red right now, you need a report for the last 100 builds, you need to identify the commit range that broke the build, you are on build champ duty, or you need a build health report. Published by microsoft in vscode-team-kit. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Deployment
- Documentation
- Data analysis
- Deployment use cases
- Documentation use cases
Technical details
- Install or run with Copy skill directory
When to use build-health Skill
- Use it for deployment.
- Use it for documentation.
- Use it for data analysis.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/vscode-team-kit
- Skill file: build-health/skills/build-health/SKILL.md
What it does
Analyze VS Code rolling build health on Azure DevOps. Use when: the rolling build is red right now, you need a report for the last 100 builds, you need to identify the commit range that broke the build, you are on build champ duty, or you need a build health report.
Skill instructions
Build Health Quickly diagnose the VS Code rolling build (Pipeline 111) on Azure DevOps. This skill has two modes: 1. Fix the build if it is red right now by finding where the red streak started and identifying the compare range from last green to first red. 2. Analyze and present the last 100 builds in a predictable report file. The report file is the primary artifact. Generate it first, summarize what it shows, and only then ask whether the user wants heuristic culprit analysis. When to Use - The rolling build on main is red and you need to find where it broke - You need a stable report for the last 100 builds - You're the build champ and want a quick health overview - You need to separate recurring infra failures from likely code regressions - You want to trace a build break back to a narrow compare range Output Contract Always produce a markdown report file before presenting conclusions. - Default output directory: /tmp/build-health - Default report path: /tmp/build-health/build-hea
Explore related resources
Frequently asked questions
What is build-health?
build-health is a open-source AI agent skill with Copy skill directory. Analyze VS Code rolling build health on Azure DevOps. Use when: the rolling build is red right now, you need a report for the last 100 builds, you need to identify the commit range that broke the build, you.
Who is build-health best for?
build-health is best for reusing agent instructions, scripts, and references, deployment workflows, documentation workflows, data analysis workflows.
How do I install build-health?
Install or run build-health using Copy skill directory. Check build-health for the latest setup command.
Is build-health actively maintained?
build-health may need a closer maintenance check before production use.
Auto-fetched from GitHub.
