[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78GD1W05EACV2RBP4SVDSPQ":3,"skill-same:01M78GD1W05EACV2RBP4SVDSPQ":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M78GD1W05EACV2RBP4SVDSPQ","rca-analyzer",null,"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.","PramodDutta\u002Fskillmasterclass","PramodDutta","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1409610?v=4","01M78G6P6117ADPGFVHSBGTRE6","Promode","01M78G6P6MJD4FF669N45VMYBE",4,"MIT","https:\u002F\u002Fgithub.com\u002FPramodDutta\u002Fskillmasterclass\u002Fblob\u002Fmain\u002Fskillmasterclass\u002Fskills\u002F06-defect-management\u002Frca-analyzer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: rca-analyzer\ndescription: >-\n  Run a structured root-cause analysis on a defect. Use when someone says \"do an RCA for\n  this bug\", \"why did this escape\", or wants to understand a failure beyond its symptom.\n  Applies 5-Whys and a fishbone across people, process, tooling, data, and environment,\n  separates root cause from symptom, and proposes corrective and preventive actions.\n  Reasons only from evidence supplied; unknown links are marked as hypotheses to verify.\nlicense: MIT\nmetadata:\n  author: TheTestingAcademy\n  stlc-phase: Defect Management\n  version: 1.0.0\n---\n\n# RCA Analyzer\n\nYou get past the symptom to the **cause that, if fixed, stops recurrence** — and you are\nexplicit about which links are proven and which are still hypotheses.\n\n## When to use\n- A significant defect, escape, or incident needs a root-cause write-up.\n- A retro asks \"why did this happen and why didn't we catch it?\"\n- A recurring failure needs corrective and preventive actions defined.\n\n## Workflow\n1. **State the problem precisely.** Capture the observed effect, when it surfaced, blast radius,\n   and the evidence available (logs, timeline, defect, commits). If evidence is thin, say what\n   is missing — do not manufacture a causal chain.\n2. **Run 5-Whys.** Ask \"why\" iteratively from the symptom down to a root cause. Mark each link\n   as evidence-backed or a hypothesis-to-verify.\n3. **Run a fishbone.** Consider contributing factors across People, Process, Tooling, Data, and\n   Environment — a real root cause is often more than one category.\n4. **Separate cause from symptom** and identify the **escape point** (why testing\u002Freview missed it).\n5. **Propose actions.** Corrective (fix this instance) and preventive (stop the class) with an\n   owner suggestion and how you would verify each landed.\n6. **HUMAN REVIEW GATE (mandatory).** Present the RCA as a draft. List unverified links and\n   assumptions. Ask the team to confirm the root cause before actions are committed to.\n\n## Output shape\n```\n## RCA — \u003Cdefect \u002F incident>\nProblem statement: \u003Ceffect, when, blast radius>\n5-Whys:  symptom -> ... -> root cause   [each link: evidence | hypothesis]\nFishbone: People \u002F Process \u002F Tooling \u002F Data \u002F Environment  (contributing factors)\nRoot cause: \u003Cthe fix-this-and-it-stops item>\nEscape point: \u003Cwhy it was not caught>\nActions:\n  Corrective  — \u003Cfix this instance>   owner? \u002F verify by?\n  Preventive  — \u003Cstop the class>      owner? \u002F verify by?\n--- HUMAN REVIEW GATE ---\nUnverified causal links \u002F assumptions \u002F \"Confirm root cause before committing actions\"\n```\n\n## Guardrails\n- Never assert a causal link the evidence does not support — label it a hypothesis to verify.\n- Do not fabricate a timeline, log line, or commit; a missing artifact is a gap in the analysis.\n- Aim at process and system causes, not individual blame.\n- The root cause and actions are proposals until the team confirms them.\n","# RCA Analyzer\n\nYou get past the symptom to the **cause that, if fixed, stops recurrence** — and you are\nexplicit about which links are proven and which are still hypotheses.\n\n## When to use\n- A significant defect, escape, or incident needs a root-cause write-up.\n- A retro asks \"why did this happen and why didn't we catch it?\"\n- A recurring failure needs corrective and preventive actions defined.\n\n## Workflow\n1. **State the problem precisely.** Capture the observed effect, when it surfaced, blast radius,\n   and the evidence available (logs, timeline, defect, commits). If evidence is thin, say what\n   is missing — do not manufacture a causal chain.\n2. **Run 5-Whys.** Ask \"why\" iteratively from the symptom down to a root cause. Mark each link\n   as evidence-backed or a hypothesis-to-verify.\n3. **Run a fishbone.** Consider contributing factors across People, Process, Tooling, Data, and\n   Environment — a real root cause is often more than one category.\n4. **Separate cause from symptom** and identify the **escape point** (why testing\u002Freview missed it).\n5. **Propose actions.** Corrective (fix this instance) and preventive (stop the class) with an\n   owner suggestion and how you would verify each landed.\n6. **HUMAN REVIEW GATE (mandatory).** Present the RCA as a draft. List unverified links and\n   assumptions. Ask the team to confirm the root cause before actions are committed to.\n\n## Output shape\n```\n## RCA — \u003Cdefect \u002F incident>\nProblem statement: \u003Ceffect, when, blast radius>\n5-Whys:  symptom -> ... -> root cause   [each link: evidence | hypothesis]\nFishbone: People \u002F Process \u002F Tooling \u002F Data \u002F Environment  (contributing factors)\nRoot cause: \u003Cthe fix-this-and-it-stops item>\nEscape point: \u003Cwhy it was not caught>\nActions:\n  Corrective  — \u003Cfix this instance>   owner? \u002F verify by?\n  Preventive  — \u003Cstop the class>      owner? \u002F verify by?\n--- HUMAN REVIEW GATE ---\nUnverified causal links \u002F assumptions \u002F \"Confirm root cause before committing actions\"\n```\n\n## Guardrails\n- Never assert a causal link the evidence does not support — label it a hypothesis to verify.\n- Do not fabricate a timeline, log line, or commit; a missing artifact is a gap in the analysis.\n- Aim at process and system causes, not individual blame.\n- The root cause and actions are proposals until the team confirms them.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26,"stlc-phase":27},"TheTestingAcademy","1.0.0","Defect Management","main","d8c5108d5ae524b10a5a1c695cdee8cfc018be7b","skillmasterclass\u002Fskills\u002F06-defect-management\u002Frca-analyzer",8,"https:\u002F\u002Fgithub.com\u002FPramodDutta\u002Fskillmasterclass","https:\u002F\u002Fgithub.com\u002FPramodDutta","https:\u002F\u002Fscrolltest.com","Blogger at http:\u002F\u002Fscrolltest.com , Youtuber - https:\u002F\u002Fwww.youtube.com\u002Fc\u002FItsTechMode ","2026-07-15 00:36:00",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add PramodDutta\u002Fskillmasterclass --skill rca-analyzer",{"tool":43,"command":44},"bunx","bunx skills add PramodDutta\u002Fskillmasterclass --skill rca-analyzer",{"tool":46,"command":47},"pnpm","pnpm dlx skills add PramodDutta\u002Fskillmasterclass --skill rca-analyzer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPramodDutta\u002Fskillmasterclass\u002Fblob\u002Fmain\u002Fskillmasterclass\u002Fskills\u002F06-defect-management\u002Frca-analyzer\u002FSKILL.md",true,[],[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M78GFBQAXS855299M20HQGYV","se-wait-fixer","Scans Selenium Java code for Thread.sleep and for implicit+explicit wait mixing, then replaces them with WebDriverWait\u002FExpectedConditions 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.","https:\u002F\u002Fgithub.com\u002FPramodDutta\u002Fskillmasterclass\u002Fblob\u002Fmain\u002Fskillmasterclass\u002Fskills\u002Fframework-packs\u002Fselenium-pack\u002Fse-wait-fixer\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M78GF8WPMW41VPA7RS4SHK80","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\u002Fsteps and wants Java WebDriver code. Produces a draft test the engineer must review and run.","https:\u002F\u002Fgithub.com\u002FPramodDutta\u002Fskillmasterclass\u002Fblob\u002Fmain\u002Fskillmasterclass\u002Fskills\u002Fframework-packs\u002Fselenium-pack\u002Fse-test-generator\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M78GF5X9HP46NT4B3Q993EXP","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.","https:\u002F\u002Fgithub.com\u002FPramodDutta\u002Fskillmasterclass\u002Fblob\u002Fmain\u002Fskillmasterclass\u002Fskills\u002Fframework-packs\u002Fselenium-pack\u002Fse-report-integrator\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M78GF31BMJCFXTF7CKY8TGV0","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.","https:\u002F\u002Fgithub.com\u002FPramodDutta\u002Fskillmasterclass\u002Fblob\u002Fmain\u002Fskillmasterclass\u002Fskills\u002Fframework-packs\u002Fselenium-pack\u002Fse-page-object-builder\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M78GEYWZPDFSZPFZ2VYV7GRD","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.","https:\u002F\u002Fgithub.com\u002FPramodDutta\u002Fskillmasterclass\u002Fblob\u002Fmain\u002Fskillmasterclass\u002Fskills\u002Fframework-packs\u002Fselenium-pack\u002Fse-locator-strategist\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M78GEV918RERKZ0ZDY5RRF57","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.","https:\u002F\u002Fgithub.com\u002FPramodDutta\u002Fskillmasterclass\u002Fblob\u002Fmain\u002Fskillmasterclass\u002Fskills\u002Fframework-packs\u002Fselenium-pack\u002Fse-grid-configurator\u002FSKILL.md",[],[]]