shermanhuman/compound-v-verify
skills/compound-v-verify/SKILL.md
Mandatory checklist before claiming a task is done. Ensures verification, clean code, and accurate reporting. Use before saying "done" or "complete".
development
Updated Apr 19, 2026
$ install --global
skillsauthnpx skillsauth add shermanhuman/compound-v compound-v-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 19, 2026, 2:35 AM13.0s1 file scanned
SKILL.md
- name:
- compound-v-verify
- description:
- Mandatory checklist before claiming a task is done. Ensures verification, clean code, and accurate reporting. Use before saying "done" or "complete".
Verification Before Completion
Before reporting a task as done, run through this checklist.
When to use this skill
- before telling the user a task is complete
- before moving to the next plan step
- before writing a review or execution summary
The checklist
- Requirements — Re-read the task description. Confirm all requirements are met and no details or edge cases were missed.
- Tests — Run the full test suite, not just the tests you wrote. Confirm all pass.
- Code cleanliness — Remove commented-out code, debug prints, and placeholder TODOs.
- Warnings — Check for and resolve linter warnings, compiler warnings, and deprecation notices.
- Verification commands — Run the exact verification commands from the plan step. Confirm expected output.
- Documentation — Update relevant docs if you changed behavior, APIs, CLI flags, or configuration.
Statement of completion
When you announce completion, include:
- What you did (1-2 lines)
- How you verified it (exact commands + results)
Example: "Step 3 complete. Added auth middleware to lib/auth/plug.ex. Verified: mix test test/auth/ — 8 tests, 0 failures."
Never
- Say "done" without running verification commands
- Skip the checklist because "it's simple"
- Move to step N+1 if step N is not verified
Related Skills
shermanhuman/compound-v-tdd
development
VerifiedTrustedCommunity
Applies tests-first discipline (red/green/refactor) and adds regression tests for bugs. Use when implementing features, fixing bugs, or refactoring.
SKILL.mdUpdated Apr 19, 2026
shermanhuman/compound-v-review
testing
VerifiedTrustedCommunity
Reviews changes for correctness, edge cases, style, security, and maintainability with severity levels. 10 parallel checks with version-specific research. Use before finalizing changes.
SKILL.mdUpdated Apr 19, 2026
shermanhuman/compound-v-plan
research
VerifiedTrustedCommunity
Autonomous planning with internal reasoning. Researches, evaluates ideas, presents a plan. Minimizes user round-trips. Use before making non-trivial changes.
SKILL.mdUpdated Apr 19, 2026
shermanhuman/compound-v-persist
data-ai
VerifiedTrustedCommunity
Resolves target repository and storage location for conversation artifacts. Guarantees organized, time-sorted history.
SKILL.mdUpdated Apr 19, 2026