Agent skill

Investigate

by catlog22 in catlog22/Claude-Code-Workflow

Systematic debugging with Iron Law methodology. An agent skill from catlog22/Claude-Code-Workflow.

MITAuto-check: notesDevelopment

Install Investigate

skills CLI
$ npx skills add catlog22/Claude-Code-Workflow --skill investigate -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install catlog22/Claude-Code-Workflow investigate --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/investigate .claude/skills/investigate && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
investigate
GitHub stars
2.1k
Token cost
~1.1k tokens
SKILL.md length
340 words
Files
8
Skills in repo
82
Repo updated
First seen
Licence
MIT

At a glance

Systematic debugging with Iron Law methodology. An agent skill from catlog22/Claude-Code-Workflow.

  • Works in 5 steps: Reproduce the bug with concrete evidence → Analyze patterns to assess scope → Form and test hypotheses (max 3 strikes) → …
  • Tasks that involve Debugging
  • SKILL.md covers Iron Law Principle, Key Design Principles, Execution Flow and Directory Setup, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Investigate is an agent skill from catlog22/Claude-Code-Workflow. Systematic debugging with Iron Law methodology. 5-phase investigation from evidence collection to verified fix. Triggers on "investigate", "debug", "root cause".

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files (for example `phases/01-root-cause-investigation.md`, `phases/02-pattern-analysis.md` and `phases/03-hypothesis-testing.md`).

It sits in Development, covering Debugging, Root cause analysis and Digital forensics. The repository describes itself as: JSON-driven multi-agent cadence-team development framework with intelligent CLI orchestration (Gemini/Qwen/Codex), context-first architecture, and automated workflow execution. The licence is MIT.

When your agent uses it

  • Tasks that involve Debugging
  • Tasks that involve Root cause analysis
  • Tasks that involve Digital forensics

Example prompts

  • “investigate”
  • “root cause”
  • “/investigate”

Requirements

  • Pre-approved tools (allowed-tools): Bash, Read, Write, Edit, Glob, Grep

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Reproduce the bug with concrete evidence
  2. Analyze patterns to assess scope
  3. Form and test hypotheses (max 3 strikes)
  4. Implement minimal fix ONLY after root cause is confirmed
  5. Verify fix and generate structured report

What it can do on your machine

Read from SKILL.md and the folder at commit 07491b0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Read
    • Write
    • Edit
    • Glob
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Investigate loads about 1.1k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 340 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~43
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Read, Write, Edit, Glob, Grep

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from catlog22/Claude-Code-Workflow at commit 07491b0, republished under its MIT licence (© catlog22). 340 words, ~1,095 tokens.

Download SKILL.mdSave it as .claude/skills/investigate/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
investigate
description
Systematic debugging with Iron Law methodology. 5-phase investigation from evidence collection to verified fix. Triggers on "investigate", "debug", "root cause".
allowed-tools
Bash, Read, Write, Edit, Glob, Grep

Investigate

Systematic debugging skill that enforces the Iron Law: never fix without a confirmed root cause. Produces a structured debug report with full evidence chain, minimal fix, and regression test.

Iron Law Principle

No fix without confirmed root cause. Every investigation follows a strict evidence chain:

  1. Reproduce the bug with concrete evidence
  2. Analyze patterns to assess scope
  3. Form and test hypotheses (max 3 strikes)
  4. Implement minimal fix ONLY after root cause is confirmed
  5. Verify fix and generate structured report

Violation of the Iron Law (skipping to Phase 4 without Phase 3 confirmation) is prohibited.

Key Design Principles

  1. Evidence-First: Collect before theorizing. Logs, stack traces, and reproduction steps are mandatory inputs.
  2. Minimal Fix: Change only what is necessary. Refactoring is not debugging.
  3. 3-Strike Escalation: If 3 consecutive hypothesis tests fail, STOP and escalate with a diagnostic dump.
  4. Regression Coverage: Every fix must include a test that fails without the fix and passes with it.
  5. Structured Output: All findings are recorded in machine-readable JSON for future reference.

Execution Flow

Phase 1: Root Cause Investigation
  Reproduce bug, collect evidence (errors, logs, traces)
  Use ccw cli --tool gemini --mode analysis for initial diagnosis
  Output: investigation-report.json
      |
      v
Phase 2: Pattern Analysis
  Search codebase for similar patterns (same error, module, antipattern)
  Assess scope: isolated vs systemic
  Output: pattern-analysis section in report
      |
      v
Phase 3: Hypothesis Testing
  Form max 3 hypotheses from evidence
  Test each with minimal read-only probes
  3-strike rule: STOP and escalate on 3 consecutive failures
  Output: confirmed root cause with evidence chain
      |
      v
Phase 4: Implementation  [GATE: requires Phase 3 confirmed root cause]
  Implement minimal fix
  Add regression test
  Verify fix resolves reproduction case
      |
      v
Phase 5: Verification & Report
  Run full test suite
  Check for regressions
  Generate structured debug report to .workflow/.debug/

Directory Setup

bash
mkdir -p .workflow/.debug

Output Structure

.workflow/.debug/
  debug-report-{YYYY-MM-DD}-{slug}.json    # Structured debug report

Completion Status Protocol

This skill follows the Completion Status Protocol defined in _shared/SKILL-DESIGN-SPEC.md sections 13-14.

StatusWhen
DONERoot cause confirmed, fix applied, regression test passes, no regressions
DONE_WITH_CONCERNSFix applied but partial test coverage or minor warnings
BLOCKEDCannot reproduce bug, or 3-strike escalation triggered in Phase 3
NEEDS_CONTEXTMissing reproduction steps, unclear error conditions

Reference Documents

DocumentPurpose
phases/01-root-cause-investigation.mdEvidence collection and reproduction
phases/02-pattern-analysis.mdCodebase pattern search and scope assessment
phases/03-hypothesis-testing.mdHypothesis formation, testing, and 3-strike rule
phases/04-implementation.mdMinimal fix with Iron Law gate
phases/05-verification-report.mdTest suite, regression check, report generation
specs/iron-law.mdIron Law rules definition
specs/debug-report-format.mdStructured debug report JSON schema

CLI Integration

This skill leverages ccw cli for multi-model analysis at key points:

PhaseCLI UsageMode
Phase 1Initial diagnosis from error evidence--mode analysis
Phase 2Cross-file pattern search--mode analysis
Phase 3Hypothesis validation assistance--mode analysis

All CLI calls use --mode analysis (read-only). No write-mode CLI calls during investigation phases 1-3.

© catlog22, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files in .claude/skills/investigate of catlog22/Claude-Code-Workflow.

  • SKILL.md
  • phases/01-root-cause-investigation.md
  • phases/02-pattern-analysis.md
  • phases/03-hypothesis-testing.md
  • phases/04-implementation.md
  • phases/05-verification-report.md
  • specs/debug-report-format.md
  • specs/iron-law.md

Open the folder on GitHubat commit 07491b0

Compare with similar skills

Investigate next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Investigate compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Investigate this skillcatlog22/Claude-Code-Workflow2.1k—~1.1kAutomated safety check: NotesMIT
Parallel Debuggingwshobson/agents40k—~1.2kAutomated safety check: PassMIT
OpenLogi macOS Permissions TriageAprilNEA/OpenLogi23k—~2.5kAutomated safety check: NotesApache-2.0
Bug Finder for daisyUIsaadeghi/daisyui43k—~2.3kAutomated safety check: PassMIT
Root Cause Debugginggarrytan/gstack136k—~1.4kAutomated safety check: PassMIT
Graph-Based Bug Tracingtirth8205/code-review-graph32k1 repos~287Automated safety check: PassMIT

Similar skills

  • Parallel Debugging

    wshobson/agents

    Debug complex issues using competing hypotheses with parallel investigation, evidence collection, and root cause arbitration.

    40k GitHub stars~1.2k tokensUpdated 4 days ago
    DevelopmentAuto-check passed
  • Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.

    23k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check: notes
  • Bug Finder for daisyUI

    saadeghi/daisyui

    Investigates suspected bugs in the daisyUI monorepo through read-only analysis, then writes a decision-ready fix plan in tmp/bugs without changing any product code.

    43k GitHub stars~2.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Root Cause Debugging

    garrytan/gstack

    Investigates bugs, errors and stack traces in phases and requires a root-cause hypothesis to be confirmed before any fix is written.

    136k GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check passed
  • Graph-Based Bug Tracing

    tirth8205/code-review-graph

    Traces a bug through a code knowledge graph, following callers, callees and execution flow before opening source files, within a small token budget.

    32k GitHub starsUsed in 1 repo~287 tokens
    DevelopmentAuto-check passed
  • Systematic Debugging

    ChrisWiles/claude-code-showcase

    Applies a four-phase debugging routine that finds the root cause of a bug or failing test before any fix is written.

    6.1k GitHub starsUsed in 3 repos~1.2k tokens
    DevelopmentAuto-check passed

More from catlog22/Claude-Code-Workflow

All 82 skills in this repo
  • Ccw Help

    catlog22/Claude-Code-Workflow

    CCW command help system. An agent skill from catlog22/Claude-Code-Workflow.

    2.1k GitHub stars~2.5k tokensUpdated 3 mo ago
    Auto-check passed
  • Brainstorm

    catlog22/Claude-Code-Workflow

    Unified brainstorming skill with dual-mode operation — auto mode (framework generation, parallel multi-role analysis, cross-role synthesis) and single role analysis.

    2.1k GitHub stars~4.8k tokensUpdated 3 mo ago
    Auto-check: notes
  • Ccw Chain

    catlog22/Claude-Code-Workflow

    Chain-based CCW workflow orchestrator. An agent skill from catlog22/Claude-Code-Workflow.

    2.1k GitHub stars~1.1k tokensUpdated 3 mo ago
    Auto-check: notes
  • Delegation Check

    catlog22/Claude-Code-Workflow

    Check workflow delegation prompts against agent role definitions for content separation violations.

    2.1k GitHub stars~2.8k tokensUpdated 3 mo ago
    Auto-check: notes
  • Issue Discover

    catlog22/Claude-Code-Workflow

    Unified issue discovery and creation. An agent skill from catlog22/Claude-Code-Workflow.

    2.1k GitHub stars~3.3k tokensUpdated 3 mo ago
    Auto-check: notes
  • Issue Manage

    catlog22/Claude-Code-Workflow

    Interactive issue management with menu-driven CRUD operations.

    2.1k GitHub stars~2.1k tokensUpdated 3 mo ago
    Auto-check: notes

Categories

Questions about Investigate

What does Investigate do?

Systematic debugging with Iron Law methodology. An agent skill from catlog22/Claude-Code-Workflow. Investigate is an agent skill from catlog22/Claude-Code-Workflow. Systematic debugging with Iron Law methodology.

When should I use Investigate?

Investigate fits situations like: tasks that involve Debugging; tasks that involve Root cause analysis; tasks that involve Digital forensics.

How do I install Investigate in Claude Code?

Run `npx skills add catlog22/Claude-Code-Workflow --skill investigate -a claude-code`. Or copy the skill folder (.claude/skills/investigate in catlog22/Claude-Code-Workflow) into .claude/skills/investigate in your project. Claude Code loads it when a task matches its description.

How do I install Investigate in Codex?

Run `npx skills add catlog22/Claude-Code-Workflow --skill investigate -a codex`. Or copy the skill folder (.claude/skills/investigate in catlog22/Claude-Code-Workflow) into .agents/skills/investigate in your project. Codex loads it when a task matches its description.

Can I use Investigate in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add catlog22/Claude-Code-Workflow --skill investigate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/investigate, .gemini/skills/investigate, .github/skills/investigate and .opencode/skills/investigate in your project.

What does Investigate need to run?

SKILL.md names no scripts, command-line tools or credentials: Investigate is instructions for the agent only. Its frontmatter pre-approves these tools: Bash, Read, Write, Edit, Glob, Grep.

Does Investigate access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Investigate safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Investigate use?

Investigate is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Investigate use?

About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Investigate?

Skills that share tags, products or a category with Investigate: Parallel Debugging (wshobson/agents, 40k stars), OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars), Bug Finder for daisyUI (saadeghi/daisyui, 43k stars) and Root Cause Debugging (garrytan/gstack, 136k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Investigate?

catlog22 (a GitHub user) maintains it in catlog22/Claude-Code-Workflow, which has 2,130 GitHub stars. The repository holds 82 skills in this directory. The repository was last updated on June 18, 2026.

Source: catlog22/Claude-Code-Workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.