Repo Debugging Ledger
Debug repositories with a hypothesis ledger, checked locations, and loop-breaking discipline. Use when tests fail, CI fails, behavior regresses, local tooling errors, flaky bugs appear, or an investigation risks repeated searches, repeated commands, circular hypotheses, or unverified fixes.
Install
$ agentstack add skill-markoblogo-abvx-agent-skills-repo-debugging-ledger ✓ 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-markoblogo-abvx-agent-skills-repo-debugging-ledger) 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
Repo Debugging Ledger
Use this skill as a lightweight overlay on normal debugging. Its job is to prevent loops and untested assumptions.
Start With A Repro Signal
Create the smallest useful pass/fail loop:
- unit/integration test,
- CLI command,
- HTTP request,
- browser script,
- fixture replay,
- log assertion,
- repeated flake trigger.
If no loop exists, state the best available signal and what artifact would make it deterministic.
Hypothesis Ledger
Before editing, write or mentally maintain 3-5 ranked hypotheses:
H1:
Prediction:
Probe:
Result:
Status: open / supported / falsifiedProbe one variable at a time. Prefer evidence that distinguishes between hypotheses.
Checked-Location Ledger
Track what has already been inspected:
Checked:
- file/function/command:
evidence:
conclusion:Do not reopen the same file, rerun the same broad search, or repeat the same command unless a phase change makes it newly relevant: new failing signal, new stack trace, changed code, or a narrowed hypothesis.
Search And Instrumentation
- Use
rgand targeted file reads first. - Search for exact symbols, error text, config keys, route names, and call sites before broad terms.
- Tag temporary logs with a unique marker such as
[DEBUG-7b3c]. - Remove temporary instrumentation before finalizing.
- If a likely area is exhausted, broaden to a different subsystem instead of cycling through the same files.
Fix Discipline
- Add or identify a regression check before the fix when a reasonable seam exists.
- Keep the fix scoped to the supported hypothesis.
- Re-run the original repro signal after the fix.
- Run the project’s normal checks before finalizing, or explain the blocker.
Final Report
Include:
- root cause or best-supported cause,
- files changed,
- verification run,
- residual risks or missing test seam.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: markoblogo
- Source: markoblogo/abvx-agent-skills
- License: MIT
- Homepage: https://abvx.xyz/work/abvx-agent-skills
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.