debug-test-failures Skill
Systematic debugging workflow for test failures. Use when tests are failing, a CI build is red, or when asked to debug test issues. Published by microsoft in haste.
Decision snapshot
Is this a fit?
Testing, Design and media, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Shell access
Copy skill directory
2 months ago · MIT license
Access note: Shell access.
What is debug-test-failures Skill?
Systematic debugging workflow for test failures. Use when tests are failing, a CI build is red, or when asked to debug test issues. Published by microsoft in haste. 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
- Design and media
- Testing use cases
- Design and media use cases
Declared skill metadata
- Source file: .github/skills/debug-test-failures/SKILL.md
Allowed tools declared by source
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
- Shell access
Requirements and access
Security and permissions
Review permissions before connecting any MCP server to an agent. Pay special attention to whether it can read local files, write data, call external services, or perform destructive actions.
When to use debug-test-failures Skill
- Use it for testing.
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/haste
- Skill file: .github/skills/debug-test-failures/SKILL.md
What it does
Systematic debugging workflow for test failures. Use when tests are failing, a CI build is red, or when asked to debug test issues.
Skill instructions
Debug Test Failures Overview A systematic process for diagnosing and fixing test failures. Use this skill when tests fail, CI is red, or someone reports a broken build. The key principle: find the root cause, not just the symptom. Key Concepts Failure Categories - Deterministic failure: Same result every time. Usually a code bug or outdated test. - Flaky failure: Intermittent. Usually caused by timing, ordering, shared state, or external dependencies. - Environment failure: Works locally, fails in CI. Usually paths, permissions, or missing dependencies. Patterns & Techniques Systematic Debugging Process Step 1: Reproduce Run the failing test in isolation: bash Python tests cd hastelib && hatch run test:pytest UI lint cd ui && npm run lint Run it 2-3 times. If intermittent, it's likely flaky. Step 2: Analyze - Read the error message and stack trace carefully - Identify the assertion that failed: expected vs actual values - Check if the failure is in the test or the code under test Step
Verified compatibility and discovery
Frequently asked questions
What is debug-test-failures?
debug-test-failures is a open-source AI agent skill with Copy skill directory. Systematic debugging workflow for test failures. Use when tests are failing, a CI build is red, or when asked to debug test issues.
Who is debug-test-failures best for?
debug-test-failures is best for reusing agent instructions, scripts, and references, testing workflows, design and media workflows.
How do I install debug-test-failures?
Install or run debug-test-failures using Copy skill directory. Check debug-test-failures for the latest setup command.
Is debug-test-failures actively maintained?
debug-test-failures 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.
