Skip to content
Skills Library
Programming · Testing

repro-first

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

Licence
MIT
Last repository change
30.07.2026

Assessment and security

96/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content31 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
1
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 30.07.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.

What it does and when to use it

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.

Original author description

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.

How it works

SKILL.md has no level-two headings · 33 lines, 243 words

SKILL.md preview
---
name: "repro-first"
description: "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."
---

# 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.
Files in this package (3)
  • SKILL.md 2 KB
  • rules.md 2 KB
  • skill.json 1 KB

Versions

The database has no other skills named repro-first.

Database snapshot: 13.11.2026 · package version fdf3e53e557f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90fix-bug
    Fixes a bug by reproducing it in a failing test first, then making the smallest change that turns it green. Use when something is "broken", "wrong", "fails", "doesn't work", throws an error, or a user or issue reports a bug.
  • 100e2e-repro
    Turn a bug report into one Playwright E2E test that is red on the bug and green once it is fixed, before anyone touches the code. Use when asked to reproduce a bug, write a regression test for a bug report, or confirm a reported bug is real. Reproduces live in a browser with playwright-cli first.
  • 100fix-bug
    Reproduce the bug, find the root cause, fix it there, and verify against the repro with prove-it-works. Use for any defect report; not for a direct fix in Normal mode when no repro-first loop is needed, and not for a performance regression (use tune-perf).
  • 95rs-bugfix
    Use when fixing a known or suspected bug — reproduce it with a failing test first, confirm independently, fix at the invariant (not the symptom), hunt the variants of the same root cause, prove the fix, and leave a regression guard and a reviewable report. Also for regressions…
  • 100bug-fix-verification
    Reproduce a reported bug, establish meaningful regression coverage when feasible, apply a minimal fix, and verify it. Use for debugging and regression work; not for general features or read-only audit.
  • 90qa-repro
    Run /qa-repro to reproduce a reported bug and shrink it to the smallest failing case. Use it before any diagnosis or verification. It triages deterministic versus intermittent, records the environment, captures the failure on video and the failure state in a screenshot, and…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.