popoffvg/test-set-verify
harness/plugins/work-manager/common/skills/test-set-verify/SKILL.md
Use when the user asks to review, audit, score, or validate test sets for missed cases before execution or merge.
$ install --global
skillsauthnpx skillsauth add popoffvg/dotfiles test-set-verifyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 20, 2026, 4:43 AM139.4s1 file scanned
SKILL.md
- name:
- test-set-verify
- description:
- Use when the user asks to review, audit, score, or validate test sets for missed cases before execution or merge.
Test Set Verify
Audit an existing test set for completeness, correctness, and missed-case risk.
Verification outputs
Return exactly:
- Coverage score (0-100)
- Critical gaps (must-fix)
- Non-critical gaps (should-fix)
- False/weak assertions
- Traceability defects (requirements without tests or tests without requirements)
- Patch plan (minimal edits to close gaps)
Scoring rubric
- Requirement coverage: 30
- Negative + boundary depth: 20
- Resilience/failure-mode depth: 20
- Assertion quality (observable outcomes): 15
- Environment/preflight realism: 10
- Determinism/flakiness controls: 5
Fail gate: any P0 path or safety condition missing => Not Ready regardless of numeric score.
Must-check invariants
- No requirement is untested.
- No scenario without explicit oracle.
- No single-point happy-path-only coverage.
- No hidden dependency assumptions.
- No retry loops without termination criteria.
- No vague assertions like "works" / "succeeds".
Session-derived missed-case checks
Based on Pi/Claude session patterns, always verify:
- Tooling preconditions captured
- Is there a check for lint/auth/assets/config readiness before test execution?
- Stale-state protection present
- Do scenarios include read/refresh checkpoints after state-changing actions?
- Transient permission/tool failure handling
- Are there scenarios for temporary transport/permission interruptions with bounded retry or fallback?
- Subsystem-specific failure observability
- Do expected results identify exact failing subsystem, not generic failure text?
- Duplicate-fix regression lock
- Is there a deterministic regression case for previously repeated or reintroduced defects?
Verification algorithm
- Parse requirements and scenario IDs.
- Build requirement↔scenario matrix.
- Run gap scan by category (happy/neg/boundary/resilience/regression).
- Evaluate oracle quality per scenario.
- Run session-derived missed-case checks.
- Compute score + Not Ready/Ready verdict.
- Produce minimal patch list with concrete scenario IDs to add/update.
Verdict format
- Verdict: Ready | Not Ready
- Score: NN/100
- Must-fix now: [IDs]
- Should-fix next: [IDs]
- Minimal patch set: bullet list with exact scenario IDs
Related Skills
popoffvg/test-set-write
testing
VerifiedTrustedCommunity
Use when the user asks to create test sets, enumerate scenarios, generate edge cases, or draft a coverage matrix before implementation.
2SKILL.mdUpdated Jun 2, 2026
popoffvg/test-harness-plugin
tools
VerifiedTrustedCommunity
Test harness plugins in isolation using tmux panes. Runs MCP servers, unit tests, typecheck, and Claude plugin loading. Use when user says "test plugin", "check plugin", "run plugin tests", "validate plugin", or names a specific plugin to test.
2SKILL.mdUpdated Jun 2, 2026
popoffvg/test-bdd
development
VerifiedTrustedCommunity
Guide for designing integration and e2e tests using BDD (Behavior-Driven Development) methodology with Cucumber-style Given/When/Then scenarios. Use when writing or reviewing tests for any service, API, or component. Language-agnostic — covers scenario structure, step notation, assertion principles, async patterns, and common anti-patterns.
2SKILL.mdUpdated Jun 2, 2026
popoffvg/test-bdd-tdd
development
VerifiedTrustedCommunity
Applies behavior-driven development principles including Gherkin scenarios and test-driven development. This skill should be used when the user asks to implement features, fix bugs, or when writing executable specifications and tests before writing production code.
2SKILL.mdUpdated Jun 2, 2026