noob-rca

Classifies run pack failures into environment, flaky, bug, data, or network categories.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/ganeshgaxy/apps-for-testing --skill noob-rca
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: noob-rca
Source: https://github.com/ganeshgaxy/apps-for-testing/tree/main/.claude/skills/noob-rca
Command: npx skills add https://github.com/ganeshgaxy/apps-for-testing --skill noob-rca

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Root-cause analysis of failed test runs by diagnosing and classifying failures into env, flaky, bug, data, or network categories, and by guiding remediation.

Core Features & Use Cases

  • Classify failures from a completed run pack into environment, flaky, bug, data, or network categories and provide a concise root-cause summary.
  • Collect evidence (logs, artifacts) and prepare actionable remediation steps for future runs.
  • Suggest patterns and actions to update tests and configurations after run execution.

Quick Start

Run noob-rca on a completed run pack to identify failures, classify root causes, and generate remediation guidance.

Frequently Asked Questions about noob-rca

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

FAQPage Schema
How do I perform root-cause analysis on failed test runs?

Root-cause analysis of failed test runs involves classifying failures into environment, flaky, bug, data, or network categories. This Skill uses completed run pack data to generate structured RCA steps, capture evidence, and propose actionable mitigations for future runs.

How do I classify test failures into flaky, environment, or bug categories?

Test failures are classified by analyzing runpack data, failed entries, and artifact captures post-execution. The Skill identifies patterns to categorize each failure as environment, flaky, bug, data, or network, enabling targeted remediation.

What is the best way to capture evidence and artifacts after test execution?

The best way to capture evidence after test execution is to run a root-cause analysis on the completed run pack. This Skill collects logs and artifacts from failed entries to prepare actionable remediation steps and suggest test configuration updates.

Can I use noob-rca to get remediation guidance for flaky test failures?

Yes, you can use noob-rca to get remediation guidance for flaky test failures. It operates after test execution, classifies the root cause, and suggests patterns and actions to update tests and configurations for future runs.

Do I need to wait until test execution is complete to analyze runpack data?

Yes, you need a completed run pack to analyze runpack data. The Skill operates strictly after test execution, requiring access to failed entries and artifact captures to accurately classify failures and inform remediation decisions.

Why does root-cause analysis categorize failures into environment, data, and network issues?

Root-cause analysis categorizes failures into environment, data, and network issues to enable targeted remediation. By distinguishing bug failures from flaky or network failures, the Skill generates concise summaries and actionable mitigations for future test runs.