triage-failures

Group scenario failures by root-cause patterns and create or reopen issues.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Tomoda826/mtg-goldfisher --skill triage-failures
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-failures
Source: https://github.com/Tomoda826/mtg-goldfisher/tree/main/.claude/skills/triage-failures
Command: npx skills add https://github.com/Tomoda826/mtg-goldfisher --skill triage-failures

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Consolidates scattered scenario failure data into actionable insights by grouping failures by root-cause patterns and auto-generating or reopening issues to track remediation.

Core Features & Use Cases

  • Failure grouping: Clusters failures by root-cause patterns from results/scenario_results.json.
  • Issue generation: Creates or reopens tracker entries in docs/SCENARIO_ISSUES.md based on regressions.
  • Regression handling: Detects tests that reappear in fixed issues and updates tracking accordingly.

Quick Start

Triage the latest scenario results to produce a consolidated issue report.

Frequently Asked Questions about triage-failures

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

FAQPage Schema
How do I automatically group scenario failures by root cause?

You can automatically group scenario failures by reading results from scenario_results.json, clustering them by root-cause patterns, and auto-creating or reopening issues to track remediation.

What is the best way to track test regressions in an issue tracker?

Tracking test regressions involves detecting tests that reappear in previously fixed issues and updating the tracking documents, such as SCENARIO_ISSUES.md, to automatically reopen existing issues.

How do I generate issue documentation from scenario failure results?

Generating issue documentation from scenario failure results requires processing scenario_results.json to consolidate failure data and updating docs/SCENARIO_ISSUES.md with new or reopened tracker entries.

Can I preview issue creation changes before applying them to my scenario results?

Yes, you can preview issue creation changes before applying them by utilizing the built-in dry-run mode, which allows you to review the grouped scenario failures and proposed tracker updates safely.

Do I need Node.js to run automated scenario failure triage scripts?

Yes, you need Node.js to run automated scenario failure triage scripts, because the triage logic relies on local Node.js scripts located in the scripts directory to process results and detect regressions.