About

Imported from tonone-ai/tonone (skills/proof-recon/SKILL.md). Install upstream with npx skills add tonone-ai/tonone --skill proof-recon. Copyright stays with the author (MIT).

Testing Reconnaissance

Name: proof-recon
Author: tonone-ai

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.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml

targets:
  - https://api.opensmartroute.ai/api/v1/registry/tonone-ai-tonone-proof-recon/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

tonone-ai-tonone-proof-recon.ocm.jsonjson

{
  "ocm": "1",
  "id": "tonone-ai-tonone-proof-recon",
  "kind": "skill",
  "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\".",
  "publisher": "tonone-ai",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "coding"
    ],
    "tags": [
      "skill-md",
      "engineering",
      "qa",
      "testing",
      "recon",
      "github"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "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\"."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github",
      "repository": "https://github.com/tonone-ai/tonone",
      "path": "skills/proof-recon/SKILL.md",
      "ref": "64caa639d941227719d912936fedede546983cee",
      "url": "https://github.com/tonone-ai/tonone/blob/64caa639d941227719d912936fedede546983cee/skills/proof-recon/SKILL.md",
      "key": "tonone-ai/tonone/skills/proof-recon/SKILL.md"
    },
    "compatibility": "Designed for Claude Code",
    "allowed_tools": [
      "Read,",
      "Bash,",
      "Glob,",
      "Grep,",
      "WebFetch,",
      "WebSearch,",
      "AskUserQuestion"
    ],
    "license": "MIT"
  },
  "instructions": "# Testing Reconnaissance\n\nYou are Proof — the QA and testing engineer on the Engineering Team.\n\nFollow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.\n\n## Steps\n\n### Step 0: Detect Environment\n\nIdentify the full stack:\n\n- Check for languages and frameworks: `package.json`, `pyproject.toml`, `go.mod`, `Cargo.toml`\n- Check for test frameworks: Jest, Vitest, pytest, Go testing, RSpec, JUnit\n- Check for E2E tools: Playwright, Cypress, Selenium\n- Check for CI: `.github/workflows/`, test scripts, CI configs\n\n### ",
  "cost": {
    "context_tokens": 762
  }
}

Fetch it by URL: GET /api/v1/registry/tonone-ai-tonone-proof-recon/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.