Agent Skills: Root Cause Tracing
Systematically trace bugs backward through call stack to find original trigger
ID: obra/superpowers-skills/Root Cause Tracing
748169
Install this agent skill to your local
Skill Files
The files that make up Root Cause Tracing.
More agent skills
- code-maturity-assessorSystematic code maturity assessment using Trail of Bits' 9-category framework. Analyzes codebase for arithmetic safety, auditing practices, access controls, complexity, decentralization, documentation, MEV risks, low-level code, and testing, then produces a scorecard with evidence-based ratings and a priority-ordered roadmap. Use when assessing or scoring the maturity of a smart contract or blockchain codebase, producing a maturity scorecard or evaluation, or judging how mature, well-tested, or well-documented such a project is against a rubric.
- code-reviewReview changed code against project standards. Checks for missing tests, dead code, type safety, lint issues, and coding conventions. Run after completing any implementation work.
- search-strategyQuery decomposition and multi-source search orchestration. Breaks natural language questions into targeted searches per source, translates queries into source-specific syntax, ranks results by relevance, and handles ambiguity and fallback strategies.
- drive-redisearchDrive the locally built RediSearch module the way a user does — a real redis-server with redisearch.so loaded (standalone or a 3-shard OSS cluster), exercised through FT.* commands in redis-cli — and capture evidence. Use to prove a change to indexing, querying, aggregation, vector/hybrid search, or the coordinator works end to end, beyond what unit tests show, or to reproduce a reported behavior by hand.
- deepchat-sddUse before substantial DeepChat code, configuration, documentation, test, build, feature, issue, refactor, or architecture changes that need a durable RFC and an explicit execution path. Skip trivial style fixes, small localized logic changes, routine docs edits, and simple bugs unless the developer asks for SDD. Use plan.md as the only separate tracker when needed, default to implementation-first validation, and ask before optional GitHub issue sync unless the developer explicitly requested sync.
- scientific-visualizationCreate and audit truthful, accessible, publication-ready scientific figures with Matplotlib, Seaborn, or Plotly. Use for figure design, multi-panel layouts, uncertainty and missing-data displays, color/contrast review, image metadata validation, and journal export planning.