What problem does it solve? Test suites often lack consistent categorization, making it impossible to know the balance of positive versus negative tests, whether critical paths are covered, or which tests are slow integration tests. This Skill audits an existing test suite and applies a standardized trait taxonomy (positive, negative, boundary, critical-path, smoke, regression, integration, performance, security, and more) to every test method. ## Core Features & Use Cases - Cross-language trait tagging: Works with .NET (MSTest/xUnit/NUnit/TUnit), Python (pytest), Java (JUnit 5/TestNG), JavaScript/TypeScript, Go, Ruby, Rust, Swift, Kotlin, PowerShell, and C++, using each framework's canonical tag syntax. - Capability-aware editing: Auto-edits source files when the framework has canonical tag attributes, emits a report-only Markdown table for frameworks without one, and respects project conventions for convention-based frameworks like Go build tags. - Trait distribution summary: Produces a summary table showing the count and percentage of each trait, with observations about positive-to-negative ratios and critical-path coverage gaps. - Use Case: Point the Skill at a large xUnit test project to audit coverage; it classifies each test by reading names, assertions, and setup, adds [Trait("Category", "...")] attributes without duplicating existing tags, and reports that only 12% of tests cover negative paths. ## Quick Start Analyze the test project in the tests folder and tag every test method with the appropriate trait categories, then show me the trait distribution summary.
