zaxbysauce/reviewing-doc-drift
.claude/skills/reviewing-doc-drift/SKILL.md
Verify that README changes, release notes, changelog bullets, migration notes, PR descriptions, examples, and docstrings match what the code actually ships.
development
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add zaxbysauce/ragappv3 reviewing-doc-driftInstall 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 16, 2026, 12:45 PM36.5s1 file scanned
SKILL.md
- name:
- reviewing-doc-drift
- description:
- Verify that README changes, release notes, changelog bullets, migration notes, PR descriptions, examples, and docstrings match what the code actually ships.
Reviewing Docs and Release Drift
Goal
Detect claimed features that are not actually shipped, and shipped behavior that is not documented.
Workflow
- Extract atomic claims from README/docs, release notes, changelog, PR text, examples, comments, docstrings, and migration notes.
- For each claim, locate structural proof in code, tests, config, routes, exports, handlers, migrations, or user-visible wiring.
- Classify each claim:
- SUPPORTED
- PARTIALLY_SUPPORTED
- UNSUPPORTED
- CONTRADICTED
- STEALTH_CHANGE
- Emit defects only for unsupported, contradicted, or material stealth changes.
Required checks
- feature claims map to actual handlers, exports, routes, commands, or user-facing paths
- resilience claims map to retries, backoff, fallback, or recovery logic
- caching claims map to cache read, write, and invalidation behavior
- security claims map to enforced checks where the privileged action executes
- compatibility claims map to actual platform-safe behavior
- breaking changes have migration notes or equivalent guidance
- release/changelog scope matches actual changed behavior
- examples would work if followed literally
Related Skills
zaxbysauce/unswarm
development
VerifiedTrustedCommunity
Disable swarm mode for the current Claude Code session and return to normal behavior.
SKILL.mdUpdated Apr 16, 2026
zaxbysauce/swarm
development
VerifiedTrustedCommunity
Enable a high-quality swarm-like Claude Code workflow for the current session, and optionally execute a task immediately using that mode. Uses parallel subagents for breadth, independent reviewer validation for precision, and critic challenge for final confidence. Use when the user wants swarm-like behavior, higher review rigor, or maximum quality without sacrificing Claude Code speed.
SKILL.mdUpdated Apr 16, 2026
zaxbysauce/swarm-pr-review
tools
VerifiedTrustedCommunity
Run a swarm-like PR review using parallel exploration, independent reviewer validation, and critic challenge. Use for deep pull request review with low false-positive tolerance.
SKILL.mdUpdated Apr 16, 2026
zaxbysauce/.claude/skills/swarm-implement
development
VerifiedTrustedCommunity
--- name: swarm-implement description: Execute complex implementation work with a swarm-like Claude Code workflow: parallel exploration, scoped planning, selective deep validation, and independent reviewer/critic checks where risk justifies them. Use for feature work, bug fixes, refactors, and multi-file changes. disable-model-invocation: true --- # /swarm-implement Use this skill for implementation work when you want Claude Code to behave like a fast, high-quality swarm rather than a single-t
SKILL.mdUpdated Apr 16, 2026