proof-recon

Included with Lifetime

$97 forever

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".

Cloud & DevOps

What this skill does


# 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.

Files: 2

Size: 3.9 KB

Complexity: 14/100

Category: Cloud & DevOps

Source: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/tree/main/plugins/ai-agency/tonone/skills/proof-recon

Related in Cloud & DevOps

appbuilder-action-scaffolder

Included

Create, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.

Cloud & DevOpsscripts

orchestrating-datacloud

Included

Salesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).

Cloud & DevOpsscripts

github-project-automation

Included

Automate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error

Cloud & DevOpsscripts

sf-datacloud

Included

Salesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).

Cloud & DevOpsscripts

fabric-cli

Included

Use this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.

Cloud & DevOpsscripts

lark

Included

Lark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.

Cloud & DevOpsscripts