test-tagging

Analyzes test suites and tags each test with standardized trait classifications across multiple frameworks.

Updated Aug 9, 2026
One-click install
npx skills add https://github.com/adinj00/player-performance --skill test-tagging-adinj00
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-tagging
Source: https://github.com/adinj00/player-performance/tree/main/.agents/skills/test-tagging
Command: npx skills add https://github.com/adinj00/player-performance --skill test-tagging-adinj00

SYSTEM DOCUMENTATION & REQUIREMENTS

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 integration tests. 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: Classifies tests with traits like positive, negative, boundary, critical-path, smoke, regression, integration, performance, and security across .NET, Python, JS/TS, Java, Go, Ruby, Rust, Swift, Kotlin, PowerShell, and C++. - Capability-aware editing: Auto-edits source when the framework has canonical tag syntax (MSTest, xUnit, NUnit, pytest, JUnit 5, RSpec, Pester), and emits report-only output for frameworks without one (Go testing, plain Jest/Vitest, Rust). - Trait distribution summary: Produces a summary table showing trait counts, positive-to-negative ratios, and critical-path coverage gaps. - Use Case: Point the Skill at a pytest project to tag every test with @pytest.mark.positive or @pytest.mark.negative, then review the generated distribution report to find untested critical paths. ## Quick Start Analyze the test suite in my project and tag each test with the appropriate trait classifications, then show me the trait distribution summary.

Frequently Asked Questions about test-tagging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I tag tests with categories in pytest or xUnit?

In pytest, add @pytest.mark.<trait> decorators above each test function; in xUnit, add [Trait("Category", "<trait>")] attributes. This Skill detects the framework automatically and applies the correct canonical tag syntax for each test.

How to audit test suite coverage of positive and negative tests?

Run a trait-tagging analysis that classifies each test by its assertions and inputs, then generates a distribution table showing counts and percentages per trait. Tests asserting success are positive; tests asserting exceptions or error handling are negative.

Does test tagging work with Go or Jest test files?

Go standard testing and plain Jest/Vitest have no canonical tag attribute, so they are treated as report-only: the analysis emits a Markdown table of suggested tags without modifying source. Edits only occur if you confirm a project convention like build tags or file suffixes.

Can a single test have multiple trait tags?

Yes, a test can carry multiple traits, such as both negative and boundary. Every test should receive at least positive or negative, with additive traits like boundary, integration, or critical-path layered on top.

When should I not use automated test trait tagging?

Do not use it for writing new tests, running or filtering tests, or migrating between test frameworks. It only classifies and labels existing tests; use dedicated test-writing or test-running tools for those tasks.