test-analysis-extensions

Provides language-specific reference files for polyglot test analysis skills.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Test analysis skills need framework-specific lookup tables (assertion APIs, skip annotations, sleep patterns, tag syntax) that vary across languages, and this Skill centralizes those per-language reference files so analysis stays language-neutral. ## Core Features & Use Cases - Extension Discovery: Lists available per-language extension files covering .NET, Python, TypeScript, Java, Go, Ruby, Rust, Swift, Kotlin, PowerShell, and C++. - Capability Tagging: Each extension declares per-capability support such as tag support levels (auto-edit, report-only, convention-based) so skills can gate behavior safely. - Use Case: When the test-quality-auditor agent analyzes a pytest codebase, it calls this Skill to locate extensions/python.md, then reads it to learn pytest fixtures, markers, and skip conventions before auditing assertion quality. ## Quick Start Ask the agent to find the test analysis extension file for your project's language and test framework before running a test quality audit.

Frequently Asked Questions about test-analysis-extensions

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

FAQPage Schema
How do I find framework-specific test conventions for a test quality audit?

Call this Skill to list available extension files, then read the one matching your language and framework, such as dotnet.md for xUnit or python.md for pytest. Each file documents assertion APIs, skip annotations, and lifecycle hooks for that ecosystem.

What languages and test frameworks do the test analysis extensions cover?

Extensions cover .NET (MSTest, xUnit, NUnit, TUnit), Python (pytest, unittest), TypeScript (Jest, Vitest, Mocha), Java (JUnit, TestNG), Go, Ruby, Rust, Swift, Kotlin, PowerShell Pester, and C++ (GoogleTest, Catch2, doctest).

Can I use test-analysis-extensions directly for analyzing my tests?

No, it is a lookup provider, not an analysis skill. It is invoked by the test-quality-auditor agent and polyglot analysis skills that need framework-specific detection tables before performing their own analysis.

What happens if my test framework has no extension file?

Fall back to the closest matching extension, for example using python.md pytest semantics for Pest, and note the gap in the report. When detection is uncertain, read multiple extension files rather than guessing.

How does the test-tagging skill know if it can edit tags in my language?

Each extension declares a tag-support capability: auto-edit means a canonical attribute exists that the skill can safely write, report-only means audits without edits, and convention-based means tags exist only via naming or comment conventions.