Skip to main content

root-cause-tracing

Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior

Stars

4,576

Forks

272

Updated

October 22, 2025 at 03:13

Installation

/plugin marketplace add obra/superpowers

Copy and paste this command into Claude Code to install the skill

Related Skills

obra

using-git-worktrees

obra

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

4,576•development
obra

sharing-skills

obra

Use when you've developed a broadly useful skill and want to contribute it upstream via pull request - guides process of branching, committing, pushing, and creating PR to contribute skills back to upstream repository

4,576•development
obra

executing-plans

obra

Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches

4,576•development
obra

brainstorming

obra

Use when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation

4,576•development
obra

requesting-code-review

obra

Use when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches superpowers:code-reviewer subagent to review implementation against plan or requirements before proceeding

4,576•development
obra

receiving-code-review

obra

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

4,576•development
obra

verification-before-completion

obra

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

4,576•development
obra

subagent-driven-development

obra

Use when executing implementation plans with independent tasks in the current session - dispatches fresh subagent for each task with code review between tasks, enabling fast iteration with quality gates

4,576•development
obra

defense-in-depth

obra

Use when invalid data causes failures deep in execution, requiring validation at multiple system layers - validates at every layer data passes through to make bugs structurally impossible

4,576•development
obra

using-tmux-for-interactive-commands

obra

Use when you need to run interactive CLI tools (vim, git rebase -i, Python REPL, etc.) that require real-time input/output - provides tmux-based approach for controlling interactive sessions through detached sessions and send-keys

4•development
obra

browsing

obra

Use when you need direct browser control - teaches Chrome DevTools Protocol for controlling existing browser sessions, multi-tab management, form automation, and content extraction via use_browser MCP tool

29•development
ryancnelson

Delegating to CDN Agent

ryancnelson

Recognize Fastly CDN queries and delegate to specialized sub-agent to avoid context pollution

28•development
root-cause-tracing by obra - Claude AI Skill | SkillsMP