jimweller/verify-claims
configs/claude-code/skills/verify-claims/SKILL.md
Use when about to claim work is complete or passing, when receiving subagent results, or when writing a regression test for a bug fix
testing
Updated Apr 27, 2026
$ install --global
skillsauthnpx skillsauth add jimweller/dotfiles verify-claimsInstall 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 27, 2026, 1:06 PM57.0s1 file scanned
SKILL.md
- name:
- verify-claims
- description:
- Use when about to claim work is complete or passing, when receiving subagent results, or when writing a regression test for a bug fix
<!-- markdownlint-disable-file MD041 -->
STARTER_CHARACTER = 🧾
Verify Claims
Three procedures for proving claims with evidence. Each procedure runs before the claim is made, not after.
Verification Commands by Claim Type
Map the claim to the command that proves it. Run the command in this turn. Use the actual output, not memory of prior runs.
| Claim | Command | Insufficient | | --------------------- | ---------------------------------------------- | ------------------------------ | | Tests pass | Project test command, full suite or named test | Prior run, "should pass" | | Linter clean | Project linter command | Partial check, extrapolation | | Build succeeds | Project build command, exit 0 | Linter passing, logs look fine | | Bug fixed | Test that reproduces the original symptom | Code changed, "looks fixed" | | Regression test works | Red-green-revert-restore (see below) | Test passes once | | Subagent completed | VCS diff plus targeted re-check | Subagent self-report | | Requirements met | Re-read spec, line-by-line checklist | Tests passing |
Subagent Result Verification
Subagents report success in their final message. The report is not evidence. The diff is.
When a subagent returns:
- Read the subagent summary
- Run
git statusandgit diffto see what actually changed - If the subagent claimed tests pass, run the test command in the current turn
- If the subagent claimed a bug is fixed, run the reproduction case in the current turn
- Only then accept the result and move on
Subagents fabricate success reports under pressure. Treat the report as a hypothesis to verify, not a fact to accept.
Red-Green-Revert-Restore for Regression Tests
A test written after the fix passes immediately. Passing immediately proves nothing. To prove the test catches the bug:
- Write the regression test
- Run it with the fix in place. Expect: pass.
- Revert the fix only.
- Run the test. Must fail.
- Restore the fix.
- Run the test. Expect: pass.
If step 4 passes, the test does not exercise the bug. Throw it out and write a new one.
This procedure is unnecessary when test-driven-development order is followed (test first, then fix). It is the recovery procedure for the inverted order.
Related Skills
jimweller/transcript-search
testing
VerifiedTrustedCommunity
Search saved session transcripts for past decisions, actions, errors, and context that has left the current conversation window.
1SKILL.mdUpdated Apr 22, 2026
jimweller/prd-review
data-ai
VerifiedTrustedCommunity
Review a PRD for defects via Claude opus subagent.
SKILL.mdUpdated Apr 29, 2026
jimweller/md-syntax
development
VerifiedTrustedCommunity
Markdown authoring guidelines for formatting, code blocks, and structure. Use when writing or editing markdown files.
SKILL.mdUpdated Apr 29, 2026
jimweller/configs/claude-code/skills/md-style
development
VerifiedTrustedCommunity
--- name: md-style description: README style guide for concise, direct documentation. Use when writing or editing README files. ß--- <!-- markdownlint-disable-file MD041 --> # README Style Guide Write concise, direct README files for experienced engineers. ## Principles - **No fluff** - Skip tables of contents, verbose explanations, development history - **No roadmaps** - Document current state only, not plans or decisions. Readme is an engineering specification. Not a project plan or chan
SKILL.mdUpdated Apr 29, 2026