Skip to content
Skills Library
Programming · Review & audit

code-review

/code-review

Review code changes like a senior engineer — correctness, security, performance, readability — for JavaScript/TypeScript and Python. Use whenever the user asks to review, check, audit, or "look over" code, a diff, a PR, a branch, or staged changes, or asks "is this okay?", "ada bug?", "cek kode ini", even if they don't say "review".

Repository
kiln ↗
Licence
MIT
Last repository change
09.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
1
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 09.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/collect_diff.sh

What it does and when to use it

Review code changes like a senior engineer — correctness, security, performance, readability — for JavaScript/TypeScript and Python. Use whenever the user asks to review, check, audit, or "look over" code, a diff, a PR, a branch, or staged changes, or asks "is this okay?", "ada bug?", "cek kode ini", even if they don't say "review".

Triggers from the description

look overis this okay?ada bug?cek kode init say
Original author description

Review code changes like a senior engineer — correctness, security, performance, readability — for JavaScript/TypeScript and Python. Use whenever the user asks to review, check, audit, or "look over" code, a diff, a PR, a branch, or staged changes, or asks "is this okay?", "ada bug?", "cek kode ini", even if they don't say "review".

How it works

  1. 1. Establish scope
  2. 2. Understand intent before judging
  3. 3. Check, in priority order
  4. 4. Verify, don't guess
  5. 5. Output format
Original SKILL.md headings · 71 lines, 482 words
SKILL.md preview
---
name: code-review
description: Review code changes like a senior engineer — correctness, security, performance, readability — for JavaScript/TypeScript and Python. Use whenever the user asks to review, check, audit, or "look over" code, a diff, a PR, a branch, or staged changes, or asks "is this okay?", "ada bug?", "cek kode ini", even if they don't say "review".
---

# Code Review

Goal: find the issues that actually matter, ranked by impact, with concrete fixes. Not a style lecture.

## 1. Establish scope

Figure out what to review, in this order:
1. Files/snippets the user pointed at.
2. Otherwise `git diff --staged`; if empty, `git diff`; if empty, `git diff main...HEAD` (try `master` if `main` doesn't exist).
3. If still nothing, ask.

Run `scripts/collect_diff.sh` to get the diff plus a file list in one go. Read the surrounding code of every changed hunk — bugs usually live at the boundary between new and old code, so the diff alone is not enough.

## 2. Understand intent before judging

Read the commit message / PR description / user's explanation. Ask yourself: what is this change trying to do? A review that misses the intent produces noise.

## 3. Check, in priority order

**🔴 Blocker — correctness & security**
- Logic errors, off-by-one, wrong conditions, unhandled `null`/`undefined`/`None`
- Async mistakes: missing `await`, unhandled promise rejections, `async` in `forEach`, race conditions, Python `asyncio` calls blocking the loop
- Injection: SQL string concatenation, `eval`/`exec`, shell commands built from input, `dangerouslySetInnerHTML`, Python `pickle`/`yaml.load` on untrusted data
- Secrets hard-coded, auth/permission checks missing on new endpoints
- Resource leaks: files/connections not closed (use `with` / `try…finally`)
- Mutable default arguments in Python (`def f(x=[])`)

**🟡 Should fix — robustness & performance**
- N+1 queries, work inside loops that could be hoisted, unbounded memory growth
- Error handling that swallows exceptions (`except: pass`, empty `catch {}`)
- TypeScript: `any`, unsafe `as` casts, non-null `!` hiding real nulls
- Missing tests for new branches
- React: missing/incorrect `useEffect` dependencies, keys from array index on reorderable lists

**🟢 Nice to have — maintainability**
- Naming, duplication, dead code, overly long functions
- Only mention if it materially helps; skip pure taste.

## 4. Verify, don't guess

If a project has them, run them and include results:
- JS/TS: `npx tsc --noEmit`, `npm run lint`, `npm test -- --related` (or the project's equivalents in `package.json`)
- Python: `ruff check`, `mypy`, `pytest -q` on affected tests

Don't claim something is a bug unless you can explain the input that triggers it. If unsure, say "possible issue" and why.

## 5. Output format

```
## Summary
<1–2 sentences: what changed and the overall verdict: ✅ ready to merge / ⚠️ needs fixes / ❌ don't merge>

## 🔴 Blockers
- `path/file.ts:42` — <the problem>. <why it's dangerous>.
  Fix: <short code fix>

## 🟡 Should fix
...

## 🟢 Suggestions
...

## What's already good
<1–3 specific points, not filler>
```

Write the report in the user's language (for example, Indonesian if they wrote in Indonesian); translate the headings too. Omit empty sections. Max ~10 findings; if more, keep the most important and say how many minor ones were left out.

Offer to apply the fixes — don't edit files unless the user asks.
Files in this package (2)
  • SKILL.md 3 KB
  • scripts/collect_diff.sh 1 KB

Versions

RepositoryScoreLicence
This page · KILN-skills/kiln100MIT
microsoft/aspire100MIT
kdlbs/kandev100AGPL-3.0
dotnet/runtime100MIT
drosam/agents100MIT
ggml-org/llama.cpp100MIT
ShamelesAbyss/Nyx100Apache-2.0
dzhng/jevgrep100MIT
iuliandita/skills100MIT

Database snapshot: 13.11.2026 · package version 5e63ed251c64 (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

  • 100code-reviewer
    Senior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.
  • 90senior-code-reviewer
    Reviews code like a senior engineer for bugs, edge cases, readability, performance and maintainability. Use when the user pastes code or a diff for review, or asks 'review this', 'is this good code' or 'what would you change'.
  • 100code-review-changes
    Reviews code changes (a pull request, merge request or diff) like a senior engineer - finds real bugs, security holes, data risks and breaking changes, verifies each one, and reports it with file:line, a concrete failure scenario and a suggested fix. Use when asked to review a…
  • 100code-review-senior
    Senior code review skill. Analyze code changes for security, performance, code quality, architecture, and testing. Use when reviewing code changes.
  • 100review-code
    Multi-dimensional code review with structured reports. Analyzes correctness, readability, performance, security, testing, and architecture. Triggers on "review code", "code review", "审查代码", "代码审查".
  • 100code-review-checklist
    Five-axis code review checklist (correctness, security, readability, performance, test coverage) producing actionable comments instead of style nitpicks. Use when the user asks to review code, a diff, or a pull request.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.