matt-bat/got-skills / skills/diagnose-before-fix
diagnose-before-fix
VerifiedUse for debugging or remediation work when reported symptoms may not be the true root cause; verify the cause independently before applying fixes, even when the user suggests one.
Diagnose Before Fix
Quick Index (Action-Routed)
Read First (All Actions)
MissionTrigger RuleCause Verification Standard
Action Modules (Read As Needed)
- Reproducing and isolating failures:
Symptom CaptureHypothesis Testing
- Choosing a fix path:
Root Cause Decision Rule
- Confirming the repair:
Verification After Fix
Output
Output Contract
Mission
Separate observed symptoms from verified causes so fixes address the actual failure mode.
Trigger Rule
Use this skill when:
- a user reports a bug, error, regression, or broken behavior
- the user suggests a cause but it is not yet proven
- multiple plausible root causes exist
- a quick patch would risk masking the true problem
Treat user-provided causes as hypotheses, not facts, until verified.
Cause Verification Standard
Before changing behavior:
- reproduce the symptom or inspect direct evidence
- test the proposed cause explicitly
- compare at least one alternative explanation when feasible
- only fix the verified root cause
If the root cause cannot be verified:
- say so plainly
- limit changes to safe mitigation
- preserve evidence for the next pass
Symptom Capture
Record the failure in concrete terms:
- what fails
- where it fails
- when it fails
- what changed recently
Hypothesis Testing
Test from cheapest to most informative:
- direct logs or stack traces
- targeted reproduction
- narrow code-path inspection
- focused unit or integration check
Root Cause Decision Rule
Do not patch a visible symptom unless:
- the cause is verified, or
- the change is explicitly a temporary mitigation and is labeled as such
Verification After Fix
After a fix:
- rerun the reproducer or targeted check
- confirm the original symptom is gone
- confirm adjacent behavior still works
Output Contract
When using this skill, provide:
- symptom description
- tested hypotheses
- verified cause or verified uncertainty
- fix applied or mitigation chosen
- post-fix validation summary
Related Skills
- Regression Prevention: protect adjacent behavior during the fix.
- Effective Testing Methods: add the smallest useful validation for the verified cause.
- Order of Operations: sequence diagnosis before mutation.
- Thoughtful Approach: avoid overfitting the fix to a symptom.
- Scripted Command Execution: run deterministic reproductions and probes.
Least-resistance reasoning
Prefer the simplest explanation that fits the evidence. Test the cheapest reversible hypothesis first, and add complexity only when a failed test or new evidence requires it. Keep the claim falsifiable by naming what would confirm or disconfirm it.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |