pipeline-test-triage Skill
Triage test failures in an Azure DevOps pipeline run for Fluid Framework. Use when the user shares an ADO build/pipeline URL or build ID and wants failures analyzed, when they ask "why did this pipeline fail", "summarize the test failures", "is this test flaky or a real bug", "compare these runs", or wants bugs filed f Published by microsoft in FluidFramework.
What is pipeline-test-triage Skill?
Triage test failures in an Azure DevOps pipeline run for Fluid Framework. Use when the user shares an ADO build/pipeline URL or build ID and wants failures analyzed, when they ask "why did this pipeline fail", "summarize the test failures", "is this test flaky or a real bug", "compare these runs", or wants bugs filed f Published by microsoft in FluidFramework. 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
- Browser automation
- Testing
- Deployment
- Browser automation use cases
- Testing use cases
Technical details
- Install or run with Copy skill directory
When to use pipeline-test-triage Skill
- Use it for browser automation.
- Use it for testing.
- Use it for deployment.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/FluidFramework
- Skill file: .claude/skills/pipeline-test-triage/SKILL.md
What it does
Triage test failures in an Azure DevOps pipeline run for Fluid Framework. Use when the user shares an ADO build/pipeline URL or build ID and wants failures analyzed, when they ask "why did this pipeline fail", "summarize the test failures", "is this test flaky or a real bug", "compare these runs", or wants bugs filed f
Skill instructions
Pipeline Test Triage Analyze test failures for a given ADO pipeline run, classify them (service flakiness vs. infra/harness vs. deterministic product/test bug), compare against adjacent runs to tell flaky from deterministic, and optionally file well-formed ADO bugs for the real ones. Org: fluidframework · Project: internal (work items and pipelines) · Repo on GitHub: microsoft/FluidFramework. --- Prefer the cheapest source that answers the question Reach for the smallest, most-structured source first, and escalate only when it can't answer the question. A single Real Service E2E run has ~660 logs and tens of MB, almost all of which are passing "Container" logs — so bulk-downloading logs works but is the slow, expensive option; treat it as a last resort, not a first move. | Tier | Source | Gets you | Auth | Use when | |------|--------|----------|------|----------| | 1 (primary) | Playwright on the Tests tab | Grouped failures + error/stack + per-test run history | Signed-in browser (one
Explore related resources
Frequently asked questions
What is pipeline-test-triage?
pipeline-test-triage is a open-source AI agent skill with Copy skill directory. Triage test failures in an Azure DevOps pipeline run for Fluid Framework. Use when the user shares an ADO build/pipeline URL or build ID and wants failures analyzed, when they ask "why did this.
Who is pipeline-test-triage best for?
pipeline-test-triage is best for reusing agent instructions, scripts, and references, browser automation workflows, testing workflows, deployment workflows.
How do I install pipeline-test-triage?
Install or run pipeline-test-triage using Copy skill directory. Check pipeline-test-triage for the latest setup command.
Is pipeline-test-triage actively maintained?
pipeline-test-triage may need a closer maintenance check before production use.
Auto-fetched from GitHub.
