test-audit

Audits codebase testing across major frameworks to identify weaknesses and risks.

29|1|Updated Jul 18, 2015
One-click install
npx skills add https://github.com/joshmanders/dotfiles --skill test-audit-joshmanders
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-audit
Source: https://github.com/joshmanders/dotfiles/tree/main/claude/skills/test-audit
Command: npx skills add https://github.com/joshmanders/dotfiles --skill test-audit-joshmanders

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit teams and codebases to measure and improve confidence in test suites by identifying gaps, inconsistencies, and risks that undermine reliability.

Core Features & Use Cases

  • Phase-driven two-step workflow: Phase 1 defines methodology in plan mode; Phase 2 executes the audit against approved plans.
  • Structured reporting: inventory, classification of tests, and an executive findings report.
  • Risk-aware recommendations: identify false confidence signals and prioritize fixes.

Quick Start

Enter plan mode to define the methodology, then await user approval before proceeding to Phase 2.

Frequently Asked Questions about test-audit

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

FAQPage Schema
How do I audit my Jest or pytest test suite for reliability gaps?

To audit test suite reliability, you define a methodology in plan mode, approve it, then execute the audit to classify tests and output an executive findings report identifying false confidence signals and prioritized fixes.

What is a phase-driven test quality audit and how does it work?

A phase-driven test quality audit works by enforcing a two-step workflow where Phase 1 defines the evaluation methodology and Phase 2 executes the audit against the approved plan, ensuring structured reporting and risk-aware recommendations.

Can I use this audit methodology with Go testing and PHPUnit?

Yes, you can apply this audit methodology to Go testing and PHPUnit, as it evaluates test quality across multiple stacks including Jest, Vitest, Pest, and pytest to inventory tests and quantify software confidence.

How do I identify false confidence signals in my test suites?

You identify false confidence signals by executing a structured audit that classifies tests, inventories coverage, and generates an executive findings report to highlight inconsistencies and risks undermining reliability.

What's the best way to report on test suite quality across different frameworks?

The best way to report on test suite quality is using a structured audit workflow that inventories tests, classifies them, and outputs an executive findings report with risk-aware recommendations for improving reliability.