AgentStack
SKILL verified MIT Self-run

Diagnose

skill-markoblogo-abvx-agent-skills-diagnose · by markoblogo

Debug coding failures through reproduction, ranked hypotheses, narrow fixes, and verification. Use when a bug, regression, flaky test, performance failure, or inconsistent behavior is broken, slow, throwing, or hard to reproduce and the task needs disciplined diagnosis instead of guessed fixes.

No reviews yet
0 installs
13 views
0.0% view→install

Install

$ agentstack add skill-markoblogo-abvx-agent-skills-diagnose

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Diagnose? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Diagnose

The core job is to build a reliable feedback loop. Without one, hypotheses are weak.

Phase 1: Feedback Loop

Create the smallest useful pass/fail signal:

  • failing test;
  • CLI command with fixture;
  • HTTP request against local server;
  • browser script;
  • replayed trace or payload;
  • small harness around the relevant function;
  • repeated flake trigger with counted failure rate.

If no loop can be built, state what was tried and ask for logs, traces, access, or permission to instrument.

Phase 2: Reproduce

Confirm the loop matches the user's symptom, not a nearby failure. Capture exact error text, wrong output, timing, network failure, or UI state.

For nondeterministic issues, raise the reproduction rate with repetition, stress, seeded randomness, timing controls, and isolation.

Phase 3: Hypothesize

Write 3-5 ranked hypotheses before editing. Each must include:

Hypothesis:
Prediction:
Probe:
Result:
Status:

Test one variable at a time. Update rankings as evidence arrives.

Phase 4: Instrument

  • Prefer debugger, REPL, targeted logs, traces, or profiler over broad logging.
  • Tag temporary instrumentation with a unique marker such as [DEBUG-7b3c].
  • Remove all temporary instrumentation before finalizing.
  • For performance regressions, measure first and fix second.

Phase 5: Fix And Regression Test

If a correct seam exists, turn the minimized repro into a failing regression check before the fix. If no correct seam exists, document that as an architecture gap.

Apply the smallest fix supported by evidence, then rerun:

  • the regression check;
  • the original feedback loop;
  • relevant project checks.

Final Report

Include root cause, winning hypothesis, files changed, verification, debug cleanup, and residual risk.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.