# Verify Testing Coverage Before Review

Teams often miss tests for critical paths during fast reviews. This skill guides Claude, Codex, and Claude Code through focused testing checks.

## Install

```bash
npx skillstore add danielpodolsky/testing-gate
```

## Metadata

- Status: approved
- Slug: danielpodolsky-testing-gate
- Skillstore revision: r1
- Version status: missing
- Tree hash: 7620c5b4e2ee222f7d4d7d99405a9e056c756261b4489bdb7777b6b97fd865e8
- Author: DanielPodolsky
- GitHub username: DanielPodolsky
- License: MIT
- Repository: https://github.com/DanielPodolsky/mentor-spec/tree/main/.claude/skills/gates/testing
- Ref: 34f316ba14ef36c7a620fc09f2676d2429997a77
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/danielpodolsky-testing-gate
- Manifest: https://skillstore.pages.dev/api/skills/danielpodolsky-testing-gate/manifest

## Capabilities

- Asks structured questions about test existence, coverage strategy, and test quality.
- Classifies outcomes as pass or warning based on the provided testing evidence.
- Provides response templates for passing tests, missing tests, and weak tests.
- Explains what a strong test suite should cover across feature complexity levels.
- Offers stack-specific testing hints for React, Next.js, backend APIs, and Python.
- Connects testing work to interview and portfolio discussion points.

## Use Cases

- Mentor Junior Developers: Guide learners to explain what their tests prove before moving to code review.
- Review Feature Readiness: Check whether a feature has meaningful tests for happy paths, edge cases, and errors.
- Prepare Portfolio Projects: Help developers identify testing work they can discuss in interviews and project writeups.

## Prompt Templates

### Basic Test Check

```
Use the testing gate for this feature. Ask what tests exist, what they prove, and whether any critical path is missing.
```

### Improve Weak Tests

```
Review these tests with the testing gate. Identify the weakest coverage area and suggest one practical improvement without blocking progress.
```

### Stack-Specific Guidance

```
Apply the testing gate to this project stack. Recommend suitable test types and one next test for the most important behavior.
```

### Interview-Ready Assessment

```
Use the testing gate to assess whether this feature has interview-ready testing evidence. Summarize strengths, gaps, and a concise interview talking point.
```

## Limitations

- Does not run test suites or collect coverage metrics automatically.
- Depends on the learner or agent to provide accurate project context.
- Uses warnings instead of hard blocking, so weak coverage can still proceed.
- Focuses on testing habits and review discussion, not full quality assurance.

## Best Practices

- Ask for the most important test before judging overall coverage.
- Tie feedback to observable behavior, not implementation details.
- Suggest one realistic next test when coverage is missing or weak.

## Anti Patterns

- Treating missing tests as a hard blocker when the gate defines warnings.
- Accepting placeholder tests that do not verify real behavior.
- Focusing only on coverage percentage without discussing critical paths.

## Security Audit

- Audited at: 2026-07-06T09:58:41.409\+00:00
- Summary: All ten static findings are false positives caused by Markdown formatting, response templates, and ordinary testing guidance. No evidence found of prompt injection, data exfiltration, network access, or instructions to execute commands.

## Stats

- Views: 285
- Downloads: 14
- Favorites: 0
- Popularity score: 0