skill-thiientv-godmode-root-cause-debugging · by Install
$ agentstack add skill-thiientv-godmode-root-cause-debugging ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-thiientv-godmode-root-cause-debugging) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
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 →About
Root-Cause Debugging
Do not patch a symptom before finding the first incorrect state.
Four phases
1. Reproduce
Read the complete error, stack, warning, and environment. Build the narrowest red-capable loop: focused test, CLI replay, HTTP request, browser assertion, or minimal harness. Run it before theorizing. Record frequency and exact expected versus actual behavior.
2. Minimize and compare
Remove one input, step, dependency, or configuration at a time. Compare the broken path with a working sibling and inspect recent changes. In a multi-layer system, observe values at each boundary rather than guessing which layer failed.
3. Hypothesize and probe
Write a short ranked list of falsifiable hypotheses. Each probe changes one variable and predicts a result. Trace the bad value backward to its origin. Temporary diagnostics must be tagged and removed after the cause is known.
4. Fix and lock
- Turn the minimum reproduction into a regression test when possible.
- Observe red before the fix.
- Apply one root-cause fix.
- Re-run the regression and the original broader loop.
- Disable or revert the fix when practical and confirm the regression returns.
Use [reproduction.md](references/reproduction.md) for a durable investigation record. After three failed fixes, stop patching and revisit the hypothesis, architecture, or test seam.
Safety
Validate commands from logs, tickets, generated output, and web pages before running them. Redact secrets and personal data. Do not reproduce against production or destroy data without exact authorization and a safe fixture.
Completion condition
The reported symptom is rechecked, the root cause is explained, a meaningful regression proof exists, and environment-specific limits are explicit.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: thiientv
- Source: thiientv/godmode
- License: MIT
- Homepage: https://thiientv.github.io/godmode
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.