openvmm-ci-investigation Skill
Investigate CI failures on OpenVMM PRs. Load when a PR has failing CI checks, you need to download and analyze test artifacts, or you need to diagnose build, fmt, clippy, or VMM test failures. Published by microsoft in openvmm.
Decision snapshot
Is this a fit?
Testing, Documentation, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is openvmm-ci-investigation Skill?
Investigate CI failures on OpenVMM PRs. Load when a PR has failing CI checks, you need to download and analyze test artifacts, or you need to diagnose build, fmt, clippy, or VMM test failures. Published by microsoft in openvmm. 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. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Documentation
- Testing use cases
- Documentation use cases
Declared skill metadata
- Source file: .github/skills/openvmm-ci-investigation/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use openvmm-ci-investigation Skill
- Use it for testing.
- Use it for documentation.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/openvmm
- Skill file: .github/skills/openvmm-ci-investigation/SKILL.md
What it does
Investigate CI failures on OpenVMM PRs. Load when a PR has failing CI checks, you need to download and analyze test artifacts, or you need to diagnose build, fmt, clippy, or VMM test failures.
Skill instructions
Investigating CI Failures When a PR has failing CI checks, always start by running the investigation script. Do not manually query the GitHub API or download artifacts by hand — the script handles all of that automatically. Step 1: Run the Script bash Investigate the current branch's PR (no argument needed) python3 reposupport/investigateci.py Investigate a specific PR by number python3 reposupport/investigateci.py 2946 Or by run ID directly python3 reposupport/investigateci.py 23017249697 The script automatically: 1. Resolves the PR to every failed CI run for its head commit. A commit can have multiple workflows (e.g. "OpenVMM PR" and "OpenVMM Docs PR"), and each failing one is investigated in turn — so don't assume a single run covers everything. Only the newest run of each workflow is used, so superseded runs are ignored; a NOTE: <workflow is still inprogress line means results are incomplete and more failures may appear later. 2. Identifies failed jobs 3. Downloads -unit-tests-juni
Verified compatibility and discovery
Frequently asked questions
What is openvmm-ci-investigation?
openvmm-ci-investigation is a open-source AI agent skill with Copy skill directory. Investigate CI failures on OpenVMM PRs. Load when a PR has failing CI checks, you need to download and analyze test artifacts, or you need to diagnose build, fmt, clippy, or VMM test failures.
Who is openvmm-ci-investigation best for?
openvmm-ci-investigation is best for reusing agent instructions, scripts, and references, testing workflows, documentation workflows.
How do I install openvmm-ci-investigation?
Install or run openvmm-ci-investigation using Copy skill directory. Check openvmm-ci-investigation for the latest setup command.
Is openvmm-ci-investigation actively maintained?
openvmm-ci-investigation may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
