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 and coverage gaps. ## Core Features & Use Cases - Cross-language trait tagging: Classifies tests with 15 standardized traits (positive, negative, boundary, critical-path, smoke, regression, integration, performance, security, concurrency, and more) across .NET, Python, Java, Go, Ruby, Rust, Swift, Kotlin, PowerShell, JS/TS, and C++ frameworks. - Capability-aware editing: Auto-edits source when the framework has canonical tag syntax (MSTest, xUnit, NUnit, pytest, JUnit 5, RSpec, Pester, Catch2), and falls back to report-only mode for frameworks without one (Go testing, plain Jest/Vitest, GoogleTest). - Trait distribution reporting: Produces a summary table showing trait counts and percentages, plus observations on positive-to-negative ratios and critical-path coverage. - Use Case: Point the Skill at a pytest project to tag every test with markers like @pytest.mark.negative and receive a distribution report revealing that only 5% of tests cover error paths. ## Quick Start Analyze the test suite in my project and tag each test with the appropriate trait categories, then show me the trait distribution summary.
