1. Habit
  2. Skills
  3. Test Anti-Patterns skill
dotnet · 4K installs

Test Anti-Patterns skill
Runs by itself, test files change.

Tests that prove nothing get caught.

Install the Test Anti-Patterns skill and make it a habit: follow https://gethabit.dev/skills/dotnet/test-anti-patterns.md

  1. 1Copy
  2. 2Paste into Claude Code, Codex or Cursor
  3. 3It runs by itself

4K installs6K starsMIT licenceSource on GitHub ↗

Test Anti-Patterns

by dotnet · 4K installs

The skill

Test anti-patterns audits a test file or suite in any language and produces a severity-ranked report of tests that verify nothing, swallowed exceptions, flaky or order-dependent tests, duplication and magic values.

Only when you ask.

The habit

Tests that prove nothing get caught.

↻ Runs by itselftest files change

How the habit works.
You don't have to.

Three questionsWhen does it start? How does it check its work? What does it remember?

01

It starts by itself

test files change. Runs in GitHub Actions or Claude Code routine.

  • ↻ test files change
  • pull_request paths: **/*Tests*/**, **/test_*.py, **/*.test.*

02

It checks its work

complete, consistent report. If a check fails, it tells you.

  • ✓the reviewed test count equals the discovered test count
  • ✓summary counts equal the listed findings
  • ✓every Critical and High finding has a fix with an exact expected value

03

It remembers

test audit log. The next run reads it first: open Critical and High findings from earlier audits.

loops/test-anti-pattern-audit-loop/log.md

One run, step by step.
Then it stops.

Stop ruleStops after the changed test files of one pull request.

  1. 01

    Detect language

    Find the test files in the workspace and identify language and framework.

  2. 02

    Inventory tests

    List every test method and class-level fixture before reading bodies.

  3. 03

    Scan the catalog

    Check each test against the Critical, High, Medium and Low anti-patterns.

  4. 04

    Check production code

    Open the production symbol behind each suspicious test to judge the oracle.

  5. 05

    Calibrate severity

    Apply the severity rules and the not-an-issue list, never inflating findings.

  6. 06

    Report

    Write summary, findings with locations and fixes, adjacent gaps and positive observations.

What it may do.
Nothing more.

Safe by defaultIt writes only in its own folder and asks you before anything goes out.

Is it for you?
Use it when it fits.

Quick checkRead both lists. If the left one sounds like you, the Test Anti-Patterns skill helps.

Use it when

  • ✓ You ask if your tests are good
  • ✓ Your tests are flaky
  • ✓ You review a test pull request

Skip it when

  • – You want new tests written
  • – You want to run the tests

Questions

Test Anti-Patterns skill, answered.

Does it edit the tests?

No. It produces a diagnostic report; writing fixes belongs to other skills.

Is a pytest bare assert a problem?

No. The skill lists it as the canonical form, not an issue.

Which languages does it cover?

It is polyglot, with examples for .NET, Python, JS/TS, Java, Go, Ruby, Rust, PowerShell and C++.

How do I install the Test Anti-Patterns skill?

Copy the prompt at the top into your agent. It installs the skill from dotnet/skills and sets up the habit. Or run npx skills add dotnet/skills --skill test-anti-patterns.

Is the Test Anti-Patterns skill free?

Yes. It is published under MIT. Habit is free too.

Test Anti-Patterns. Now as a habit.

Install the Test Anti-Patterns skill and make it a habit: follow https://gethabit.dev/skills/dotnet/test-anti-patterns.md

  • Free
  • No account
  • Undo in one line

All dotnet skills →More code skills →

Works in

  • Claude Code
  • Codex
  • Cursor
  • ChatGPT
  • Claude app

Made by dotnet, published under MIT. Habit links to the original and never changes it. Is this your skill?

Copying didn't work here. Select the line and copy it by hand.