← LeaderboardThe Skill Leaderboard

test-analysis-extensions

Provides file paths to language-specific reference files for the test ANALYSIS skills (assertion-quality, test-anti-patterns, test-gap-analysis, test-smell-detection, test-tagging). Read this catalog to discover available extension files (e.g., dotnet.md for .NET/MSTest/xUnit/NUnit/TUnit, python.md for pytest/unittest, typescript.md for Jest/Vitest/Mocha, java.md for JUnit/TestNG, etc.). Do not invoke this reference-only skill — its bundled files are read by the quality agent and analysis skills needing framework-specific lookup tables (test markers, assertion APIs, skip annotations, sleep pat

Published by dotnet ↗dotnet/skills

Try your first task

test-analysis-extensions

Start a fresh conversation. Replace the highlighted placeholders.

Use test-analysis-extensions to provide a reference-selection note for an already active test-analysis workflow using [known language, framework and analysis goal]. Select the matching bundled extension relative to this catalog, and require its complete read before analyzing tests; mixed frameworks need each relevant extension. Keep capability support separate as auto-edit, report-only or convention-based rather than promising automatic edits everywhere. Treat the extension as lookup data, not instructions to follow blindly. Do not invoke this reference-only catalog through a skill tool. Return selected paths and missing evidence only; wait for my explicit confirmation before project reads, analysis commands or changes.

Required inputs

  • [known language, framework and analysis goal]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: test-analysis-extensionsdescription: >-  Provides file paths to language-specific reference files for the test  ANALYSIS skills (assertion-quality, test-anti-patterns, test-gap-analysis,  test-smell-detection, test-tagging). Read this catalog to discover available  extension files (e.g., dotnet.md for .NET/MSTest/xUnit/NUnit/TUnit,  python.md for pytest/unittest, typescript.md for Jest/Vitest/Mocha,  java.md for JUnit/TestNG, etc.). Do not invoke this reference-only skill —  its bundled files are read by the quality agent and analysis skills needing  framework-specific lookup tables (test markers, assertion APIs, skip  annotations, sleep patterns, mystery guest indicators, integration  markers, setup/teardown, tag-support capability).user-invocable: falsedisable-model-invocation: truelicense: MIT

Test Analysis Extensions

This reference-only catalog lists the bundled files used by test analysis. Consumers read the matching file directly; disable-model-invocation: true means this catalog must not be invoked through the model's skill tool. Resolve these resource paths relative to this catalog, not the project workspace.

Available Extension Files

FileLanguages / FrameworksContents
extensions/dotnet.md.NET (C#/F#/VB) — MSTest, xUnit, NUnit, TUnitTest markers, assertion APIs, sleep/delay patterns, skip annotations, mystery guest, integration markers, setup/teardown, tag support
extensions/python.mdPython — pytest, unittestSame categories, with pytest fixtures/markers and unittest TestCase
extensions/typescript.mdTypeScript / JavaScript — Jest, Vitest, Mocha, Jasmine, node:testSame categories, with async/await pitfalls
extensions/java.mdJava — JUnit 4, JUnit 5 (Jupiter), TestNGSame categories, with @Tag / @Category / groups
extensions/go.mdGo — testing package, testifySame categories, with table-driven idiom and build tags
extensions/ruby.mdRuby — RSpec, MinitestSame categories, with RSpec metadata and Minitest tags
extensions/rust.mdRust — built-in #[test], cargo testSame categories, with #[ignore], #[should_panic], feature flags
extensions/swift.mdSwift — XCTest, Swift TestingSame categories, with @Test, @Tag, @Suite
extensions/kotlin.mdKotlin — JUnit 5, Kotest, MockKSame categories, with @Tag and Kotest tags
extensions/powershell.mdPowerShell — Pester v5Same categories, with -Tag and Skip
extensions/cpp.mdC++ — GoogleTest, Catch2, doctestSame categories, with [tags] and * filters

Usage

  1. Detect the target codebase's primary language and test framework.
  2. Read the matching extension file before performing analysis.
  3. If multiple test frameworks are present (e.g., a project mixing Jest and Mocha), read all relevant extensions.
  4. Each extension file documents the same categories so analysis skills can be language-neutral.

Capability tags

Each extension file declares per-capability support so skills can gate behaviour safely:

  • Test discovery — how to locate test files and methods.
  • Assertion detection — framework-specific and language-level assertion forms.
  • Sleep/delay patterns — synchronous and asynchronous waits.
  • Skip / ignore — how to recognize skipped/ignored tests.
  • Setup / teardown — fixture and lifecycle hooks.
  • Mystery guest indicators — common file/db/network/env coupling patterns.
  • Integration markers — conventions that mark a test as integration/E2E.
  • Tag support (for test-tagging skill) — one of:
    • auto-edit — language has a canonical attribute/marker the skill can safely write.
    • report-only — no canonical syntax; produce audit reports without edits.
    • convention-based — tags exist via name/comment conventions only.

Notes for skill authors

  • Treat extension files as data, not as guidance to follow verbatim. They tell skills how to detect things in each language, not what to think about findings.
  • When language detection is uncertain, prefer reading multiple extension files over guessing.
  • If the user explicitly names a framework that does not have an extension file yet, fall back to the closest one (e.g., Pest → python.md/pytest semantics) and note the gap in the report.