tests

Map test suite structure and metadata from local test directories.

Updated May 3, 2026
One-click install
npx skills add https://github.com/jreakin/jre-vidget --skill tests-jreakin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tests
Source: https://github.com/jreakin/jre-vidget/tree/main/.claude/skills/generated/tests
Command: npx skills add https://github.com/jreakin/jre-vidget --skill tests-jreakin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers quickly locate, understand, and validate the structure and intent of test suites within a codebase, providing a clear map of tests, symbols, and entry points to improve onboarding and maintenance.

Core Features & Use Cases

  • Cataloging test files and symbols across tests directories to reveal coverage and organization.
  • Linking test entry points (e.g., tests/test_*.py) and related sources to execution flows and dependencies for quick navigation.
  • Guiding exploration by summarizing key files, entry points, and execution flows to accelerate debugging and refactoring.

Quick Start

Inspect the tests area and use the overview to navigate to test files and references.

Frequently Asked Questions about tests

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

FAQPage Schema
How do I map test suite structure and execution flow in a local repository?

Test coverage analysis aggregates key test files and related sources to reveal organization and coverage. It links test entry points to execution flows, accelerating debugging and refactoring by summarizing the structure.

What's the best way to explore and validate test suites for code analysis?

Mapping test entry points involves linking test files like tests/test_*.py to related sources in directories such as src/jre_vidget/*. This reveals dependencies and execution flows to accelerate debugging and refactoring.

Can I use this approach to catalog test files and symbols across directories?

Parsing SKILL.md frontmatter extracts metadata to catalog listed entry points. Aggregating these entry points with key files creates a cohesive overview of the test suite's structure and dependencies.

Does test suite mapping work without external dependencies?

Parsing local test directories and aggregating files from paths like src/jre_vidget/* builds a cohesive overview. This reveals test coverage, dependencies, and execution flow without external tools.