skills.rest
xiaolai
xiaolaiCOMMUNITY
Explore all skills by this author →
Website𝕏@xiaolaiGitHub

tooling-catalog

Catalogs test runners, coverage tools, and probe commands across programming language ecosystems.

10|7|Updated Feb 23, 2026
Search Tags:#tdd#mutation testing#property-based testing#ci#test runners#coverage tools#lane configuration
One-click install
npx skills add https://github.com/xiaolai/tdd-guardian-for-claude --skill tooling-catalog-xiaolai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tooling-catalog
Source: https://github.com/xiaolai/tdd-guardian-for-claude/tree/main/skills/tdd-guardian/tooling-catalog
Command: npx skills add https://github.com/xiaolai/tdd-guardian-for-claude --skill tooling-catalog-xiaolai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Configuring test lanes for an unfamiliar repository requires knowing which test runner, coverage tool, report format, and mutation tool each language ecosystem uses, and getting a command wrong produces silent failures or unparseable reports. ## Core Features & Use Cases - Per-language tooling references: Covers JavaScript/TypeScript, Python, JVM, .NET, Go, Rust, C/C++, Ruby, PHP, Elixir, Haskell, and more, with exact test, coverage, and dry-run probe commands for each. - Coverage format matrix: Documents nine coverage report formats (LCOV, Cobertura, JaCoCo, Clover, and others), which metrics each actually measures, and which merge as a true per-line union. - Property-testing library index: Names the property-based testing library for each ecosystem so specification-strength requirements can be met where a library exists. - Use Case: When setting up a coverage-gated test lane in a Rust repository, consult the catalog to learn that cargo llvm-cov --lcov is the preferred coverage command and that cargo mutants handles mutation testing. ## Quick Start Ask the assistant to detect this repository's test tooling and configure a coverage-gated test lane using the tooling catalog.

Frequently Asked Questions about tooling-catalog

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

FAQPage Schema
How do I detect which test runner a repository uses?▼

Check manifest files and dependencies: package.json with vitest or jest signals those runners, pyproject.toml with pytest config signals pytest, and pom.xml or build.gradle indicate Maven or Gradle. The catalog maps each manifest fingerprint to its ecosystem reference file.

What coverage format should I use for merging multiple test lanes?▼

Use a per-line format like LCOV or Cobertura so reports merge as a true union. Summary-only formats like istanbul-summary fall back to weighted averages that double-count lines exercised by two lanes.

Does Go coverage report function and branch metrics?▼

No, go-cover measures statements only and reports functions and branches as null. Set those thresholds to 0 rather than accepting a permanent warning from the gate.

Why does my .NET coverage report path keep changing?▼

dotnet test writes coverage under a GUID directory that is not stable. Use the coverlet MSBuild form with /p:CoverletOutput to pin the report to a fixed path the gate can read.

What property-based testing library should I use in Python?▼

Use hypothesis, which also supports stateful testing for state-machine invariants. The catalog names one property-testing library per ecosystem and marks ecosystems like Zig and Lua where none is in wide use.

What should I do when a language is not in the catalog?▼

Read the CI config and project README for the documented test command, then ask the user directly. Check whether the tool can emit LCOV or Cobertura, since either format makes the lane fully supported.

Related Skills

Explore More Software Engineering Skills→
breeze4breeze4

stack-detection

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

Community
Intermediate
BedriftsgrafenBedriftsgrafen

Safe Push

Validate backend and frontend code locally before pushing commits.

Official
Intermediate
Nandansai08Nandansai08
1

coverage-analysis

Analyzes code coverage reports to identify untested branches and prioritize testing effort.

Community
Intermediate
sheawinklersheawinkler
78

code-wiki

Generate a codebase wiki with Mermaid architecture diagrams and Markdown module documentation.

Community
Advanced