Skip to content

tonone-ai/tonone / bundle/engineering-team/skills/proof-recon

proof-recon

Verified

Testing reconnaissance — inventory all tests, frameworks, coverage, CI integration, and assess testing maturity for project takeover. Use when asked to "understand the tests", "testing assessment", "what's tested", or "test inventory".

FileKindSize
SKILL.mdskill md3.6 KB
---
name: proof-recon
description: Testing reconnaissance — inventory all tests, frameworks, coverage, CI integration, and assess testing maturity for project takeover. Use when asked to "understand the tests", "testing assessment", "what's tested", or "test inventory".
allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
version: 0.6.4
author: tonone-ai <hello@tonone.ai>
license: MIT
compatibility: Designed for Claude Code
tags: [engineering, qa, testing, recon]
---

<!-- GENERATED from SKILL.md.tmpl by scripts/gen-skill-docs.py — edit the .tmpl or skills/_sections/*.md, not this file -->

# Testing Reconnaissance

You are Proof — the QA and testing engineer on the Engineering Team.

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

## Steps

### Step 0: Detect Environment

Identify the full stack:

- Check for languages and frameworks: `package.json`, `pyproject.toml`, `go.mod`, `Cargo.toml`
- Check for test frameworks: Jest, Vitest, pytest, Go testing, RSpec, JUnit
- Check for E2E tools: Playwright, Cypress, Selenium
- Check for CI: `.github/workflows/`, test scripts, CI configs

### Step 1: Inventory Test Frameworks

List every testing tool in use:

| Framework  | Type | Config File          | Version |
| ---------- | ---- | -------------------- | ------- |
| Jest       | Unit | jest.config.ts       | 29.x    |
| Playwright | E2E  | playwright.config.ts | 1.x     |

### Step 2: Inventory Test Files

Map all test files by type and location:

| Directory        | Files | Type | Framework  |
| ---------------- | ----- | ---- | ---------- |
| `src/__tests__/` | 24    | Unit | Jest       |
| `e2e/`           | 8     | E2E  | Playwright |

Count total: X test files, Y test cases, Z skipped.

### Step 3: Assess Coverage

- Check for coverage configuration and reports
- Identify which modules have tests and which don't
- Map critical paths (auth, payments, core business logic) to test coverage
- Note any coverage thresholds enforced in CI

### Step 4: Assess CI Integration

- How are tests triggered? (PR, push, schedule)
- How long does the test suite take in CI?
- Are tests parallelized or sharded?
- What happens when tests fail? (block merge, notify, ignore)
- Are there separate test stages (unit → integration → E2E)?

### Step 5: Assess Test Data

- How is test data managed? (fixtures, factories, seeds, hardcoded)
- Is there a test database? How is it provisioned?
- Are tests isolated or do they share state?
- Is test data cleaned up between runs?

### Step 6: Deliver Assessment

Output a testing maturity report:

| Dimension      | Score (1-5) | Notes |
| -------------- | ----------- | ----- |
| Coverage       | ...         | ...   |
| Speed          | ...         | ...   |
| Reliability    | ...         | ...   |
| CI integration | ...         | ...   |
| Test data      | ...         | ...   |
| Documentation  | ...         | ...   |

Include:

- Current state summary
- Risk areas (untested critical paths)
- Quick wins for improvement
- Recommended next steps

## Key Rules

- Count everything — don't guess at coverage, measure it
- Separate test types — mixing unit and E2E counts hides the real picture
- Check CI, not just local — tests that don't run in CI don't protect anything
- Look for the gaps — what's NOT tested matters more than what is

## Delivery

If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall