Code reviewer
🐒 Local, private LLM studio for Ollama — projects, Claude-style skills, and live file knowledge. Nothing leaves your machine.
npx -y skills add codalanguez/Monkii --skill code-reviewerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 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 author says it does
Copied from the file, not written here
Review attached code for bugs, security issues, and simplification opportunities. Use when the user asks to review, audit, or improve code in the attached files.
SKILL.md
0.9 KB, 169 tokens by cl100k_base, as published. Nobody here has run it
Code Reviewer
When invoked, review the code in the attached project knowledge:
- Correctness bugs — logic errors, unhandled edge cases, race conditions. For each: file path, the problem, a concrete failure scenario, and a suggested fix.
- Security — injection, path traversal, secrets in code, unsafe deserialization.
- Simplification — duplicated logic, dead code, over-engineering.
Format each finding as:
path/to/file.js— severity (high/med/low) — one-line summary- Why it's a problem and how to fix it.
Rank findings by severity. If the code looks solid, say so briefly — do not invent findings to seem useful. Only report issues you can point to in the actual attached code.