test-analysis-extensions

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

1|Updated Jul 27, 2026
One-click install
npx skills add https://github.com/FittyAr/Cardscape --skill test-analysis-extensions-fittyar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-analysis-extensions
Source: https://github.com/FittyAr/Cardscape/tree/main/.agents/skills/test-analysis-extensions
Command: npx skills add https://github.com/FittyAr/Cardscape --skill test-analysis-extensions-fittyar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Test analysis skills need framework-specific knowledge (assertion APIs, skip annotations, sleep patterns, tag syntax) that varies across languages, and this Skill centralizes that lookup data so analysis stays language-neutral. ## Core Features & Use Cases - Per-language extension files: Eleven reference files covering .NET, Python, TypeScript, Java, Go, Ruby, Rust, Swift, Kotlin, PowerShell, and C++ test frameworks. - Uniform capability categories: Each file documents test discovery, assertion detection, sleep patterns, skip/ignore, setup/teardown, mystery guest indicators, integration markers, and tag support. - Tag-support gating: Declares auto-edit, report-only, or convention-based capability so the test-tagging skill knows whether it can safely write tags. - Use Case: The test-quality-auditor agent analyzing a pytest codebase reads extensions/python.md to get pytest fixture, marker, and assertion patterns before running test-gap-analysis. ## Quick Start Ask the test-quality-auditor agent to analyze your test suite and it will load the extension file matching your language and framework.

Frequently Asked Questions about test-analysis-extensions

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

FAQPage Schema
How do test analysis skills handle multiple programming languages?▼

They load a per-language extension file containing framework-specific lookup tables for assertions, markers, and lifecycle hooks. The analysis logic stays language-neutral while detection patterns come from the matching extension file.

Which test frameworks are covered by the extension files?▼

Eleven files 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).

What happens if my test framework has no extension file?▼

The skill falls back to the closest matching extension, such as using python.md pytest semantics for Pest, and notes the gap in the analysis report. Reading multiple extensions is preferred over guessing when detection is uncertain.

Can the test-tagging skill write tags in every language?▼

No. Each extension declares a tag-support level: auto-edit for languages with canonical tag syntax, report-only where no safe syntax exists, and convention-based where tags exist only via naming or comment conventions.

Should I invoke this skill directly for test analysis?▼

No. It is marked user-invocable false and disable-model-invocation true, meaning it is called internally by the test-quality-auditor agent and polyglot analysis skills that need framework-specific lookup tables.