skills.rest
nikhilsitaram
nikhilsitaramCOMMUNITY
Explore all skills by this author →
GitHub

test-audit

Audit test suites for weak assertions, flakiness, and isolation problems.

89|7|Updated Feb 25, 2026
Search Tags:#qa#audit#regression#coverage#assertions#tests#flakiness
One-click install
npx skills add https://github.com/nikhilsitaram/claude-caliper --skill test-audit-nikhilsitaram
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-audit
Source: https://github.com/nikhilsitaram/claude-caliper/tree/main/skills/test-audit
Command: npx skills add https://github.com/nikhilsitaram/claude-caliper --skill test-audit-nikhilsitaram

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, git, sed, and includes scripts (resource) components.

What problem does it solve?

This Skill audits test suites for quality gaps that let regressions slip through, such as weak assertions, flaky tests, poor isolation, and false-pass risk.

Core Features & Use Cases

  • Repo-wide or scoped audits: Review every test in a repository, a single directory, or only changed tests.
  • Test-health analysis: Flag brittle assertions, missing coverage, smell patterns, and suite-level problems across layers.
  • Fix workflow support: Surface findings, route approved fixes to implementers, and optionally record testing conventions in the repo.
  • Use case: Ask it to evaluate a recent pull request's tests before merge and identify which checks would fail to catch a regression.

Quick Start

Ask the test-audit skill to review the repository's tests or changed tests and report the highest-risk gaps first.

Frequently Asked Questions about test-audit

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

FAQPage Schema
How do I find weak assertions and flaky tests before a release?▼

You can audit your test suite to detect weak assertions, flakiness, and isolation problems before regressions escape, covering unit, component, integration, and end-to-end layers.

Can I check only the changed tests in a recent pull request?▼

Yes, you can scope the test audit to only changed tests within a recent pull request, analyzing false-pass risks and routing approved fixes to implementers before merge.

What is the best way to audit test coverage and smell patterns repo-wide?▼

The best way to audit test coverage and smell patterns repo-wide is to run a comprehensive test-health analysis that flags brittle assertions and suite-level problems across all test layers.

Does this test audit tool require specific dependencies to run?▼

Yes, the test audit tool requires bash, git, and sed dependencies to execute its scripts for scope detection, test discovery, and parallel subagent analysis.

How are testing conventions recorded after a test suite audit?▼

After a test suite audit, testing conventions are optionally synthesized and recorded in the repository, while approved fixes are routed to implementers for dispatch.

Related Skills

Explore More Software Engineering Skills→
nguyennd93nguyennd93

test-helpers

Generate TypeScript test helper files with assertions and factory functions.

Community
Advanced
erclxerclx
2

aitk-ask

Query documentation indexes and wiki files for cited repository answers.

Community
Intermediate
kynoptickynoptic
1

Auditing Test Quality

Audit test suites for vanity tests and mock-to-assertion ratios.

Community
Intermediate
Chang-Shih-YungChang-Shih-Yung

health

Aggregate type checker, linter, and test results into a 0-10 composite score.

Community
Advanced