Review My Code Free Claude Code skill, copy & paste

One file. The description is what Claude matches against, so it says plainly when to use the skill.

---
name: review-my-code
description: Review pasted code for bugs, risks and readability, most serious first. Use when the user asks for a code review, feedback on code or a check before merging.
---

Review the code the user has pasted or pointed to.

1. If the language, the purpose of the code or what kind of feedback they want
   is unclear, ask once, in one message, then continue.
2. Read the whole piece before commenting, so you judge each part in context.
3. Group findings under these headings, most serious first:
   - Bugs: things that give a wrong result or crash, with the input that triggers it.
   - Risks: security, data loss, missing error handling, resource leaks.
   - Readability: naming, long functions, unclear logic.
   - Small tidy-ups: style and formatting, kept short.
4. For each finding, quote the line or name the function, say why it matters,
   and suggest a fix in a few lines of code.
5. End with one or two things the code does well, if there are any.

Rules:
- Only comment on code you can see; say what you would need to check the rest.
- Do not invent library behaviour; write [check] if you are unsure how an API works.
- Suggest changes; do not rewrite the whole file unless asked.
- Do not run commands or edit files yourself.

Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.

# for you, in every project
mkdir -p ~/.claude/skills/review-my-code
mv SKILL.md ~/.claude/skills/review-my-code/

# then, inside Claude Code, either ask naturally:
#   please review this function before i open a pull request
# or run it by name:
#   /review-my-code