root-cause-tracing

Description

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 with quantitative tracking, adding instrumentation when needed, to identify source of invalid data or incorrect behavior

Tool Access

Full access

Inherits all available tools

Supporting Files

0 files

Additional assets for this skill

Tool Access

This skill inherits all available tools. When active, it can use any tool Claude has access to.

Links

GitHub Stats

0 forks

Updated 15 days ago

Related Skills

Plugin Settings

46.0K

This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin-name.local.md pattern for storing plugin-specific configuration with YAML frontmatter and markdown content.

From plugin-dev

Plugin Structure

46.0K

This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.

From plugin-dev

Skill Development

46.0K

This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.

From plugin-dev