5 reviewed skills.
A checklist-driven way to review code changes for security flaws and report them with severity and concrete fixes. Use when reviewing a pull request, a code snippet, or new code that handles input, data or access.
Steers coding work toward the smallest correct change: reuse what exists, avoid new dependencies and speculative abstractions, never cut safety. Use when writing, reviewing or refactoring code where over-building is a risk.
Standing guidance for reviewing and rewriting version-control commit messages so history stays readable. Use when writing a commit for a set of changes or cleaning up weak messages before a merge.
Use when you have just written or changed code and before presenting it: runs a focused second pass for the mistakes generated code commonly contains, fixes what it can, and reports what was fixed and what needs the author's attention.
Standing approach for reviewing code: rank findings by impact, explain why, and suggest a fix. Use when asked to review code, a change or a pull request.
