test-result-analyzer

Classify test failures into BUG, FLAKY, ENVIRONMENT, TEST-DEFECT, or UNCLASSIFIED with RTM linkage.

1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/mytechsonamy/VibeFlow --skill test-result-analyzer-mytechsonamy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-result-analyzer
Source: https://github.com/mytechsonamy/VibeFlow/tree/main/skills/test-result-analyzer
Command: npx skills add https://github.com/mytechsonamy/VibeFlow --skill test-result-analyzer-mytechsonamy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill decodes a pile of test failures from a primary report and translates them into structured, prioritized classifications that downstream partners can act on.

Core Features & Use Cases

  • Classification: label each failure as BUG, FLAKY, ENVIRONMENT, TEST-DEFECT, or UNCLASSIFIED to enforce governance and triage.
  • RTM & Traceability: link failures to RTM requirements when scenario-set.md and rtm.md are provided.
  • Ticket Generation: produce ready-to-import backlog tickets for bugs with confidence above threshold and detailed evidence.

Quick Start

Classify the latest run's failures by pointing at the primary report and optional RTM data to generate test results and tickets.

Frequently Asked Questions about test-result-analyzer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I classify test failures from a CI-CD report into structured bug categories?

To classify test failures, this Skill analyzes a primary test report and labels each failure into a taxonomy of BUG, FLAKY, ENVIRONMENT, TEST-DEFECT, or UNCLASSIFIED. It outputs structured classifications into .vibeflow/reports to support triage.

Can I link test failures to PRD requirements and downstream tickets using RTM?

Yes, you can link test failures to RTM requirements by providing scenario-set.md and rtm.md files. The Skill applies RTM linkage to map failures to PRD requirements and generates ready-to-import backlog tickets for downstream ticketing.

How do I automate bug ticket generation from test results above a confidence threshold?

Automated bug ticket generation works by classifying test failures and producing ticket templates for bugs with confidence above threshold. The Skill emits these ready-to-import tickets alongside detailed evidence in .vibeflow/reports for human triage.

What is the difference between a flaky test and a test defect when triaging test results?

The difference is determined by classifying test results into a taxonomy where FLAKY indicates intermittent test failures and TEST-DEFECT identifies issues within the test logic itself. The Skill applies this classification to enforce governance and separate actionable bugs from test issues.

Does test result classification require any specific dependencies or environment setup?

No specific dependencies are required to run test result classification. The Skill operates on a single primary test report as input, while RTM and traceability features are optional enhancements activated only when scenario-set.md and rtm.md are present.

Why are some of my test failures marked as UNCLASSIFIED instead of a specific bug category?

Test failures are marked as UNCLASSIFIED when the analyzer lacks sufficient evidence to confidently label them as BUG, FLAKY, ENVIRONMENT, or TEST-DEFECT. This prevents incorrect automated ticketing and routes ambiguous failures for manual human triage.