diagnose

Spawn a dedicated debug agent to investigate project errors in an isolated context.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/hodor/claude-compass --skill diagnose-hodor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/hodor/claude-compass/tree/main/plugin/skills/diagnose
Command: npx skills add https://github.com/hodor/claude-compass --skill diagnose-hodor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The diagnose skill helps investigate errors, test failures, or unexpected behavior in your project by spawning a debug agent in an isolated context.

Core Features & Use Cases

  • Debugging: Spawn a debug agent to investigate issues in a separate context window.
  • Isolation: Prevents issues from affecting the main conversation's token budget.
  • Use Case: When you encounter a problem in your project, use the /compass:diagnose skill to initiate a debug session that can help you identify the issue.

Quick Start

Use the /compass:diagnose skill to investigate an error in your project with the command: '/compass:diagnose investigate the error "Error message here"'

Frequently Asked Questions about diagnose

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I investigate project errors without affecting my main conversation context?

You can investigate project errors in an isolated context by spawning a dedicated debug agent. This approach prevents issue investigation from affecting the main conversation's token budget, ensuring your primary context remains clean.

What is context isolation for debugging and when do I need it?

Context isolation for debugging separates your error investigation into a distinct window. You need this technique when resolving project issues that require extensive analysis, preventing the debug process from consuming your main session's resources.

How to debug test failures or unexpected behavior in a project context?

To debug test failures or unexpected behavior, initiate a debug session using the /compass:diagnose command followed by your specific trigger. This spawns an agent to investigate the problem and identify the root cause.

Can I use a debug agent to resolve issues without cluttering my main workspace?

Yes, you can use a debug agent to resolve project issues without cluttering your main workspace. The agent operates in a separated context window, isolating the debugging process from your primary conversation environment.

Does running an issue investigation in an isolated context impact token usage?

Running an issue investigation in an isolated context positively impacts token usage by preventing the debug agent's operations from affecting your main conversation's token budget. This maintains separation while resolving project issues.

Why does spawning a debug agent help with error investigation?

Spawning a debug agent helps with error investigation by dedic a focused context to analyze unexpected behavior. This isolation ensures thorough issue resolution without interfering with the ongoing main conversation context.