Code Reviewer

A thorough second set of eyes on code — it reviews TypeScript, JavaScript, Python, Swift, Kotlin, and Go for bugs, quality issues, and security problems, and produces a clear checklist. Perfect for safely vetting AI-written code before it goes live.

Cowork & Chat

How to use it

Give it the code or a diff and it walks through best practices, runs a security scan, and hands back specific, prioritized feedback. Works in Cowork/Chat — it reads the code you provide; it doesn’t need to run your project. Use it as the “is this safe to ship?” gate on vibe-coded changes.

How to invoke / keep it on

Paste code or point it at a file and ask for a review — Claude auto-loads it. For repeat use, add “always code-review changes” to a Project’s instructions.

20 powerful examples for Melinda Maria

Copy, tweak, make them yours. Just describe the task — Claude loads the skill automatically.

01"Review this new tool Claude wrote for our canto-mcp connector before I deploy — flag bugs, security issues, and anything that could leak data, as a checklist."

02"Here’s a Python script that renames and sorts our ApparelMagic exports — review it for edge cases and safety before I run it on real files."

03"Do a security-focused review of the auth code in a connector and tell me, in plain English, what each risk means and how to fix it."

04"Compare the old and new version of this Worker handler and tell me what changed and whether the change is safe."

05"Review the JavaScript behind the onboarding hub’s Metric Mixer and flag anything fragile before I ship it."

06"Vet this script that bulk-updates Shopify product tags — tell me what could go wrong on real data and how to make it safer."

07"Review a new gorgias write tool and confirm the confirm-gate can’t be bypassed."

08"Check this Python that calls QuickBooks for any place it mishandles money values or rounding."

09"Give me a prioritized review (critical → minor) of this connector diff so I know what to fix first."

10"Review error handling in this code and tell me where a failure would crash silently versus surface clearly."

11"Look at this regex-based string replacement (the kind that once mangled our connector cards) and tell me if it’s safe or fragile."

12"Review this code for hard-coded secrets or tokens and flag anything that should be an environment variable."

13"Check whether this function handles empty or missing API responses (like Meta Ads returning nothing) gracefully."

14"Review the input validation on a tool that takes a date range and tell me what bad input could break it."

15"Do a readability + maintainability pass so a non-coder could follow this connector code later."

16"Review this Box/Drive file-handling script for path-traversal or accidental overwrite risks."

17"Tell me if this code has any race conditions when two requests hit the connector at once."

18"Review a TypeScript MCP tool’s types and confirm the input schema matches what the code actually expects."

19"Give me a go/no-go on shipping this change, with the reasons stated plainly for the team."

20"Review this script before I run it on production data and give me a short “safe to run?” verdict with caveats."

← Back to Engineering & Prompt-craft