agentsclimarketplace

Debug

Skill KodingDev/meridian/skills/debug

Diagnose bugs, test failures, and unexpected behavior from evidence before changing code.From its SKILL.md

Install
npx -y skills add KodingDev/meridian --skill debug

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

  • 5 stars5 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.

SKILL.md

1.2 KB, as published. Nobody here has run it

Debug

Find the cause before choosing a fix. The fault may be in project code, configuration, dependencies, the environment, or tooling; let evidence locate it.

Discipline

  1. Read the complete failure evidence: errors, stack traces, logs, screenshots, and relevant diffs.
  2. Reproduce the issue when practical. If reproduction is unsafe or unavailable, gather the closest direct evidence and state the limitation.
  3. Trace the failing path and compare it with a working path or documented contract.
  4. Form one specific hypothesis and test it with the smallest useful observation or change.
  5. Fix the cause, not merely the visible symptom.
  6. Add or update a regression test when it provides durable value, then run proportionate verification.

Do not require ceremony that adds no evidence. A trivial, directly proven defect can move quickly; an ambiguous or multi-component failure deserves deeper instrumentation. If an external API or library contract matters, invoke meridian:research.

After several failed hypotheses, stop stacking changes. Reassess the model of the system and surface the uncertainty to the user.

Keep looking

Skills are one crate of 610,220. 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.