585 skills · sorted by relevance
Audit groups of bug reports to find shared root causes, checking claims against current code and tests. Produce a cause map, prioritize fixes that remove faulty mechanisms, and document which issues have enough evidence to close.
Investigate complex bugs by assigning competing explanations to parallel agents. Compare code evidence, contradictory findings, and confidence levels to identify likely root causes, then check that a fix resolves the original failure and related edge cases.
[omh] Application code misbehaves -- a wrong value, a flaky test, a lost update: reproduce it first, form competing hypotheses, discriminate them with the cheapest observation, and only then fix the demonstrated root cause. Use when the user says: app-debugging, app debugging, application debugging, root cause, root-cause, find the root cause, root cause analysis, flaky test.
The English summary is being prepared. Showing the original description.
Investigate root causes and manage CAPAs (Corrective and Preventive Actions) for compliance deviations. Covers investigation method selection (5-Why, fishbone, fault tree), structured root cause analysis, corrective vs preventive action design, effectiveness verification, and trend analysis. Use when an audit finding requires a CAPA, when a deviation or incident occurs in a validated system, when a regulatory observation needs a formal response, when a data integrity anomaly requires investigation, or when recurring issues suggest a systemic root cause.
The English summary is being prepared. Showing the original description.
システムログを分析してエラーの根本原因を特定し、段階的に深堀りしていくデバッグ専門家スキル。 アプリケーションログ、システムログ、クラウドサービスログなど様々な形式に対応。 5 Whys、タイムライン分析、Fishbone分析などのRCA（根本原因分析）手法を用いて 問題の本質を突き止め、再発防止策まで提案する。 Use when analyzing system logs to find error root causes, debugging application issues, or performing technical post-mortem analysis with log data. For organizational incident management processes (post-incident review, corrective action plans, incident reports without log data), use incident-rca-specialist instead. Triggers: "analyze this log", "find the root cause", "debug this error", "why is this failing", "log analysis", "what caused this crash", "troubleshoot this issue"
The English summary is being prepared. Showing the original description.
Find the root cause of a problem, not just symptoms. Use when the user says "root cause", "why does this keep happening", "5 whys", "fishbone diagram", "cause analysis", "problem investigation", "defect analysis", "incident analysis", "A3 problem solving", "what's causing this", "ishikawa" - even if they don't explicitly say "root cause analysis".
The English summary is being prepared. Showing the original description.
Use this skill when an internal or external audit raised a nonconformity, finding, exception or observation and the team must answer it, or asks "write the corrective action plan", "root cause for this audit finding", "respond to the major nonconformity", "CAPA for the auditor", "how do we close this finding" or "the auditor rejected our corrective action". Separates correction from corrective action, runs a root cause analysis that stops at a cause the company controls, checks for the same problem elsewhere, and drafts a response with actions, owners, dates and the evidence that will prove effectiveness at the next audit.
The English summary is being prepared. Showing the original description.
Support manufacturing quality investigations from containment through root cause analysis and corrective action. Organize decisions about nonconforming materials, assess whether actions prevent recurrence, interpret process control charts, and address supplier quality problems.
Turn lessons from complex tasks, debugging, failures, or rollbacks into short learning entries. Capture the root cause, a reusable action, and a recognizable signal, then merge examples that share a cause with existing notes.
Investigate software failures by reproducing the problem, reducing the failing example, and locating its root cause. Receive an evidence-based diagnosis that separates symptoms from causes, with fixes applied only when authorized.
Investigate incidents and recurring defects with structured methods such as Five Whys and Fishbone cause maps. Identify multiple contributing conditions, build a blame-free account of what happened, and propose practical changes to prevent similar failures.
Find other occurrences of a known bug across a codebase by tracing its root cause. Gradually broaden search patterns, assess matching candidates, assign severity, and document findings with rules to help prevent recurrence.
Analyze any OFAC or OFSI enforcement action — by URL, pasted text, or uploaded document — and produce a structured root cause analysis as a formatted Excel (.xlsx) spreadsheet. Use this skill whenever a user names, links to, pastes, or uploads an OFAC or OFSI enforcement action and asks for any of the following: root cause analysis, compliance gaps, what went wrong, lessons learned, organizational self-assessment, or remediation planning. Also trigger when a user asks "analyze this enforcement action", "what were the root causes", "turn this into a checklist", or "how do I make sure this doesn't happen to us". Outputs a single-sheet .xlsx table with six columns: Root Cause | What Went Wrong | How It Went Wrong | What Could Have Stopped It | Is my organization immune to this? (Yes/No/Partial) | Notes.
The English summary is being prepared. Showing the original description.
Use when a framed problem needs root-cause investigation rather than a symptom-level fix, applying Five Whys, Fishbone (Ishikawa), Current Reality Tree, and constraint identification. This should trigger when an issue's Root Cause Analysis point of view needs evaluation, or when a maintainer directly asks to find the root cause of a problem before proposing a fix. Part of Plinth Toolkit
The English summary is being prepared. Showing the original description.
Investigate failing tests, broken builds, and unexpected behavior through a structured debugging process. Reproduce the failure, narrow down its source, fix the root cause, and add a regression test that catches the same problem.
Analyze Antigravity coding session artifacts to explain scope changes, repeated rework, and underlying causes. Produce an evidence-based report with confidence levels, prompt assessments, recurring problem areas, and prioritized recommendations for improving future development sessions.
Investigate bugs and failing tests through four stages: finding the root cause, comparing working patterns, testing a hypothesis, and implementing a fix. Uses reproduction steps, diagnostic evidence, and regression tests to check the result.
Tested reasoning approaches for Claude prompts — 18 variants across 6 categories (Analytical, Strategic, Creative, Technical, Research, Comparative). Use when the user wants a specific reasoning template — retrieving, reviewing, customizing, or combining reasoning instructions for a prompt. Trigger on: "give me the Root Cause Diagnosis approach," "show me the reasoning template for," "I need the Evidence Synthesis method," "show me analytical reasoning options," "combine reasoning approaches for," "show me all reasoning variants." Also use when a prompt produces shallow output and the fix is a reasoning upgrade. Provides 18 tested approaches for analytical, strategic, creative, technical, research, and comparison tasks. If the user is unsure which reasoning method fits, use rootnode-block-selection first if available. Do NOT use for evaluating existing prompts — use rootnode-prompt-validation if available. Do NOT use for project-level audits — use rootnode-project-audit if available.
The English summary is being prepared. Showing the original description.
Deep root cause analysis using the 5 Whys and Fishbone techniques. Use when systematic debugging hasn't found the cause, or for complex systemic issues. Keywords: root cause, why, underlying, fundamental, systemic, deep, origin
The English summary is being prepared. Showing the original description.
Perform root cause analysis on a bug fix. Use when the user says 'run RCA on [commit/PR]', 'root cause analysis', or 'analyze what caused this bug'. Accepts a commit SHA, PR number, issue, or description of a fix.
The English summary is being prepared. Showing the original description.
Investigate software errors and unexpected behavior through four stages: investigation, analysis, hypothesis, and implementation. It requires identifying the root cause before making fixes and distinguishes evidence from code inspection, tests, and live runs when reporting findings.
Turn an incident review into an HTML presentation covering the root cause, fix, and follow-up actions. Use a dedicated template with speaker notes to help engineering, reliability teams, and leadership discuss next steps.
Organize a GitHub issue backlog by shared root cause, with one main tracking issue and design document per group. Route new reports into existing plans and prepare pull requests that address related bugs together with regression checks.
Write incident review documents that focus on system conditions and learning. Organize timelines, examine root causes with evidence, and turn findings into practical follow-up actions with owners and deadlines, supported by a meeting facilitation guide.