the-own-lab/test-verify
skills/test-verify/SKILL.md
Run and analyze test results against acceptance criteria. Use when verifying implementation completeness.
testing
Updated Apr 21, 2026
$ install --global
skillsauthnpx skillsauth add the-own-lab/Claude-company-of-one test-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: Apr 16, 2026, 10:05 PM13.9s1 file scanned
SKILL.md
- name:
- test-verify
- description:
- Run and analyze test results against acceptance criteria. Use when verifying implementation completeness.
Test Verify
Run tests and verify implementation against acceptance criteria.
Process
-
Read acceptance criteria from
REQUIREMENTS.md— Know exactly what must be true before running anything. -
Run full test suite — Execute all tests, not just the new ones. Catch regressions.
-
Map test results to acceptance criteria — For each acceptance criterion, identify which test(s) verify it. Flag any criterion without a corresponding test.
-
Test edge cases not covered by existing tests — Use the edge case checklist below to identify gaps and write additional tests.
-
Produce structured report — Use the report format below.
Edge Case Checklist
- [ ] Empty/null inputs
- [ ] Boundary values (zero, one, max, min, off-by-one)
- [ ] Error paths (invalid input, network failure, timeout)
- [ ] Concurrency (race conditions, duplicate submissions)
- [ ] Performance (large inputs, many records)
- [ ] Security (injection, unauthorized access, malformed input)
Report Format
Summary
One paragraph: what was tested, how many tests ran, how many passed/failed.
Criteria Verification Table
| # | Acceptance Criterion | Test(s) | Result |
| --- | ------------------------ | ---------------- | ----------- |
| 1 | Description of criterion | test_name_here | PASS / FAIL |
Edge Cases
List of edge cases tested and their results.
Issues Found
Any bugs, regressions, or concerns discovered during verification.
Verdict
PASS — All acceptance criteria verified, no critical issues. FAIL — List which criteria failed and why.
Related Skills
the-own-lab/write-brief
documentation
VerifiedTrustedCommunity
Update BRIEF.md sections during a command run. Any skill that produces a brief-persisted artifact calls this to write it back.
SKILL.mdUpdated Apr 22, 2026
the-own-lab/verify
development
VerifiedTrustedCommunity
Post-code check: run tests + confirm TODO acceptance items map to passing tests; applies a security lens but is not a separate scan.
SKILL.mdUpdated Apr 22, 2026
the-own-lab/update-docs
documentation
VerifiedTrustedCommunity
Command post-step: write CHANGELOG + TODO once per command run. One call, not per-skill doc writes.
SKILL.mdUpdated Apr 22, 2026
the-own-lab/spec-writing
content-media
VerifiedTrustedCommunity
Author REQUIREMENTS.md + DESIGN.md + TODO.md for a feature. The three files are one contract; they ship together.
SKILL.mdUpdated Apr 22, 2026