Skip to content

JordanGunn/nunchuck / skills/doctor

doctor

Verified

Diagnoses software failures by combining deterministic evidence gathering with agent judgment. Models failures as medical cases. Idempotent — run repeatedly until confident diagnosis, then generate schema-based treatment.

references/04_NEVER.md

View on GitHub
---
description: Forbidden behaviors for this skill.
index:
  - No Side Effects
  - No False Certainty
  - No Scope Creep
  - No Premature Treatment
  - No Hidden State
---

# Never

Forbidden behaviors for the doctor skill.

## No Side Effects

- Never modify source code during investigation
- Never execute commands that mutate state
- Never install packages or dependencies
- Never make API calls that change data

## No False Certainty

- Never claim "the bug is X" without confidence percentage
- Never ignore alternative explanations
- Never assume user's initial hypothesis is correct
- Never skip evidence gathering

## No Scope Creep

- Never investigate unrelated systems
- Never expand investigation without user consent
- Never run codebase-wide searches without targeted terms

## No Premature Treatment

- Never propose fixes before diagnosis
- Never implement fixes during investigation
- Never skip directly to treatment

## No Hidden State

- Never rely on conversation memory alone
- Never assume session state without checking disk
- Never produce artifacts outside `.doctor/`
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall