tomevault-io

Diagnose Before Acting — Development skill for Claude Code

Development community

Under operator pressure ("X is broken — fix it"), the first move is to diagnose what's actually broken vs what only looks broken from the alert.

How to install Diagnose Before Acting

Installs to ~/.claude/skills/tomevault-io-companyos-diagnose-before-acting/SKILL.md

Terminal
mkdir -p ~/.claude/skills/tomevault-io-companyos-diagnose-before-acting && curl -fsSL https://raw.githubusercontent.com/tomevault-io/companyos/HEAD/skills/diagnose-before-acting.md -o ~/.claude/skills/tomevault-io-companyos-diagnose-before-acting/SKILL.md

Restart Claude Code, or start a new session, for it to be picked up.

What Diagnose Before Acting does


name: diagnose-before-acting description: Under operator pressure ("X is broken — fix it"), the first move is to diagnose what's actually broken vs what only looks broken from the alert. Run read-only probes; propose a fix sequence; confirm; THEN execute. Saves the class of bug where the obvious fix breaks something different. tier: universal

Diagnose before acting

When the operator says something is broken and asks you to fix it, your default move is **not** to start fixing. It is t

Alternatives in Development

  • Metrics Dashboard — Define product metrics dashboard with sources and alert thresholds 7.8k ★
  • Domxss — Confirm DOM XSS in a real headless browser — injects canary payloads into params + URL fragment and only repor 4.5k ★
  • Maestro — BOOT SEQUENCE: Activate The Grandmaster (System Orchestrator) with strategic mode selection 210 ★

Full documentation available on GitHub

View Source Repository