test-reporting-triage-skill

Categorize test failures and generate actionable reports with owner assignments.

5|Updated Dec 31, 2025

Search Tags:#ci-cd #test-failures #test-analysis #failure-triage #qa-reporting #owner-suggestions

Ready to run

npx skills add https://github.com/patricio0312rev/skillset --skill test-reporting-triage-skill-patricio0312rev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-reporting-triage-skill
Source: https://github.com/patricio0312rev/skillset/tree/main/templates/testing/test-reporting-triage-skill
Command: npx skills add https://github.com/patricio0312rev/skillset --skill test-reporting-triage-skill-patricio0312rev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically triages test failures by categorizing issues, suggesting responsible owners, and generating actionable failure reports to accelerate debugging and accountability.

Core Features & Use Cases

Failure Categorization: automatically classifies failures into categories such as timeout, network, database, authentication, assertion, and more.
Failure Analysis & Ownership: proposes owners and actionable fixes based on error context and stack traces.
Report & Dashboards: produces markdown reports and Slack-ready summaries to communicate results to teams.
CI/Automation Integration: integrates with CI pipelines to collect results, generate reports, and optionally file issues or notify on failures.

Quick Start

Initialize the test-triage skill in your project to automatically categorize failures, assign owners, and generate a failure report from your test results.

Frequently Asked Questions about test-reporting-triage-skill

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

FAQPage Schema

How do I automate test failure triage in my CI pipeline?▼

You can automate test failure triage in a CI pipeline by integrating a skill that collects test results, categorizes failures by type, suggests responsible owners, and generates actionable reports. It applies across frontend and backend stacks.

What is the best way to categorize test failures and assign owners?▼

Categorizing test failures and assigning owners is best handled by analyzing error context and stack traces to automatically classify issues like timeouts or network errors, proposing actionable fixes and responsible team members.

Can I generate Slack-ready test failure reports from local test runs?▼

Yes, you can generate Slack-ready summaries and markdown reports from local test runs. The skill analyzes failure context to produce dashboards and structured results for immediate team communication.

Does automated failure analysis work with both frontend and backend stacks?▼

Automated failure analysis works with both frontend and backend stacks. It triages test failures across diverse environments, including local test runs, monitoring dashboards, and CI pipelines, without stack-specific limitations.

How do I categorize CI/CD test failures into timeouts, network, and database issues?▼

To categorize CI/CD test failures into timeouts, network, and database issues, apply an automated triage process that classifies failures based on error context and stack traces, generating structured results for quick debugging.

How do I create a fix checklist from automated test failure reports?▼

You can create a fix checklist from automated test failure reports by using a triage skill that analyzes stack traces to propose actionable fixes and responsible owners, satisfying accountability and debugging requirements.