code-review
/code-review
Review code or a diff for correctness bugs, security issues, and clear simplifications. Use when users ask to review code, check a PR/diff, find bugs, audit a function, or ask 'is this code correct/safe', 'what's wrong with this'. Covers logic errors, edge cases, error handling, concurrency, injection/secrets, and readability. Triggers on mentions of review, code review, audit, find bugs, check this code, PR review, 代码审查, 评审, 查 bug, 看看这段代码.
- Author
- microclaw ↗
- Repository
- microclaw ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Review code or a diff for correctness bugs, security issues, and clear simplifications. Use when users ask to review code, check a PR/diff, find bugs, audit a function, or ask 'is this code correct/safe', 'what's wrong with this'. Covers logic errors, edge cases, error handling, concurrency, injection/secrets, and readability. Triggers on mentions of review, code review, audit, find bugs, check this code, PR review, 代码审查, 评审, 查 bug, 看看这段代码.
Triggers from the description
Original author description
Review code or a diff for correctness bugs, security issues, and clear simplifications. Use when users ask to review code, check a PR/diff, find bugs, audit a function, or ask 'is this code correct/safe', 'what's wrong with this'. Covers logic errors, edge cases, error handling, concurrency, injection/secrets, and readability. Triggers on mentions of review, code review, audit, find bugs, check this code, PR review, 代码审查, 评审, 查 bug, 看看这段代码.
How it works
- What to look for (in priority order)
- How to report
- Guidance
SKILL.md preview
--- name: code-review description: "Review code or a diff for correctness bugs, security issues, and clear simplifications. Use when users ask to review code, check a PR/diff, find bugs, audit a function, or ask 'is this code correct/safe', 'what's wrong with this'. Covers logic errors, edge cases, error handling, concurrency, injection/secrets, and readability. Triggers on mentions of review, code review, audit, find bugs, check this code, PR review, 代码审查, 评审, 查 bug, 看看这段代码." license: Proprietary. LICENSE.txt has complete terms compatibility: "No external dependencies. Works on macOS, Linux, and Windows." --- # Code Review Review like a senior engineer who is kind but does not rubber-stamp. Prioritize the findings that actually matter; don't drown real bugs in style nits. ## What to look for (in priority order) 1. **Correctness** — wrong logic, off-by-one, inverted conditions, bad null/empty/zero handling, wrong types, incorrect async/await, missing returns. 2. **Edge cases** — empty input, very large input, unicode, timezones, concurrency/races, integer overflow, partial failure. 3. **Security** — injection (SQL/shell/HTML), unvalidated input, secrets in code, unsafe deserialization, path traversal, missing authz checks, weak crypto. 4. **Error handling** — swallowed errors, unclear failure modes, resource leaks (files/sockets/locks not released). 5. **Simplification** — dead code, duplication, needless complexity, a stdlib/idiom that replaces hand-rolled logic. 6. **Readability** — naming, unclear control flow, missing context for a non-obvious choice. ## How to report For each finding: ``` [severity: bug | security | nit] file:line what: <the problem, one line> why: <impact / failing case> fix: <concrete suggestion or patch> ``` - Lead with the highest-severity items. If the code is solid, say so plainly and list only the few things worth changing. - Distinguish "this is a bug" from "I'd prefer." Don't invent problems to look thorough. - When unsure whether something is a bug, say "verify: …" rather than asserting. ## Guidance - If a diff is available, review the diff in context, not the whole repo. - Suggest a test for any non-trivial bug you find. - Keep the review proportional: a 10-line snippet gets a few lines back, not an essay.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · microclaw/microclaw | 100 | MIT |
| microsoft/aspire | 100 | MIT |
| kdlbs/kandev | 100 | AGPL-3.0 |
| dotnet/runtime | 100 | MIT |
| drosam/agents | 100 | MIT |
| ggml-org/llama.cpp | 100 | MIT |
| ShamelesAbyss/Nyx | 100 | Apache-2.0 |
| dzhng/jevgrep | 100 | MIT |
| iuliandita/skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version 2db960971605 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100quick-review
Review a code diff or file for correctness bugs, security issues, and clear simplifications. One finding per line, severity-tagged. Use when user wants fast, focused code review. - 90code-audit
Review code for correctness bugs, concurrency and lifecycle errors, type-safety holes, error handling gaps, API-contract breaks, and maintainability problems, with every finding gated on a concrete failure scenario. Use when asked to review code, check a diff or branch for bugs,… - 90code-audit
Review code for correctness bugs, concurrency and lifecycle errors, type-safety holes, error handling gaps, API-contract breaks, and maintainability problems, with every finding gated on a concrete failure scenario. Use when asked to review code, check a diff or branch for bugs,… - 95combined-review-code-reviewer
Reviews code changes for repo-policy compliance (CLAUDE.md / AGENTS.md), bugs, logic errors, and code quality. Reads full files (not just diff) for context. Use when reviewing any code changes — PR, branch diff, or uncommitted work. - 90Code Review
Use when reviewing a diff, pull request, or patch - correctness and edge cases, security, API and data model changes, test quality, performance, error handling, and readability. Also covers writing review comments that are actionable and prioritised, giving an approval,… - 90find-bugs
Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.