#testing
8 skillsRefactor Without Behavior ChangePin current behavior with characterization tests, then restructure in small always-green steps so the diff provably changes no behavior.Claude Code · CodingClaude CodeSKILL.mdRefactor Without Behavior ChangePin current behavior with characterization tests, then restructure in small always-green steps so the diff provably changes no behavior.Use when restructuring, renaming, extracting, or moving existing code where the requirement is that observable behavior stays identical.@libraryCodingCopilot Instructions for Java Enterprise ServicesJava 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.GitHub Copilot · CodingGitHub Copilotcopilot-instructions.mdCopilot Instructions for Java Enterprise ServicesJava 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 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.@libraryCodingAider Conventions for Small, Test-Backed DiffsA 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.Aider · CodingAider.md (generic)Aider Conventions for Small, Test-Backed DiffsA 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.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.@libraryCodingTDD Red-Green-Refactor LoopEnforces a strict test-first cycle where every line of production code exists only to make a failing test pass.Claude Code · CodingClaude CodeSKILL.mdTDD Red-Green-Refactor LoopEnforces a strict test-first cycle where every line of production code exists only to make a failing test pass.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.@libraryCodingVitest Test Authoring RulesTest-writing rules enforcing arrange-act-assert structure, behavior-based naming, strict mock boundaries, and minimal snapshots.Cursor · CodingCursor.cursor/rules/*.mdcVitest Test Authoring RulesTest-writing rules enforcing arrange-act-assert structure, behavior-based naming, strict mock boundaries, and minimal snapshots.Attach to test files in Vitest projects to keep specs readable, deterministic, and focused on behavior rather than implementation details.@libraryCodingCopilot Instructions for .NET / C# ProjectsC# conventions for Copilot: nullable reference types treated as errors, Async suffix on every awaitable method, CancellationToken plumbing, and xUnit patterns that scale.GitHub Copilot · CodingGitHub Copilotcopilot-instructions.mdCopilot Instructions for .NET / C# ProjectsC# conventions for Copilot: nullable reference types treated as errors, Async suffix on every awaitable method, CancellationToken plumbing, and xUnit patterns that scale.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#.@libraryCodingSystematic Debugging LoopA four-phase debugging discipline — reproduce, isolate, hypothesize, verify — that forbids writing a fix before the root cause is proven.Claude Code · CodingClaude CodeSKILL.mdSystematic Debugging LoopA four-phase debugging discipline — reproduce, isolate, hypothesize, verify — that forbids writing a fix before the root cause is proven.Use when a bug, failing test, or unexplained behavior appears and the temptation is to start editing code based on a guess.@libraryCodingGo Service Project InstructionsCLAUDE.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.Claude Code · CodingClaude CodeCLAUDE.mdGo Service Project InstructionsCLAUDE.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 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.@libraryCoding