Dev & Code
Free
v1.0
Senior Dev Code Review
Get a thorough senior-level code review: bugs, security issues, performance, readability, and refactoring suggestions.
code review
quality
refactoring
security
When to use
Run this on any piece of code before merging a PR, shipping to production, or presenting to a client.
Recommended LLMs
Claude Sonnet
GPT-4o
Gemini 1.5 Pro
Plugins / Skills
Projects (Claude)
When to use
Use before any code goes to production. This is especially useful when you don't have a senior dev to review your code, when you're working solo, or when you want a second opinion fast.
Tips for best results
- Include the full context: what the code does, what tech stack it runs on, and any known constraints
- For large files, paste one function or module at a time
- Tell it what you're most worried about (e.g., "mainly check for security issues")
- After the review, ask: "Show me the refactored version of the most critical issue"
Expected output
A structured review with severity labels [CRITICAL / HIGH / MEDIUM / LOW] for each issue, specific line-level suggestions, and example refactored code where relevant.
The Prompt
Copy it, paste it, use it.
You are a senior software engineer with 10+ years of experience doing production code reviews. Review the following code as if you're doing a thorough pull request review before it ships to production.
[CODE]:
```
{paste your code here}
```
[CONTEXT]: {describe what this code does and the tech stack it runs on}
Review it for:
1. **Bugs & Logic Errors** — anything that will break in edge cases or production
2. **Security Issues** — injection risks, exposed secrets, improper auth, missing input validation
3. **Performance** — N+1 queries, unnecessary re-renders, memory leaks, inefficient algorithms
4. **Readability** — naming, function size, complexity, unclear logic
5. **Best Practices** — idiomatic patterns for this tech stack, conventions, error handling
6. **Suggested Refactors** — show the improved code, don't just describe it
Format: Use severity labels [CRITICAL / HIGH / MEDIUM / LOW] for each issue. Be direct and specific. Don't praise what's fine — only flag issues and improvements. If code is clean in an area, skip that section entirely.