Loading...
Loading...
Found 170 Skills
Break the Loop - Deep Bug Analysis
Follow this sub-process when fixing bugs — turn the verbal description of "problem found" into a closed loop from verification to repair, leaving three documents: problem report, root cause analysis, and repair record. This process adds a buffer between "seeing the problem" and "starting to modify code" to avoid common pitfalls: the problem description in your mind disappears after the fix, you only fix the surface without analyzing the root cause, the scope of repair expands and cannot be traced, and you don't know if the fix is correct without verification after modification. This skill only acts as a router, deciding which of report / analyze / fix to proceed with based on existing artifacts. For simple problems that can be identified at a glance, a fast track will be taken, skipping the two middle steps and only retaining the fix-note.
Phase 2 of the issue process — Read the issue report + read the code, identify the true root cause and assess repair risks, and finally provide users with 2-3 repair solution options for them to decide. **Do NOT start modifying code in this phase** — present the conclusions to the user after analysis, and only proceed to Phase 3 after the user confirms the solution. Prerequisite: cs-issue-report has been completed. Trigger scenarios: The user says "Analyze this bug", "Find the root cause", "Locate the issue", and {slug}-report.md already exists in the issue directory.
Apply systematic problem-solving methodologies to complex challenges. Use when the user says "guide me through structured problem solving" or "I want to crack this challenge with guided problem solving techniques"
DTC Full-Funnel Diagnosis & Attribution Engine —— Full-funnel attribution analysis, key indicator anomaly detection, cross-business-line problem localization, root cause analysis, priority ranking. Use when user mentions: 诊断, diagnose, 归因, attribution, 问题分析, root cause, 指标下降, conversion rate decline, ROAS decline, CPA increase, 全链路, full-funnel, 异常检测, anomaly, 问题出在哪, why the decline.
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries. Use when the user reports an anomaly, asks "why did X change?", or needs root-cause analysis for a trend, funnel, retention, stickiness, or lifecycle metric.
End-to-end pipeline from unlabeled ml_app traces to a bootstrapped evaluator suite. Runs trace classification → root cause analysis → eval bootstrap in sequence with user checkpoints. Use when user says "run the eval pipeline", "go from traces to evals", "bootstrap evals end to end", "classify then RCA then bootstrap", "build an eval set from scratch", or wants a guided walkthrough from production data to evaluator code.
Extract false-positive and false-negative gaps from VLM binary-classification-question (BCQ, yes/no) predictions. Use after running VLM evaluation when you have a predictions JSON and need to identify failure cases for DEFT root cause analysis on a binary-classification VLM workflow.
Conduct Kepner-Tregoe (KT) Problem Solving and Decision Making (PSDM) analysis using the four rational processes - Situation Appraisal, Problem Analysis, Decision Analysis, and Potential Problem Analysis. Use when performing structured root cause analysis, making complex decisions, evaluating alternatives with weighted criteria, conducting IS/IS NOT specification analysis, anticipating implementation risks, troubleshooting complex issues, or when user mentions "Kepner-Tregoe", "KT method", "IS/IS NOT", "situation appraisal", "decision analysis", "MUSTS and WANTS", "potential problem analysis", or needs systematic problem-solving methodology. Includes specification matrices, decision scoring, quality rubrics, and professional report generation.
Create comprehensive Fishbone (Ishikawa/Cause-and-Effect) diagrams for structured root cause brainstorming. Guides teams through problem definition, category selection (6Ms, 8Ps, 4Ss, or custom), cause identification, sub-cause drilling, prioritization via multi-voting, and 5 Whys integration. Generates visual SVG diagrams and professional HTML reports. Use when brainstorming potential causes, conducting root cause analysis, facilitating quality improvement sessions, analyzing defects or failures, structuring team problem-solving, or when user mentions "fishbone", "Ishikawa", "cause and effect diagram", "6Ms", "cause analysis", or "brainstorming causes".
When user encounters "error", "exception", "failed", "stack trace", "crashed", or needs error categorization. Provides structured root cause analysis and prevention strategies.
Systematic debugging methodology — binary search isolation, hypothesis-driven debugging, reproducing issues, and root cause analysis. Use when debugging errors, unexpected behavior, or test failures.