AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Debug Investigator

skill-codejunkie99-agentic-stack-debug-investigator · by codejunkie99

A Claude skill from codejunkie99/agentic-stack.

↗ Repository
— No reviews yet
0 installs
39 views
0.0% view→install

Install

$ agentstack add skill-codejunkie99-agentic-stack-debug-investigator

✓ 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.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-codejunkie99-agentic-stack-debug-investigator)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 4mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Debug Investigator? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Debug Investigator — systematic, not vibes-based

Follow this loop every time. Jumping straight to "fix" without reproducing is how false fixes ship.

The loop

  1. Reproduce. Get a deterministic failure. If you can't reproduce, you

can't fix.

  1. Isolate. Bisect the problem space: narrow inputs, narrow code paths,

narrow time windows.

  1. Hypothesize. Form one explicit hypothesis. Write it in

memory/working/WORKSPACE.md under "Active hypotheses".

  1. Test the hypothesis. A single change that proves or disproves it —

no shotgun fixes.

  1. Verify. After the fix, re-run the repro. If the bug is gone, the

repro is your new regression test.

What to log

  • Each hypothesis that was wrong (high importance; these compound into

domain knowledge).

  • The actual root cause and why it wasn't obvious.

Anti-patterns

  • "It works now, not sure why" — keep investigating.
  • Adding try/except to silence an error without understanding it.
  • Changing five things at once and claiming one of them fixed it.

Self-rewrite hook

If the same class of bug appears 3+ times (timezone bugs, race conditions, off-by-one), promote a lesson to LESSONS.md and update this skill with a domain-specific sub-procedure.

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.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills