test-tagging

Analyze MSTest, xUnit, or NUnit test methods and apply standardized trait tags.

1|Updated May 21, 2026

Search Tags:#nunit #dotnet #xunit #test management #mstest #trait tagging #test taxonomy

Ready to run

npx skills add https://github.com/1k-off/umbraco-observability-playground --skill test-tagging

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-tagging
Source: https://github.com/1k-off/umbraco-observability-playground/tree/main/.agents/skills/test-tagging
Command: npx skills add https://github.com/1k-off/umbraco-observability-playground --skill test-tagging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of messy or invisible test intent by helping you consistently label each test as positive, negative, boundary, critical-path, and other agreed traits so coverage patterns are easy to audit.

Core Features & Use Cases

Trait audit and classification: Examines an existing test suite and determines which standardized trait tags each test method should receive.
Optional tagging and reporting: Supports audit, tag, or both so you can review classification before making changes.
Framework-aware tagging: Detects MSTest, xUnit, or NUnit and applies the correct attribute syntax without inventing new trait values.
Distribution summary: Produces a trait distribution report to reveal over- or under-covered categories (and lists uncertain items for manual review).

Quick Start

Use the test-tagging skill to analyze your test project folder and generate a trait distribution report.

Frequently Asked Questions about test-tagging

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

FAQPage Schema

How do I standardize test traits across MSTest, xUnit, and NUnit projects?▼

You can audit test intent by running the skill in audit mode to review classification before making changes. It examines your test suite and determines which standardized trait tags each method should receive without immediately modifying the code.

What is the best way to audit test coverage for positive, negative, and boundary scenarios?▼

The skill enforces taxonomy constraints so every test is tagged at least with positive or negative, and outputs a trait distribution summary revealing over- or under-covered categories. It also lists uncertain items for manual review to validate your test suite.

Does this test tagging tool support existing test suites with predefined traits?▼

Yes, it supports existing MSTest, xUnit, or NUnit projects by detecting the framework and applying the correct attribute syntax. It preserves your existing traits without duplication while enforcing that every test is tagged at least with positive or negative.

Can I review test classifications before applying tags to my dotnet test methods?▼

Yes, you can review classifications by using the audit mode to examine the test suite and generate a trait distribution report without modifying code. This allows you to validate the proposed positive, negative, boundary, and critical-path trait assignments first.