Agent skill · luongnv89
code-review
Review or improve code — one skill, four modes: bug/security review (default), performance, clean-code audit, slop cleanup. Pass mode:review|perf|clean|cleanup or infer. Don't use for writing features or generating tests (use test-coverage).
What it needs
About 4k tokens when loaded.
What this skill does
Code Review One skill for reviewing and improving code quality. Pick a mode by intent (or pass an explicit mode: parameter); each mode is a full, self-contained workflow in references/. Load only the mode you need — this protects the agent's context budget. Modes Mode Use when the user wants to... Reads / writes Output Workflow --- --- --- --- --- review (default) find bugs, security holes, quality issues in a diff/PR read-only prioritized findings report references/review-mode.md perf make code faster — bottlenecks, leaks, algorithmic waste read-only performance findings report references/perf-mode.md clean audit readability/standards vs the bbv Clean Code cheat sheet read-only CLEANCODEAUDIT.md references/clean-mode.md cleanup actually refactor out AI slop, dead code, duplication, cruft WRITES CODE modified source files references/cleanup-mode.md Selecting the mode 1. Explicit wins. If the request carries mode:review perf clean cleanup (or --mode <name>), use it. 2. Otherwise infer from the request: "review", "find bugs", "security", "is this correct", "look for vulnerabilities" → review "slow", "faster", "optimize", "bottleneck", "memory leak", "performance" → perf "clean code audit" (or "clean-code audit"), "clean code review", "check this against clean code" → clean (user-invoked only — a bare "readability" or "audit against standards" ask is ambiguous: use step 3) "remove slop", "clean up the codebase", "refactor out cruft / dead code / duplication" → cleanup 3. Ambiguous? Ask which mode, naming the options. Fall back to review only when the intent is clearly "review this" with no other signal. Safety: cleanup writes code — the other three do not review, perf, and clean are strictly read-only: they analyze and report, never touching source. cleanup modifies files. Therefore: Never enter cleanup by weak inference. Run it only when the user explicitly asks to refactor / clean up the codebase (or passes mode:cleanup). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills luongnv89/code-review