n4m3z/VerifyCompletion
skills/VerifyCompletion/SKILL.md
Verify work before claiming done. USE WHEN about to claim work is complete, fixed, or passing, before committing or creating PRs.
$ install --global
skillsauthnpx skillsauth add n4m3z/forge-core VerifyCompletionInstall 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 14, 2026, 6:11 AM132.5s2 files scanned
SKILL.md
- name:
- VerifyCompletion
- version:
- 0.1.0
- description:
- Verify work before claiming done. USE WHEN about to claim work is complete, fixed, or passing, before committing or creating PRs.
VerifyCompletion
No completion claims without fresh verification evidence. Run the command, read the output, then claim the result.
The Gate Function
Before claiming any status or expressing satisfaction:
- Identify the command that proves the claim
- Run the full command now (not from memory, not from a previous run)
- Read the complete output, check exit code, count failures
- Match the output to your claim — does it confirm what you're about to say?
- Only then make the claim, citing the evidence
Skip any step and the claim is unverified.
Verification Requirements
| Claim | Requires | Not sufficient | | ----------------- | ---------------------------------------- | --------------------------------------- | | Tests pass | Test command output showing 0 failures | Previous run, "should pass" | | Linter clean | Linter output showing 0 errors | Partial check, extrapolation | | Build succeeds | Build command exit 0 | Linter passing, "logs look good" | | Bug fixed | Reproducing original symptom: now passes | Code changed, assumed fixed | | Requirements met | Line-by-line checklist against spec | Tests passing | | Agent completed | VCS diff shows expected changes | Agent reports "success" |
Red Flags
| Thought | Reality | | --------------------------------------- | ---------------------------------------------------- | | "Should work now" | Run the verification. | | "I'm confident" | Confidence is not evidence. | | "Just this once" | No exceptions. | | "Linter passed" | Linter is not the compiler. Run the build. | | "Agent said success" | Verify independently. Agents report intent, not fact.| | "Partial check is enough" | Partial proves nothing about the whole. | | "I already tested this earlier" | Earlier is not now. State changes between runs. | | "It's a small change, can't break" | Small changes break large systems. Verify. |
Constraints
- Never express satisfaction ("Done!", "Perfect!", "All good!") before running verification
- Never trust a previous run — re-run now
- Never trust agent success reports without checking the diff
- "Should", "probably", "seems to" are never verification
Sources
- https://github.com/obra/superpowers
Related Skills
n4m3z/Wtf
development
VerifiedTrustedCommunity
Reactive correction and root-cause fix. USE WHEN something went wrong, user is frustrated, demands a correction, says wtf, what the hell, why did you, that's wrong, this is broken, no not that, stop. Executes the immediate fix, then hunts the upstream artifact that caused it and creates a corrective change.
4SKILL.mdUpdated May 28, 2026
n4m3z/ResearchTopic
development
VerifiedTrustedCommunity
Decompose a research question into sub-queries, spawn parallel WebResearcher agents per angle, synthesize findings with citations and explicit confidence. USE WHEN the user asks to research, investigate, look online, look up, dig into, find sources, gather evidence, or survey what's known about a topic. Single-pass; for multi-round adversarial research use ResearchCouncil in forge-council.
4SKILL.mdUpdated May 27, 2026
n4m3z/WriteDocs
tools
VerifiedTrustedCommunity
Author project documentation that future humans (and AI sessions) actually read. Covers TLDRs for tools, READMEs, runbooks, journals. USE WHEN write documentation, create tldr, tool one-pager, document a cli, write readme, runbook, journal entry, capture knowledge about a tool, distill a session into reusable notes.
4SKILL.mdUpdated May 25, 2026
n4m3z/StagedReview
development
VerifiedTrustedCommunity
Review your own staged changes via a code-review TUI before triggering a commit. USE WHEN about to commit, walking through your own staged diff, self-reviewing before approval, tuicr, revdiff, git diff cached.
4SKILL.mdUpdated May 25, 2026