plugins/dp-cto/skills/adhoc-review/SKILL.md
Use when you want a code review on recent changes, a specific file, or a pull request — 'review this', 'check my code', 'what did I miss'. Works in any project without setup.
npx skillsauth add raisedadead/dotplugins adhoc-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Standalone code review task. No tracker state, no task_id, no stage context. Works in any project.
Review the scope passed as arguments. If no scope provided, determine it:
git diff --name-only HEAD~1 has changes → review that diffIf args include a lens keyword (security, simplification, test-gaps, linting, performance, docs, sweep, pushback), apply that lens. Otherwise default to Quick — pick the single most-relevant lens for the diff.
| Lens | Focus | | -------------- | ------------------------------------------------- | | security | injection, authz, secrets, SSRF, OWASP top 10 | | simplification | dead code, over-engineering, needless abstraction | | test-gaps | missing coverage, untested branches | | linting | style, naming, dead imports | | performance | N+1, hot loops, allocation | | docs | stale comments, missing context | | sweep | entropy drift across conventions | | pushback | adversarial challenge of proposals |
Present findings grouped by severity:
Every finding includes file:line + evidence + suggested fix. Deduplicate by file:line (keep higher severity).
development
Use when the user shares a URL, names a resource from SOURCES.md, shares operational feedback, says 'adopt', 'learn from', 'what can we steal from', 'compare with', 'self-develop', or 'how do we get better'.
tools
Use when you need to set up or rebuild the dp-lsp Docker image after installing the plugin — 'set up LSP', 'build the image', 'install language servers'.
development
Use when you want to write tests first, enforce test-driven development, or add test coverage — 'write tests for this', 'TDD this feature', 'add test coverage'. Strict RED-GREEN-REFACTOR discipline.
testing
Use when starting major work that needs formal design review — cross-team changes, architectural decisions, or complex features where requirements need discovery before implementation.