testing-posture

Analyzes codebase test files and frameworks to identify coverage gaps.

121|11|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/glaucia86/repocheckai --skill testing-posture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-posture
Source: https://github.com/glaucia86/repocheckai/tree/main/.github/skills/testing-posture
Command: npx skills add https://github.com/glaucia86/repocheckai --skill testing-posture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps identify gaps in your testing strategy by analyzing the presence, structure, and coverage of your test suites.

Core Features & Use Cases

  • Test Presence Check: Verifies if test files and directories exist.
  • Framework Detection: Identifies common testing frameworks like Jest or Vitest.
  • Coverage Gaps: Highlights potential missing test types (e.g., unit vs. integration).
  • Use Case: Before a major release, use this Skill to quickly assess if your testing strategy is comprehensive enough to catch critical bugs.

Quick Start

Analyze the testing posture of the current project.

Frequently Asked Questions about testing-posture

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

FAQPage Schema
How do I analyze test coverage and structure in my codebase?

To analyze test coverage and structure, this Skill evaluates the presence of test files and directories to identify testing frameworks like Jest or Vitest and highlights missing unit or integration tests.

What is the best way to identify missing unit or integration tests?

Identifying missing unit or integration tests is done by analyzing test directories and scripts to assess heuristic-based coverage and highlight gaps in your testing strategy.

Does this testing posture analysis support Vitest and Jest frameworks?

Yes, this testing posture analysis supports common frameworks by detecting specific configurations and dependencies for Vitest and Jest within your project's test scripts.

How do I check if my testing strategy is comprehensive before a release?

To check if your testing strategy is comprehensive before a release, evaluate test presence and structure to quickly determine if current coverage catches critical bugs.

What are the limitations of heuristic-based test coverage assessment?

The limitation of heuristic-based test coverage assessment is that it evaluates gaps by analyzing directory structure and scripts rather than executing tests to measure actual runtime code coverage.

Can I use this to verify if test files and directories exist in my project?

Yes, you can verify if test files and directories exist in your project through a test presence check that evaluates your codebase structure for required testing components.