skills.rest
kapilvirenahuja
kapilvirenahujaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

map-test-surface

Enumerate test files and extract tested subjects with assertion estimates into test-surface.yaml.

3|Updated Jan 25, 2026
Search Tags:#coverage gap#test framework detection#blast radius analysis#test inventory#assertion counting#static code scan
One-click install
npx skills add https://github.com/kapilvirenahuja/garura --skill map-test-surface
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: map-test-surface
Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/skills/map-test-surface
Command: npx skills add https://github.com/kapilvirenahuja/garura --skill map-test-surface

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Garura helps you quickly understand what tests exist in a codebase and what they actually cover, so you can compute blast radius and find coverage gaps without manually hunting through files.

Core Features & Use Cases

  • Detects test frameworks from config and conventions, such as pytest, jest/vitest, mocha, go test, and more.
  • Enumerates test files and subjects by deriving what each test block exercises from imports and test names.
  • Estimates scope metrics including test counts, approximate assertion counts, and useful tags like skip/xfail/slow/integration markers.
  • Emits test-surface.yaml as a structured inventory that downstream steps can use for coverage-gap analysis and blast-radius computation.

Quick Start

Ask the AI to map the test surface for your repository by generating test-surface.yaml under your chosen output directory.

Frequently Asked Questions about map-test-surface

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

FAQPage Schema
How do I map test coverage gaps in a repository without running the test suite?▼

You can map test coverage gaps by statically scanning the codebase to enumerate test files, extract tested subjects via imports, and estimate assertion counts into a structured inventory without executing tests.

What is a test surface inventory and how does it help compute blast radius?▼

A test surface inventory is a structured map of existing test files, subjects, and assertion estimates. It provides the necessary metrics to compute blast radius and identify uncovered code areas during repository audits.

Can I detect multiple test frameworks like pytest and jest during a static code scan?▼

Yes, static code scanning can detect test frameworks like pytest, jest, vitest, mocha, and go test by reading repository configuration files and applying standard naming conventions.

How do I generate a test-surface.yaml file for my codebase?▼

To generate a test-surface.yaml file, instruct the AI to map the test surface for your repository by aggregating per-file metrics, scope tags, and framework detections into your chosen output directory.

Does test inventory enumeration work for both unit and integration test layouts?▼

Yes, test inventory enumeration applies to typical unit and integration test layouts, extracting quality signals like skip, xfail, slow, and integration markers across standard file patterns.

What are the limitations of estimating test coverage through static code scanning?▼

Static code scanning estimates coverage by aggregating file metrics and assertion counts rather than measuring runtime execution paths, meaning it maps the test surface structure without verifying actual runtime branch coverage.

Related Skills

Explore More Software Engineering Skills→
pekralpekral

readme-generator

Generate README, CONTRIBUTING, and SECURITY files from repository source code.

Community
Intermediate
baskarajatibaskarajati

differential-review

...

Community
Advanced
Artifex1Artifex1
4

security-auditor

Automate interactive security audits of codebases using the Map & Probe methodology.

Community
Advanced
rube-derube-de
10

test

Detect test frameworks, run suites with coverage, and report findings as a GitHub issue.

Community
Advanced