test-tagging

Analyzes test suites and applies standardized trait tags across multiple languages and frameworks.

1|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/D1ssolve/craft-agents --skill test-tagging-d1ssolve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-tagging
Source: https://github.com/D1ssolve/craft-agents/tree/main/skills/test-tagging
Command: npx skills add https://github.com/D1ssolve/craft-agents --skill test-tagging-d1ssolve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Test suites often lack consistent categorization, making it hard to audit coverage of negative cases, critical paths, or security scenarios. This Skill classifies every test with a standardized trait taxonomy and either applies framework-native tag attributes or produces a report. ## Core Features & Use Cases - Standardized Trait Taxonomy: Classifies tests into 15 fixed traits including positive, negative, boundary, critical-path, smoke, regression, integration, performance, security, and concurrency. - Multi-Language Support: Works with .NET (MSTest, xUnit, NUnit, TUnit), Python (pytest), Java (JUnit 5, TestNG), JavaScript/TypeScript, Go, Ruby, Rust, Swift, Kotlin, PowerShell, and C++. - Capability-Aware Editing: Auto-edits source when the framework has canonical tag syntax, falls back to report-only output for frameworks without one, and respects project conventions for convention-based frameworks. - Use Case: Point the Skill at an xUnit test project to tag every test with [Trait("Category", ...)] attributes and receive a trait distribution summary showing positive-to-negative ratios and critical-path coverage gaps. ## Quick Start Analyze the test project in the tests folder and tag each test with the appropriate trait categories, 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 xUnit or MSTest?

Run the Skill against your test project and it detects the framework automatically. For xUnit it adds [Trait("Category", "...")] attributes; for MSTest it adds [TestCategory("...")], preserving any existing tags without duplication.

How to audit test suite coverage of negative and critical-path tests?

Use the audit scope to classify every test into the standardized trait taxonomy without editing source. The Skill outputs a trait distribution table showing counts and percentages, plus observations on positive-to-negative ratios and critical-path gaps.

Does test tagging work with Go or plain Jest tests?

Go standard testing, plain Jest/Vitest, Rust, XCTest, and GoogleTest are treated as report-only because they lack canonical tag syntax. The Skill emits a Markdown table of suggested tags and recommends a project convention instead of editing source.

Can pytest tests be tagged automatically with markers?

Yes, pytest supports auto-edit via @pytest.mark.<name> decorators. The Skill classifies each test function by analyzing names, assertions, and inputs, then inserts the appropriate markers adjacent to existing decorators.

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 categorizes existing tests; use dedicated test-writing or test-running tools for those tasks.