#testing

8 skills

Skills

Refactor Without Behavior Change

Pin current behavior with characterization tests, then restructure in small always-green steps so the diff provably changes no behavior.

Use when: Use when restructuring, renaming, extracting, or moving existing code where the requirement is that observable behavior stays identical.

GoodPrompts Library

0 0 0

GitHub Copilot.github/copilot-instructions.md

Copilot Instructions for Java Enterprise Services

Java service conventions for Copilot: immutable-by-default classes, Optional only as a return type, JUnit 5 with AssertJ, and exceptions that carry context instead of being swallowed.

Use when: Use in a Java 17+ backend service when you want Copilot to produce modern, immutable, well-tested Java instead of setter-heavy beans and bare try/catch blocks.

GoodPrompts Library

0 0 0

Aider.md

Aider Conventions for Small, Test-Backed Diffs

A CONVENTIONS.md for Aider that enforces minimal diffs, a failing test before every fix, and a hard rule against touching files outside the stated task.

Use when: Load with `aider --read CONVENTIONS.md` (or via .aider.conf.yml) on any project where you want edits to stay small, scoped, and verified by tests rather than sprawling refactors.

GoodPrompts Library

0 0 0

Claude CodeSKILL.md

TDD Red-Green-Refactor Loop

Enforces a strict test-first cycle where every line of production code exists only to make a failing test pass.

Use when: Use when implementing a new feature or bugfix and you want the test suite to drive the design instead of being written after the fact.

GoodPrompts Library

0 0 0

Cursor.cursor/rules/*.mdc

Vitest Test Authoring Rules

Test-writing rules enforcing arrange-act-assert structure, behavior-based naming, strict mock boundaries, and minimal snapshots.

Use when: Attach to test files in Vitest projects to keep specs readable, deterministic, and focused on behavior rather than implementation details.

GoodPrompts Library

0 0 0

GitHub Copilot.github/copilot-instructions.md

Copilot Instructions for .NET / C# Projects

C# conventions for Copilot: nullable reference types treated as errors, Async suffix on every awaitable method, CancellationToken plumbing, and xUnit patterns that scale.

Use when: Use in a .NET 8+ solution when you want Copilot suggestions to respect nullable annotations, async conventions, and your xUnit test layout instead of producing 2015-era C#.

GoodPrompts Library

0 0 0

Claude CodeSKILL.md

Systematic Debugging Loop

A four-phase debugging discipline — reproduce, isolate, hypothesize, verify — that forbids writing a fix before the root cause is proven.

Use when: Use when a bug, failing test, or unexplained behavior appears and the temptation is to start editing code based on a guess.

GoodPrompts Library

0 0 0

Claude CodeCLAUDE.md

Go Service Project Instructions

CLAUDE.md for a Go backend service: package layout, error wrapping with %w, table-driven tests, and context propagation rules an agent must follow on every handler.

Use when: Use in a Go HTTP/gRPC service repository so agents write idiomatic Go — wrapped errors, table tests, contexts passed all the way down — instead of patterns imported from other languages.

GoodPrompts Library

0 0 0