test-audit

Analyze test and Storybook coverage gaps with structured reports.

15|7|Updated Sep 11, 2023
One-click install
npx skills add https://github.com/huseyindeniz/vite-react-dapp-template --skill test-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-audit
Source: https://github.com/huseyindeniz/vite-react-dapp-template/tree/main/.claude/skills/test-audit
Command: npx skills add https://github.com/huseyindeniz/vite-react-dapp-template --skill test-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill analyzes test coverage, Storybook coverage, and test quality to help you raise confidence in your codebase.

Core Features & Use Cases

  • Test Coverage Check: Ensures a baseline of 60% test coverage for business logic.
  • Storybook Coverage Check: Maintains at least 40% story coverage for UI components.
  • Test TODOs Check: Detects TODO/FIXME/HACK comments in test files to surface gaps.
  • Report Generation: Optional comprehensive markdown reports for sharing results.

Quick Start

Run all checks to evaluate test coverage and storybook quality: node ./.claude/skills/test-audit/scripts/run_all_checks.mjs

Frequently Asked Questions about test-audit

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

FAQPage Schema
How do I check test coverage in my JavaScript codebase?

Test coverage analysis identifies gaps in your test suite by measuring what percentage of business logic is covered by tests. This Skill enforces a baseline of 60% test coverage, analyzing source files against test files to surface uncovered code and provide remediation guidance.

What's the best way to ensure Storybook coverage for UI components?

Storybook coverage tracks whether your UI components have accompanying story files for documentation and testing. This Skill maintains a minimum 40% Storybook coverage threshold, detecting components without stories and recommending which ones to prioritize.

How do I identify incomplete or skipped tests in my test files?

Incomplete tests often contain TODO, FIXME, or HACK comments marking unfinished work. This Skill scans test files for these markers, surfacing gaps in test implementation and providing structured reports to guide remediation.

Can I generate a report of test coverage and quality metrics?

Yes. This Skill produces optional comprehensive markdown reports summarizing test coverage, Storybook coverage, and test quality gaps. Reports include metrics, detected incomplete tests, and actionable recommendations for improving confidence in your codebase.

What files and repositories does this tool analyze?

This Skill applies to repositories containing business logic, UI components, and testing infrastructure. It analyzes source files, test files, story files, and code comments to identify coverage gaps and quality issues.

Why should I maintain test and Storybook coverage thresholds?

Coverage thresholds establish baseline confidence in your codebase. Enforcing minimum test coverage (60%) and Storybook coverage (40%) prevents regression, ensures UI components are documented, and catches incomplete or skipped tests before they impact production.