Skip to content
Skills Library
Programming · Review & audit

review-code

/review-code

Use when the user asks for a review or what could be improved (Indonesian: kodenya bagus?, ada yang bisa diperbaiki?, cek kodenya, review), and before committing a larger change. Finds real bugs first and changes nothing until the user approves.

Licence
MIT
Last repository change
13.11.2026

Assessment and security

86/ 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.
Content21 / 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
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

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

Licence

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

What it does and when to use it

Use when the user asks for a review or what could be improved (Indonesian: kodenya bagus?, ada yang bisa diperbaiki?, cek kodenya, review), and before committing a larger change. Finds real bugs first and changes nothing until the user approves.

Original author description

Use when the user asks for a review or what could be improved (Indonesian: kodenya bagus?, ada yang bisa diperbaiki?, cek kodenya, review), and before committing a larger change. Finds real bugs first and changes nothing until the user approves.

How it works

SKILL.md has no level-two headings · 18 lines, 179 words

SKILL.md preview
---
name: review-code
description: >-
  Use when the user asks for a review or what could be improved (Indonesian: kodenya bagus?,
  ada yang bisa diperbaiki?, cek kodenya, review), and before committing a larger change.
  Finds real bugs first and changes nothing until the user approves.
---
# Review code

1. Say what you review: the uncommitted diff (`git diff`, `git diff --staged`), a file, or a feature.
2. If subagents are available, ask the `code-reviewer` subagent for an independent pass on the diff,
   and do your own pass too.
3. Look in this order:
   - correctness: wrong logic, missing states, off-by-one, special values (-1, null, "") meaning two things
   - errors: unhandled promise rejections, empty catch, raw errors shown to users
   - security: secrets in code, injection (shell / SQL / HTML), missing auth or quota check before paid calls
   - data loss: destructive migrations, overwrites, races
   - performance: N+1 queries, render loops, unbounded lists / memory
   - dead code, then readability (last)
4. Every finding needs a concrete scenario: input → wrong result. No scenario → drop it.
5. Output, most severe first, max ~10:
   `[HIGH|MED|LOW] file:line — problem / Scenario: ... / Fix: ...`
   Then ask which ones to fix (in the user's language). Change NOTHING until the user picks.
6. Nothing found → "No findings" + the list of what you checked.

Versions

RepositoryScoreLicence
This page · AndreasTopuh/agent-workflow-kit86MIT
doodledood/manifest-dev100MIT
serpro69/claude-toolbox100Apache-2.0
serpro69/claude-toolbox100Apache-2.0
jelvodev/yaap100MIT
globalmindsolution/gms-marketplace100MIT
tojim00d/Orbit-skills100MIT
yaohuangguan/agent-playbook100MIT
paultyng/skill-issue100MIT

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

  • 100review-queue
    Use when the user wants every pull request that requests their review handled, each in its own session — `/review-queue [--team] [--root <dir>] [--comment] [--every <interval>]`, "cek PR yang minta review ke aku", "cek tiap 30 menit PR yang request review", "review semua PR yang…
  • 86code-review
    Use when the user asks to review, check or look over code changes (uncommitted diff, a commit, a branch or a file) before commit or merge. Finds bugs, not style nits.
  • 100code-review-edho-ferdian
    Senior code review across quality, security, performance, spec consistency and tests, with evidence-backed, severity-ranked findings. Load it for any review, even a short snippet or a quick "is this OK?". Use for "review this", "cek kode", "cek dulu sebelum merge", "ada yang…
  • 100pr-review
    Use when reviewing a teammate's pull request for the first time — `/pr-review <PR>`, "review PR #123", "tolong review PR-nya Budi", "ada PR yang minta review", "cek PR tim", "review requested". Not for a PR already reviewed once (that is `/recheck`) and not for your own unpushed…
  • 100comment-review
    Review and simplify the comments in existing code by spawning the comment-refiner agent. Finds comments that restate the code, sit in the wrong place, keep change history, describe callers, or use terms that do not match the code, then deletes, moves, or rewrites them after the…
  • 100code-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…

Feedback and reports

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