agentsclimarketplace

Repo debugging ledger

Skill markoblogo/abvx-agent-skills/skills/repo-debugging-ledger

Reviewable capability layer for coding agents. Portable skills, delivery gates, workflow patterns, and verification-first engineering.

Install
npx -y skills add markoblogo/abvx-agent-skills --skill repo-debugging-ledger

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.2 KB, 403 tokens by cl100k_base, as published. Nobody here has run it

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 / falsified

Probe 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 rg and 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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.