proof-recon

Inventory tests, frameworks, coverage, and CI to assess testing maturity.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Testing reconnaissance provides a structured approach to inventory and assess a project's tests, frameworks, coverage, and CI integration to support smooth handovers.

Core Features & Use Cases

  • Inventory test frameworks, languages, and CI configurations across a codebase.
  • Map tests and coverage to reveal gaps, dependencies, and risk areas for takeover.
  • Use Case: when taking over a legacy project with unknown test maturity, generate a clear testing maturity assessment and recommended improvements.

Quick Start

Run a full test inventory on the current project to generate a baseline testing maturity report.

Frequently Asked Questions about proof-recon

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

FAQPage Schema
How do I inventory test frameworks and CI configurations across a codebase?▼

To inventory test frameworks and CI configurations, run a full testing reconnaissance scan to detect languages, test frameworks, and pipeline configs, producing a comprehensive testing maturity snapshot.

What is testing maturity assessment for a legacy project takeover?▼

Testing maturity assessment is a structured evaluation of test frameworks, coverage, and CI integration that reveals gaps and risk areas in critical paths to support smooth project handovers.

Can I assess test coverage and identify gaps in critical paths across different languages?▼

Yes, you can assess test coverage across different languages by mapping tests and coverage reports to reveal dependencies, risk areas, and gaps in critical paths for a project takeover.

How do I map tests to coverage reports to reveal risk areas before a handover?▼

Map tests to coverage reports by applying reconnaissance across test files and pipelines, generating a structured maturity assessment with actionable recommendations to identify risk areas.

What's the best way to generate a baseline testing maturity report for an unfamiliar codebase?▼

The best way to generate a baseline testing maturity report is running a full test inventory on the current project, detecting CI configs and frameworks to produce actionable improvement recommendations.