exp-test-maintainability

# Test Maintainability Assessment Analyze .NET test code for maintainability issues: duplicated boilerplate, copy-paste test methods, and structural repetition across test methods and classes. Produce a report of refactoring opportunities with concrete before/after suggestions. The goal is analysis only — do not modify any files. ## When to Use - User asks to find duplicated code or boilerplate in tests - User wants to know where test code can be DRY-ed up - User asks to reduce test duplication, improve test readability, or clean up test boilerplate - User asks for refactoring opportunities in a test suite - User wants to identify shared setup or teardown candidates - User asks "what patterns repeat across my tests?" - User wants to centralize test data, introduce builders or helpers ## When Not to Use - User wants to write new tests from scratch (use `writing-mstest-tests`) - User wants to detect anti-patterns or code smells (use `test-anti-patterns`) - User wants to actually perform the refactoring (help them directly, this skill only analyzes) ## Inputs | Input | Required | Description | |-------|----------|-------------| | Test code | Yes | One or more test files or a test project directory to analyze | | Production code | No | The code under test, for context on what abstractions might help | | Scope | No | Whether to analyze within a single class or across multiple classes | ## Workflow ### Step 1: Gather the test code Read all test files the user provides or ...