test-audit

Analyze layer-wise test coverage gaps and generate Markdown remediation reports.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ryu-qqq/conventionHub --skill test-audit-ryu-qqq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-audit
Source: https://github.com/ryu-qqq/conventionHub/tree/main/.claude/skills/test-audit
Command: npx skills add https://github.com/ryu-qqq/conventionHub --skill test-audit-ryu-qqq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes layer-wise test coverage gaps and documents recommended remediation strategies to improve test quality and safety.

Core Features & Use Cases

  • Layer-wise audit: identifies missing tests and scenario gaps across domain, application, and adapter layers.
  • Actionable recommendations: generates prioritized remediation actions and documentation.
  • Use Case: imagine you have multiple modules with uneven test coverage; run this Skill to produce a consolidated report with the gaps and suggested fixes.

Quick Start

Run the test-audit tool for a specific layer/package to identify coverage gaps and generate a remediation report.

Frequently Asked Questions about test-audit

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

FAQPage Schema
How do I identify test coverage gaps across domain, application, and adapter layers?▼

Layer-wise test coverage gap analysis evaluates missing tests, fixtures, methods, edge cases, and state transitions across specified packages. It audits domain, application, and adapter layers to pinpoint scenario gaps and pattern violations in your codebase.

How do I generate a remediation report for missing tests and edge cases?▼

Generating a remediation report for missing tests involves auditing specific layers and packages for coverage gaps. The process outputs a Markdown report at claudedocs/test-audit/ detailing identified missing fixtures, methods, edge cases, and pattern violations with recommended fixes.

Can I audit test coverage for a single package instead of a full layer?▼

Yes, you can audit test coverage for a single package. The audit scope supports both per-package and full-layer analysis, allowing you to target specific modules within domain, application, or adapter layers for missing tests and remediation actions.

What is the best way to check for pattern violations in my test suite?▼

Checking for pattern violations is handled through a layer-wise audit that examines domain, application, and adapter layers. It identifies missing tests, edge cases, and pattern violations, then generates a Markdown report with recommended remediation actions.

Does test coverage auditing detect missing state transitions and fixtures?▼

Test coverage auditing detects missing state transitions and fixtures by applying audit requirements to the specified layers. It checks for missing tests, missing fixtures, missing methods, edge cases, and pattern violations, documenting all findings in a report.

How do I document recommended fix options for uneven test coverage?▼

Documenting recommended fix options for uneven test coverage involves running a layer-wise audit to identify gaps. The audit generates a Markdown report containing prioritized remediation strategies and fix options for missing tests across the analyzed packages.