cgl-consulting-troubleshooting

Description

Systematically diagnoses and fixes failures through hypothesis-driven investigation. Auto-activates when user reports something broken, failing, erroring, not working, crashed, or buggy. Spawns debugger agent for binary search isolation and minimal reproduction.

Tool Access

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

Skill Content

Troubleshooting Activation

Invoke /cgl-consulting:troubleshoot when user reports failures or broken behavior.

Trigger Patterns

"this is broken"
"it's not working"
"getting an error"
"failing when"
"doesn't work"
"crashed"
"bug in"
"something's wrong with"

Action

Skill(skill="cgl-consulting:troubleshoot")

Workflow

The troubleshoot command will:

Gather context with explorer agent (if system unfamiliar)
Spawn debugger agent for systematic investigation
Apply hypothesis-driven debugging with binary search
Isolate root cause through minimal reproduction
Verify fix resolves the issue

Links

GitHub Stats

0 forks

Updated 1 day ago

Related Skills

frontend-design

47.1K

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

From frontend-design

claude-opus-4-5-migration

47.1K

Migrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their codebase, prompts, or API calls to use Opus 4.5. Handles model string updates and prompt adjustments for known Opus 4.5 behavioral differences. Does NOT migrate Haiku 4.5.

From claude-opus-4-5-migration

Writing Hookify Rules

47.1K

This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.

From hookify