hellblazer/test-validation
nx/skills/test-validation/SKILL.md
Use when implementation is complete and test coverage needs verification, before merge or pull request
$ install --global
skillsauthnpx skillsauth add hellblazer/nexus test-validationInstall 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 20, 2026, 2:11 PM81.5s1 file scanned
SKILL.md
- name:
- test-validation
- description:
- Use when implementation is complete and test coverage needs verification, before merge or pull request
- effort:
- high
Test Validation Skill
Delegates to the test-validator agent. See registry.yaml for details.
When This Skill Activates
- After completing feature implementation
- After fixing a bug
- Before marking work as complete
- Before creating pull request
- Before merge to main branch
- When verifying test coverage for changed code
- When test quality assessment is needed
Agent Invocation
Use the Agent tool to invoke test-validator:
## Relay: test-validator
**Task**: [what needs to be done]
**Bead**: [ID] or 'none'
### Input Artifacts
- Files: [relevant files]
### Deliverable
Test coverage report with gap analysis
### Quality Criteria
- [ ] All changed files have corresponding tests
- [ ] Test coverage meets project standards
- [ ] Edge cases covered
For full relay structure and optional fields, see RELAY_TEMPLATE.md.
Validation Methodology
The agent will:
- Identify all changed/added production code
- Map existing tests to the changes
- Run relevant test suites
- Analyze coverage gaps
- Check test quality (assertions, edge cases, error paths)
- Recommend additional tests if needed
REQUIRED: Run all tests and verify output before claiming coverage is adequate.
Agent-Specific PRODUCE
- Session Scratch (T1): scratch tool: action="put", content="<snapshot>", tags="test-run" — test run snapshots and interim findings during session
- nx memory: memory_put tool: content="...", project="{project}", title="test-validation-{date}.md" — quality metrics and coverage findings persisted across sessions
Bead Integration
After validation:
- Tests pass + coverage adequate:
/beads:close <id>with success note - Tests fail: Keep in_progress, may trigger debugging
- Coverage gaps: Create new bead for missing tests
Success Criteria
- [ ] All changed files have corresponding tests
- [ ] Test coverage meets project standards
- [ ] All tests pass
- [ ] Edge cases covered
- [ ] No obvious test gaps remain
- [ ] Bead status updated appropriately
- [ ] T2 memory updated with session findings (if multi-session work)
Session Scratch (T1): Agent uses scratch tool for ephemeral working notes during the session. Flagged items auto-promote to T2 at session end.
Related Skills
hellblazer/review
development
VerifiedTrustedCommunity
Use when critiquing / auditing / reviewing a change set against decision history — tries the review plan library first (catalog lookup → decision-evolution traversal → extract → compare), falls through to /nx:query if nothing matches
1SKILL.mdUpdated Apr 17, 2026
hellblazer/research
documentation
VerifiedTrustedCommunity
Use when doing design / architecture / planning work that walks from prose (RDRs, docs, knowledge) into the modules implementing a concept
1SKILL.mdUpdated Apr 17, 2026
hellblazer/plan-promote
development
VerifiedTrustedCommunity
Use when surveying the plan library's runtime metrics to propose plans for promotion to a higher scope — advisory-only; dispatches the plan-promote-propose meta-seed (no lifecycle ops — those ship in RDR-079)
1SKILL.mdUpdated Apr 17, 2026
hellblazer/plan-inspect
business
VerifiedTrustedCommunity
Use when inspecting plan runtime metrics or enumerating dimension-registry usage — dispatches plan_match with dimensions={verb:plan-inspect}; strategy:default reports per-plan metrics, strategy:dimensions reports registry usage counts
1SKILL.mdUpdated Apr 17, 2026