cwoodruff/reflection-contract-tests
.squad/skills/reflection-contract-tests/SKILL.md
Use reflection-based tests to lock an API contract before the implementation lands.
$ install --global
skillsauthnpx skillsauth add cwoodruff/morespeakers-com reflection-contract-testsInstall 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 24, 2026, 8:59 PM2.4s1 file scanned
SKILL.md
- name:
- reflection-contract-tests
- description:
- Use reflection-based tests to lock an API contract before the implementation lands.
- domain:
- testing
- confidence:
- high
- source:
- earned
Context
Use this when a team wants tests merged ahead of an additive implementation. The goal is to keep the test project compiling while still failing loudly if required public types or members are missing.
Patterns
- Load the target assembly from an existing known type instead of referencing the new contract directly.
- Assert on public type names, namespace, shape, factory methods, operators, and property values through reflection.
- Fail with explicit messages that name the missing type or member so the implementer gets a clean failure story.
Examples
src/MoreSpeakers.Domain.Tests\ResultFoundationTests.csvalidates the futureMoreSpeakers.Domain.Result,MoreSpeakers.Domain.Result<T>, andMoreSpeakers.Domain.Errorcontract before those types exist.
Anti-Patterns
- Do not use reflection when the implementation already exists and compile-time assertions are simpler.
- Do not make reflection tests so vague that multiple incompatible APIs would pass.
Related Skills
cwoodruff/windows-compatibility
tools
VerifiedTrustedCommunity
Cross-platform path handling and command patterns
6SKILL.mdUpdated Apr 17, 2026
cwoodruff/test-discipline
development
VerifiedTrustedCommunity
Update tests when changing APIs — no exceptions
6SKILL.mdUpdated Apr 17, 2026
cwoodruff/squad-conventions
development
VerifiedTrustedCommunity
Core conventions and patterns used in the Squad codebase
6SKILL.mdUpdated Apr 17, 2026
cwoodruff/session-recovery
tools
VerifiedTrustedCommunity
Find and resume interrupted Copilot CLI sessions using session_store queries
6SKILL.mdUpdated Apr 17, 2026