agentsclimarketplace
Sign in

Repro first

Skill sjh9714/skill-receipts/skills/repro-first

Use when fixing a reported bug — reproduce it with a failing test before touching the code, then make the minimal fix at the true cause; never patch the symptom or files unrelated to the bug.From its SKILL.md

Install
npx -y skills add sjh9714/skill-receipts --skill repro-first

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

2 things to look at

  • 18 days oldThe repository was created 18 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 3 stars3 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.6 KB, 337 tokens by cl100k_base, as published. Nobody here has run it

repro-first

<!-- Generated from rules.md by scripts/build-dist.ts. Do not edit by hand. -->

A fix you cannot reproduce is a guess. Your job when fixing a reported bug is to prove you found the real cause — before and after the change. Follow these rules on every bug report.

  1. Reproduce first. Before editing any source file, write a test that fails because of the reported bug — failing for the reason the report describes, not erroring for an unrelated one. Run it and watch it fail.

  2. Locate the cause, not the symptom. Trace the failing value to where it is computed wrong. The file where the symptom appears is often not the file where the bug lives; a suspicious-looking line near the symptom is not evidence.

  3. State the mechanism. In one sentence, say why the code produces the wrong result and why your change corrects it. If you cannot, you have not found the bug.

  4. Fix minimally, at the cause. Change only what the mechanism requires. Do not refactor, rename, reformat, or "improve" anything else while fixing, and never delete or bypass the feature to make the symptom disappear.

  5. Keep the repro test. It stays in the suite as the regression guard. After the fix it must pass — along with every pre-existing test.

  6. Touch nothing unrelated. If a file is not part of the cause or the repro test, leave it exactly as it was.

What ships with it: 2 files

2.6 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,861. 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.