AGENT SKILL

rca-analyzer

Run a structured root-cause analysis on a defect. Use when someone says "do an RCA for this bug", "why did this escape", or wants to understand a failure beyond its symptom. Applies 5-Whys and a fishbone across people, process, tooling, data, and environment, separates root cause from symptom, and proposes corrective and preventive actions. Reasons only from evidence supplied; unknown links are marked as hypotheses to verify.

License 许可
MIT
最近更新
2026-07-15
Stars
★ 4
Forks
8

01 前言 Front Matter

name
rca-analyzer
license
MIT
metadata
{ "author": "TheTestingAcademy", "version": "1.0.0", "stlc-phase": "Defect Management" }
description
Run a structured root-cause analysis on a defect. Use when someone says "do an RCA for this bug", "why did this escape", or wants to understand a failure beyond its symptom. Applies 5-Whys and a fishbone across people, process, tooling, data, and environment, separates root cause from symptom, and proposes corrective and preventive actions. Reasons only from evidence supplied; unknown links are marked as hypotheses to verify.

03 SKILL.md 正文

RCA Analyzer

You get past the symptom to the cause that, if fixed, stops recurrence — and you are explicit about which links are proven and which are still hypotheses.

When to use

  • A significant defect, escape, or incident needs a root-cause write-up.
  • A retro asks "why did this happen and why didn't we catch it?"
  • A recurring failure needs corrective and preventive actions defined.

Workflow

  1. State the problem precisely. Capture the observed effect, when it surfaced, blast radius, and the evidence available (logs, timeline, defect, commits). If evidence is thin, say what is missing — do not manufacture a causal chain.
  2. Run 5-Whys. Ask "why" iteratively from the symptom down to a root cause. Mark each link as evidence-backed or a hypothesis-to-verify.
  3. Run a fishbone. Consider contributing factors across People, Process, Tooling, Data, and Environment — a real root cause is often more than one category.
  4. Separate cause from symptom and identify the escape point (why testing/review missed it).
  5. Propose actions. Corrective (fix this instance) and preventive (stop the class) with an owner suggestion and how you would verify each landed.
  6. HUMAN REVIEW GATE (mandatory). Present the RCA as a draft. List unverified links and assumptions. Ask the team to confirm the root cause before actions are committed to.

Output shape

## RCA — <defect / incident>
Problem statement: <effect, when, blast radius>
5-Whys:  symptom -> ... -> root cause   [each link: evidence | hypothesis]
Fishbone: People / Process / Tooling / Data / Environment  (contributing factors)
Root cause: <the fix-this-and-it-stops item>
Escape point: <why it was not caught>
Actions:
  Corrective  — <fix this instance>   owner? / verify by?
  Preventive  — <stop the class>      owner? / verify by?
--- HUMAN REVIEW GATE ---
Unverified causal links / assumptions / "Confirm root cause before committing actions"

Guardrails

  • Never assert a causal link the evidence does not support — label it a hypothesis to verify.
  • Do not fabricate a timeline, log line, or commit; a missing artifact is a gap in the analysis.
  • Aim at process and system causes, not individual blame.
  • The root cause and actions are proposals until the team confirms them.

04 同仓库更多 Skills

PramodDutta
PramodDutta/skillmasterclass

se-wait-fixer

Scans Selenium Java code for Thread.sleep and for implicit+explicit wait mixing, then replaces them with WebDriverWait/ExpectedConditions or FluentWait to fix synchronization. Use when an SDET says "remove Thread.sleep from my tests", "fix the flaky waits", "my implicit and explicit waits conflict", or pastes code full of hard sleeps. Produces refactors the engineer must run and confirm.

★ 4
PramodDutta
PramodDutta/skillmasterclass

se-test-generator

Generates a runnable Selenium 4 + TestNG test in Java from a plain-language scenario, using explicit waits and stable locators. Use when an SDET says "write a Selenium test for login", "generate a TestNG test for the checkout flow", "automate this scenario in Selenium", or pastes Gherkin/steps and wants Java WebDriver code. Produces a draft test the engineer must review and run.

★ 4
PramodDutta
PramodDutta/skillmasterclass

se-report-integrator

Integrates reporting (Allure or ExtentReports) into a Selenium + TestNG suite with listeners, screenshot-on-failure, and step logging. Use when an SDET says "add Allure to my tests", "set up ExtentReports", "capture a screenshot on failure", "add a TestNG listener for reporting", or wants readable run reports. Produces listener and config code the engineer must run to generate a report.

★ 4
PramodDutta
PramodDutta/skillmasterclass

se-page-object-builder

Builds a Page Object Model class in Java (PageFactory @FindBy or explicit locators) with action methods and a WebDriverWait for a given page. Use when an SDET says "create a page object for the login page", "build a POM class", "refactor these locators into a page object", or pastes a page's fields and wants a reusable POM. Produces a draft class the engineer must review and run.

★ 4
PramodDutta
PramodDutta/skillmasterclass

se-locator-strategist

Recommends and repairs Selenium locator strategy — replaces brittle absolute XPath with By.id, By.cssSelector, or Selenium 4 relative locators, and explains the trade-offs. Use when an SDET says "this XPath keeps breaking", "make this locator more stable", "why is my locator flaky", "convert this XPath to CSS", or pastes selectors to harden. Produces proposals the engineer must verify in the DOM.

★ 4
PramodDutta
PramodDutta/skillmasterclass

se-grid-configurator

Configures Selenium Grid 4 (hub-and-node or standalone, including Docker) and wires RemoteWebDriver for parallel and distributed runs. Use when an SDET says "set up Selenium Grid", "run my tests on a remote grid", "dockerize Selenium Grid 4", "point my tests at RemoteWebDriver", or wants parallel execution across nodes. Produces config and code the engineer must run and validate in their environment.

★ 4