proof-audit

Analyze JS/TS or Python test suites for speed, reliability, coverage, and quality.

69|8|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/tonone-ai/tonone --skill proof-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: proof-audit
Source: https://github.com/tonone-ai/tonone/tree/main/team/proof/skills/proof-audit
Command: npx skills add https://github.com/tonone-ai/tonone --skill proof-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit test suite health by identifying flaky tests, slow tests, coverage gaps, and anti-patterns, enabling proactive improvements.

Core Features & Use Cases

  • Health diagnostics: assess speed, reliability, coverage, and quality of the test suite.
  • Issue prioritization: surface critical, high, and low impact findings with actionable fixes.
  • Comprehensive reporting: deliver a structured health report including a score, quick wins, and long-term recommendations.

Quick Start

Audit the current test suite and return a prioritized health report.

Frequently Asked Questions about proof-audit

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

FAQPage Schema
How do I audit my test suite for flaky tests and coverage gaps?

To audit your test suite, analyze speed, reliability, coverage, and quality to flag flaky tests, slow tests, and coverage gaps. The process evaluates JS/TS or Python stacks to produce a structured health report with a score and prioritized remediation plan.

What is a test suite health score and how is it calculated?

A test suite health score is a diagnostic metric assessing overall test suite quality based on speed, reliability, coverage, and test assertions. It identifies skipped tests and anti-patterns, enabling proactive improvements through a structured health report.

Can I use this test audit on my Python and JS/TS test stacks?

Yes, you can apply this test audit to typical JS/TS or Python test stacks. It assesses test suite health by analyzing speed and reliability, flagging skipped tests, coverage gaps, and weak assertions specific to those environments.

What's the best way to prioritize fixing slow and flaky tests?

The best way to prioritize fixing slow and flaky tests is to generate a structured health report that surfaces critical issues and quick wins. This report categorizes findings by impact, enabling targeted remediation of weak assertions and anti-patterns.

Why does my test suite have weak assertions and how do I identify them?

Weak assertions occur when tests lack sufficient validation checks, often hiding coverage gaps and anti-patterns. You identify them by auditing test suite quality, which flags skipped tests and weak assertions to produce a prioritized remediation plan.