quality-audit

Identify gaps and weaknesses in test suites using static analysis cues.

4|1|Updated May 31, 2015
One-click install
npx skills add https://github.com/samcdavid/dotfiles --skill quality-audit-samcdavid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-audit
Source: https://github.com/samcdavid/dotfiles/tree/main/claude/skills/quality-audit
Command: npx skills add https://github.com/samcdavid/dotfiles --skill quality-audit-samcdavid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies gaps and weaknesses in test suites by evaluating coverage quality, fidelity, architecture, and risk alignment to improve confidence in code changes.

Core Features & Use Cases

  • Structural coverage analysis: mapping production paths to tests and identifying missing paths.
  • Test fidelity assessment: evaluating whether tests verify intended behavior and edge cases.
  • Regression risk evaluation: assessing how changes could impact release stability and risk.
  • Test architecture review: reviewing organization, suites, and mocking strategy to improve maintainability.

Quick Start

Initiate a quality audit on your current codebase to identify test coverage gaps and fidelity issues.

Frequently Asked Questions about quality-audit

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

FAQPage Schema
How do I identify gaps and weaknesses in my test suite?

To identify gaps and weaknesses in your test suite, perform a quality audit that evaluates coverage, fidelity, architecture, and risk alignment using static analysis cues and test runner metadata to output structured findings.

What is test fidelity and how does it affect code changes?

Test fidelity evaluates whether tests verify intended behavior and edge cases. High fidelity ensures that tests accurately capture production paths, directly improving confidence and trust in code changes.

How do I perform a deep QA audit on a large codebase?

Perform a deep QA audit by evaluating test definitions, coverage reports, and test structure. The audit applies to codebases of varying sizes and languages, mapping production paths to tests to identify missing routes.

Can I use static analysis to assess regression risk in unit and integration tests?

Yes, you can assess regression risk by applying static analysis cues and test runner metadata to evaluate how changes could impact release stability and risk across both unit and integration tests.

What is the best way to review test architecture and mocking strategy?

The best way to review test architecture is auditing test organization, suites, and mocking strategy. This evaluates maintainability and aligns test structure with risk assessment to improve overall suite quality.