paulund/dev-review
dev-review/SKILL.md
Run a comprehensive code review on the current PR or codebase. Use when a PR is ready for review, after implementation, or when the user asks for a review. Trigger phrases - "/review", "review this".
$ install --global
skillsauthnpx skillsauth add paulund/ai dev-reviewInstall 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 5, 2026, 6:42 AM173.0s1 file scanned
SKILL.md
- name:
- dev-review
- description:
- Run a comprehensive code review on the current PR or codebase. Use when a PR is ready for review, after implementation, or when the user asks for a review. Trigger phrases - "/review", "review this".
- category:
- dev
You are an expert code reviewer. Follow these steps:
- If no PR number is provided in the args, run
gh pr listto show open PRs - If a PR number is provided, run
gh pr view <number>to get PR details - Run
gh pr diff <number>to get the diff - Analyze the changes and provide a thorough code review that includes:
- Overview of what the PR does
- Analysis of code quality and style
- Specific suggestions for improvements
- Any potential issues or risks
Keep your review concise but thorough. Focus on:
- Code correctness
- Following project conventions
- Performance implications
- Test coverage
- Security considerations
Format your review with clear sections and bullet points. PR number: ${H}
Related Skills
paulund/test-driven-development
development
VerifiedTrustedCommunity
Use when implementing any logic, fixing any bug, or changing any behaviour. Use when you need to prove code works, when a bug report arrives, or when modifying existing functionality. Do NOT use for config changes, data migrations, or dependency updates.
3SKILL.mdUpdated Jul 1, 2026
paulund/spec-driven-development
development
VerifiedTrustedCommunity
Use when starting a new feature, when requirements are unclear, when asked to write code without a clear spec, or before any non-trivial implementation. Do NOT use for trivial bug fixes or one-line changes.
3SKILL.mdUpdated Jul 1, 2026
paulund/source-driven-development
development
VerifiedTrustedCommunity
Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters. Detects the stack from dependency files, fetches official documentation, implements following documented patterns, and cites sources for every framework-specific decision.
3SKILL.mdUpdated Jul 1, 2026
paulund/shipping-and-launch
development
VerifiedTrustedCommunity
Use when preparing to ship a feature, release, or deployment. Use before merging to main, creating a release, or deploying to production. Do NOT use for CI-only changes or internal refactors that don't reach production.
3SKILL.mdUpdated Jul 1, 2026