10 reviewed prompts.
Reviews code or a system design you own for security weaknesses, including web, API and AI-feature risks, with severity, impact, fixes and how to verify each fix. Use it before a release or a design sign-off.
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.
Reviews a code change against its requirements and lists concrete defects by severity, each with a trigger scenario, fix and test. Use before merging or releasing.
Reads a code diff and its commit message and produces a plain summary of what changed, why it matters, and what a reviewer should check. Use before opening a pull request or when reviewing someone else's change.
Reviews backend service code for layering, SOLID violations, API design and performance risks, and proposes small concrete refactors. Use it before merging a feature or when a codebase becomes hard to change.
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.
Reviews a Python snippet for missing docs, style, type hints and slow patterns, then returns an improved version with a change list. Use it before sharing or merging a script.
