Code review
Review a code snippet for bugs, security issues, and style, with concrete fixes. Use when the user shares code and asks for feedback or a review.From its SKILL.md
npx -y skills add TeamDzX/myllm-skills --skill code-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
0.8 KB, 146 tokens by cl100k_base, as published. Nobody here has run it
Code review
Review the provided code. Structure the response as:
Bugs & correctness
- Each issue with a one-line explanation and a suggested fix.
Security
- Injection, secrets in source, unsafe input handling, etc. (or "none found").
Style & clarity
- Naming, structure, dead code — only changes that actually matter.
Suggested patch
- A short corrected snippet for the most important fix.
Rules:
- Be specific and cite the line or symbol you mean.
- Don't rewrite the whole thing unless asked.
- If the code is fine, say so plainly rather than inventing problems.
- Match the language's idioms; don't impose another language's conventions.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.