eng-tdd
/eng-tdd
Naprawia błąd metodą najpierw test, gdy istnieje jasna i tania ścieżka testu regresji, przy prośbie o TDD albo test regresji.
- Autor
- jpoehnelt ↗
- Repozytorium
- skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 23.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 23.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Naprawia błąd metodą najpierw test, gdy istnieje jasna i tania ścieżka testu regresji, przy prośbie o TDD albo test regresji.
Oryginalny opis (EN)
Fix a bug test-first when there is a clear, cheap regression test path. Use when the user asks for TDD, a failing test, or a regression test, or when the bug has an obvious cheap local test target.
Jak działa
- Workflow
- If a failing test is impractical
- Guardrails
- Verify
Podgląd SKILL.md
--- name: eng-tdd description: Fix a bug test-first when there is a clear, cheap regression test path. Use when the user asks for TDD, a failing test, or a regression test, or when the bug has an obvious cheap local test target. --- # TDD bug fix Repo facts (from AGENTS.md or CLAUDE.md): the test policy (some repos require coverage for every behavior change, others allow a test only where a branch's behavior is uncertain), the test runner per package, and the single-test command. Follow the policy; when it rules out a new test, skip to the closest executable check below. When the test path is clear and cheap, make the broken behavior executable before changing production code. The goal is a focused regression test that fails before the fix and passes after it. Do not force a test when it is impractical: broad harness setup, brittle mocks, slow end-to-end infrastructure, production-only state, vague reproduction steps, or large unrelated fixture churn. Use the closest useful verification instead. ## Workflow 1. **Understand the bug.** Identify intended behavior, current behavior, the affected path, and the smallest observable reproduction. 2. **Choose the narrowest executable check.** Prefer the unit, component, or integration test style already used for that code, in the location the repo uses (often colocated as `foo.test.ts`), run with the repo's single-test command. If no practical path is obvious, do not create one just to satisfy the workflow. 3. **Write the failing test first.** Add the smallest test that would have caught the bug. It encodes intended behavior, not the current implementation. 4. **Run it before fixing.** Confirm it fails for the intended reason. If it passes or fails for an unrelated reason, correct the test first. 5. **Fix the bug.** Make the smallest production change that satisfies the intended behavior and keeps nearby contracts. 6. **Rerun the test.** Confirm it passes. ## If a failing test is impractical Use the closest executable check: a targeted script, a manual reproduction command, browser automation, a snapshot comparison, or a focused integration check. Prefer no new test over a bad test. A bad test mostly tests mocks, encodes implementation details, depends on timing or global state, needs expensive infrastructure for a small fix, or would be deleted right after proving the fix. ## Guardrails - Do not change tests to match a wrong implementation. - Do not weaken assertions unless the expected behavior genuinely changed and you can say why. - Keep the test focused on the bug. No fixture churn or unrelated coverage. - If the bug is flaky, make the test deterministic and document the signal it locks down. - If the bug exposes a broader class of failures, land the focused regression first, then consider sibling coverage. ## Verify - Name the check that failed before the fix and the failure it produced. - Name the passing run after the fix and any nearby validation. - If failing-before evidence is missing, say why and name the closest check used.
Wersje
W bazie nie ma innych skilli o nazwie eng-tdd.
Migawka bazy z 13.11.2026 · wersja paczki 214ab29792ea (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 1 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100tdd
Stosuje TDD tylko na jawną prośbę o TDD, padający test lub test regresji albo gdy błąd ma tani, lokalny cel testowy. - 100tdd
Stosuje TDD tylko na jawną prośbę o TDD, padający test lub test regresji albo gdy błąd ma tani, lokalny cel testowy. - 100tdd
Stosuje TDD tylko na jawną prośbę o TDD, padający test lub test regresji albo gdy błąd ma tani, lokalny cel testowy. - 100tdd
Pisze testy najpierw: buduje funkcję od czerwonego do zielonego przy uzgodnionych punktach styku albo naprawia błąd testem regresji. - 100tdd-pstack
Pisze nieudany test regresyjny przed poprawką błędu, gdy użytkownik prosi o TDD albo ma tani lokalny test. - 100tdd
Stosuje TDD tylko na wyraźne życzenie albo gdy błąd ma tani lokalny test; w innych przypadkach pomija go.