Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

Loslegen

write-failing-test-first

Sterne2

Forks0

Aktualisiert12. Juli 2026 um 12:09

Before fixing any bug, write a test that reproduces it and watch it fail. Use for every bug fix.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

YaoYinYing

YaoYinYing/REvoDesign

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Softwarequalitätssicherungsanalysten und -testerInformatik- und Mathematikberufe·SOC 15-1253

SKILL.md

readonly

name	write-failing-test-first
description	Before fixing any bug, write a test that reproduces it and watch it fail. Use for every bug fix.
when_to_use	fixing a bug, "make X work", a reported defect

Write the Failing Test First

The only proof you fixed a bug is a test that failed before and passes after.

Write the smallest test that reproduces the reported behavior.
Run it. Watch it fail for the right reason (read the assertion, not just red).
Now fix the code.
Run the test. It passes. Run the FULL suite — you didn't break anything else. If you can't write the test easily, the architecture is telling you something (tight coupling). Say so. Never: fix first, test after (you'll write a test that passes regardless). Never: skip the watch-it-fail step.

Mehr aus diesem Repository

gleiches Repository

adversarial-verify

YaoYinYing/REvoDesign

Review a diff against the goal spec assuming the code is BROKEN. The reviewer that lives in the maker's head always agrees with itself — this pulls review into a hostile, separate pass. Invoke after every code change before marking work done.

2026-07-122

authz-check

YaoYinYing/REvoDesign

Verify that an endpoint checks ownership, not just authentication. Use on any handler that reads or mutates user data.

2026-07-122

bisect-regression

YaoYinYing/REvoDesign

Find the exact commit that introduced a bug. Use when something worked before and broke, and you don't know which change did it.

2026-07-122

changelog-from-diff

YaoYinYing/REvoDesign

Turn a set of commits or a diff into a clean, user-facing changelog entry. Use before a release or PR description.

2026-07-122

clean-commits

YaoYinYing/REvoDesign

Turn messy WIP into clean, atomic commits with messages that explain why. Use before opening a PR.

2026-07-122

context-budget

YaoYinYing/REvoDesign

Keep the agent's context lean so accuracy doesn't collapse. Use on long sessions, big files, or when the agent starts hallucinating.

2026-07-122

name	write-failing-test-first
description	Before fixing any bug, write a test that reproduces it and watch it fail. Use for every bug fix.
when_to_use	fixing a bug, "make X work", a reported defect

Write the Failing Test First

The only proof you fixed a bug is a test that failed before and passes after.

Write the smallest test that reproduces the reported behavior.
Run it. Watch it fail for the right reason (read the assertion, not just red).
Now fix the code.
Run the test. It passes. Run the FULL suite — you didn't break anything else. If you can't write the test easily, the architecture is telling you something (tight coupling). Say so. Never: fix first, test after (you'll write a test that passes regardless). Never: skip the watch-it-fail step.