What problem does it solve? Test suites often lack consistent metadata, making it impossible to know the balance of positive versus negative tests, whether critical paths are covered, or which tests are slow, flaky, or integration-heavy. This Skill audits an existing test suite and applies a standardized trait taxonomy so teams gain visibility into test distribution. ## Core Features & Use Cases - Cross-language trait tagging: Works with .NET (MSTest/xUnit/NUnit/TUnit), Python (pytest), JS/TS (Jest/Vitest), Java (JUnit/TestNG), Go, Ruby, Rust, Swift, Kotlin, PowerShell, and C++ frameworks. - Capability-aware editing: Auto-edits source when the framework has canonical tag syntax (e.g., [TestCategory], @pytest.mark, @Tag), and emits a report-only Markdown table for frameworks without one (Go, plain Jest, plain Rust). - Trait distribution summary: Produces a summary table showing counts and percentages per trait, plus observations on positive/negative ratios and critical-path coverage. - Use Case: Point the Skill at a pytest project to tag every test with traits like positive, negative, boundary, and critical-path, then review the generated distribution report to find coverage gaps. ## Quick Start Analyze the test suite in my project and tag each test with the standardized trait taxonomy, then show me the trait distribution summary.
