Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →dotnet/test-tagging
Analyzes test suites in any language and tags each test with standardized traits (positive, negative, critical-path, boundary, smoke, regression, integration, performance, security).
Passed 4 of 9 test cases with the skill, and 2 of 9 without it.
and 10 more in the full report
7 fixed2 passed either way11 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
Can you calculate the CRAP score for `OrderProcessor.ProcessOrder` method to evaluate its cyclomatic complexity against branch coverage?
| Checked | Without skill | With skill |
|---|---|---|
| Declines to calculate CRAP risk scores. | Missed | Passed |
| Directs the user to `crap-score` for method risk evaluations. | Missed | Passed |
The instructions your model reads when the skill loads.
Analyze an existing test suite in any supported language and apply a standardized set of trait tags to each test method, giving teams visibility into their test distribution (positive vs. negative, critical-path coverage, smoke tests, etc.).
Language-specific guidance: Call the
test-analysis-extensionsskill to discover available extension files, then read the file matching the target codebase. The extension file documents framework-specific tag attributes and a "tag-support capability" (auto-edit, report-only, or convention-based) that drives whether this skill modifies source files or only emits a report.
code-testing-agent for any language, or writing-mstest-tests for MSTest)run-tests for .NET; equivalent native runners elsewhere)test-anti-patterns or the matching analysis skill)coverage-analysis); raw coverage collection (use run-tests for .NET, native tooling otherwise)crap-score)test-gap-analysis)| Input | Required | Description |
|---|---|---|
| Test project or files | Yes | Path to the test project, folder, or specific test files to analyze |
| Scope | No | tag (apply canonical attributes, or a confirmed project convention), audit (report only), or both (default: both). Frameworks declared report-only always emit a report; convention-based frameworks edit only after the user confirms the convention. |
| Framework | No | Auto-detected. Override when detection fails. |
Use exactly these trait names and values. Do not invent new trait values outside this table.
| Trait Value | Meaning | Heuristics |
|---|---|---|
positive | Verifies expected behavior under normal/valid conditions | Asserts success, valid output, expected state, no exceptions for valid input |
negative | Verifies correct handling of invalid input, errors, or edge cases | Asserts exceptions, error codes, validation failures, rejects bad input |
boundary | Tests limits, thresholds, empty/null/None/nil inputs, min/max values | Operates on 0, -1, int.MaxValue / sys.maxsize / Number.MAX_SAFE_INTEGER / math.MaxInt64 / i32::MAX, empty string, null/None/nil/undefined, empty collection, boundary of valid range |
test cases passed, vs 2 / 9 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.