skills.rest
adinj00
adinj00COMMUNITY
Explore all skills by this author →
GitHub

test-analysis-extensions

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

Updated Aug 9, 2026
Search Tags:#code quality#reference data#polyglot#test analysis#test frameworks#test tagging#assertion detection
One-click install
npx skills add https://github.com/adinj00/player-performance --skill test-analysis-extensions-adinj00
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-analysis-extensions
Source: https://github.com/adinj00/player-performance/tree/main/.agents/skills/test-analysis-extensions
Command: npx skills add https://github.com/adinj00/player-performance --skill test-analysis-extensions-adinj00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Test analysis skills need framework-specific lookup tables (assertion APIs, skip annotations, sleep patterns, tag syntax) that differ across languages, and this Skill centralizes those per-language reference files so analysis stays accurate across polyglot codebases. ## Core Features & Use Cases - Per-Language Reference Files: Ships extension files for .NET, Python, TypeScript/JavaScript, Java, Go, Ruby, Rust, Swift, Kotlin, PowerShell, and C++ covering their major test frameworks. - Standardized Capability Categories: Each file documents test discovery, assertion detection, sleep patterns, skip/ignore markers, setup/teardown, mystery guest indicators, integration markers, and tag support. - Tag Support Gating: Declares auto-edit, report-only, or convention-based tagging capability per language so the test-tagging skill behaves safely. - Use Case: When auditing a mixed Jest and Mocha TypeScript repository, the test-quality-auditor agent reads typescript.md to correctly detect unawaited promises, .only commits, and framework-specific assertion forms. ## Quick Start Invoke this skill to list the available extension files, then read the extension file matching your codebase's language and test framework before running test analysis.

Frequently Asked Questions about test-analysis-extensions

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

FAQPage Schema
How do I analyze test quality across multiple programming languages?▼

Detect the codebase's primary language and test framework, then read the matching extension file before analysis. Each file documents the same capability categories, so analysis skills remain language-neutral while using framework-specific detection rules.

What test frameworks are covered by the extension files?▼

Extensions cover MSTest, xUnit, NUnit, TUnit, pytest, unittest, Jest, Vitest, Mocha, Jasmine, node:test, JUnit 4/5, TestNG, Go testing with testify, RSpec, Minitest, Rust built-in tests, XCTest, Swift Testing, Kotest, Pester v5, GoogleTest, Catch2, and doctest.

Can test tagging be automated for every language?▼

No. Languages like .NET, Java, Python, Kotlin, Swift Testing, PowerShell, and C++ support auto-edit tagging via canonical attributes. Go, TypeScript, and Rust default to report-only or convention-based modes because they lack a canonical per-test tag syntax.

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

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

Why should bare assert statements not be flagged in pytest analysis?▼

Bare assert is the canonical pytest assertion form and produces rich failure diffs through pytest's assertion rewriting. The python.md extension explicitly calibrates analysis skills to avoid flagging it as a missing-framework-API smell.

Related Skills

Explore More Software Engineering Skills→
breeze4breeze4

stack-detection

Detect project toolchains and CI/CD stacks from manifest files.

Community
Intermediate
FittyArFittyAr
1

test-analysis-extensions

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

Community
Intermediate
dotBeepsdotBeeps

go-check

Run go vet, golangci-lint, and go test on Go code.

Community
Intermediate
OutlineDrivenOutlineDriven
5

cleanup-codebase

Remove dead fields, redundant wrappers, and stale configurations from code.

Official
Intermediate