Skip to content
Skills Library
Programming · Review & audit

code-review

/code-review

Exacting review of code changes for bugs, structure, reuse, comment discipline, and dead code, ending in a pass / needs revision / reject verdict. Use for any code review, including a GitHub PR number or URL.

Repository
avintra ↗
Licence
Apache-2.0
Last repository change
13.11.2026

Assessment and security

90/ 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.
Content25 / 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
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

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Exacting review of code changes for bugs, structure, reuse, comment discipline, and dead code, ending in a pass / needs revision / reject verdict. Use for any code review, including a GitHub PR number or URL.

Arguments

/code-review Diff, commit, branch, file, snippet, or GitHub PR (#123 / URL); optional review focus
Original author description

Exacting review of code changes for bugs, structure, reuse, comment discipline, and dead code, ending in a pass / needs revision / reject verdict. Use for any code review, including a GitHub PR number or URL.

How it works

  1. 1. Load the target
  2. 2. Load the conventions
  3. 3. Apply every rule to every changed file
  4. 4. Report
Original SKILL.md headings · 63 lines, 549 words
SKILL.md preview
---
name: code-review
argument-hint: "Diff, commit, branch, file, snippet, or GitHub PR (#123 / URL); optional review focus"
description: "Exacting review of code changes for bugs, structure, reuse, comment discipline, and dead code, ending in a pass / needs revision / reject verdict. Use for any code review, including a GitHub PR number or URL."
---

# Code Review

Review as an **exacting** senior developer: is the code robust, modular, readable at a glance, and consistent with this repository? Judge engineering decisions, not just correctness. Formatting counts only where it hurts readability or maintenance.

## 1. Load the target

- **GitHub PR** (`#123`, `123`, or a PR URL): follow [`github-pr.md`](github-pr.md). The review stays read-only: the PR is never commented on, approved, rejected, or merged. Landing it is `merge-pr`'s job.
- **Branch**: `git diff <base>...HEAD`, with the branch's base (ask when unclear).
- **Commit**: `git show <sha>`.
- **Working tree**: `git diff` plus `git diff --cached`.
- **Snippet or file**: review it as given.

Done when you hold the complete changed-file list and diffstat. Name any file you could not read (binary, generated, fetch failure) instead of reviewing it blind. If a reliable review needs context you lack, say what is missing.

## 2. Load the conventions

Read the root `AGENTS.md`, the area `AGENTS.md` for each touched area (`apis/WorcBackend-legacy/`, `clients/web-apps/`), and each touched feature's `README.md`. Structure and naming are judged against these.

## 3. Apply every rule to every changed file

Each heading is also a report section, in this order.

### 1. Critical Issues & Bugs

Logic flaws, race conditions, unhandled exceptions or promises, data loss, missing authentication or authorization, injection, resource leaks, and breaking changes to state, APIs, or data models. This is the highest-priority section.

### 2. Architecture / Modularity

One responsibility per file. Components, models, utilities, services, and integrations live in separate files inside clear domain boundaries, following the feature-folder layout the area `AGENTS.md` defines. Flag oversized files and logic crammed into one file.

A feature carries the same name on the frontend and the backend: the `src/features/<feature>/` folder, its `.apis.ts` and DTO files, and the backend controller, service, and DTOs name the domain identically, differing only in casing (kebab-case, camelCase, PascalCase). Flag every mismatch (`machines` vs `RunnerController`, `job-schedules` vs `TriggersController`) as an issue, naming both sides and the name to converge on.

### 3. Code Reuse

New logic written where an existing method, hook, helper, utility, or library already does the job, and copy-pasted patterns. Name the existing abstraction to reuse.

### 4. Documentation / Comments

- Precise names and decomposition carry the meaning. A large function held together by explanatory comments needs splitting.
- Exported or public APIs and complex public types carry one short JSDoc/XML sentence describing the contract. Internal functions and variables stay undocumented.
- The only inline comments are `IMPORTANT NOTE:` warnings about external constraints, race conditions, or required hacks.

### 5. Dead Code

Variables, functions, classes, imports, fields, or branches left unused or obsolete by the change, plus stale scaffolding and temporary logic.

### 6. General Quality

Naming, edge cases, clarity, and any other issue that reduces maintainability.

Done when every changed file has been checked against all six sections.

## 4. Report

Open with the scope: changed-file list and diffstat. Then give the six sections in order. Each finding names a `path:line` (or code region) and the concrete fix. Write "None" for an empty section. Close with:

### 7. Verdict

`pass`, `needs revision`, or `reject`, with a one-line reason.

When delegated, write the review into the assigned report and return the shared compact status summary. Include the full findings payload only when asked for routing.
Files in this package (2)
  • SKILL.md 4 KB
  • github-pr.md 2 KB

Versions

RepositoryScoreLicence
This page · aventisia/avintra90Apache-2.0
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 130d1fe6e1e1 (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
    Perform a comprehensive code review on a GitHub pull request. Use when the user asks to review a PR, review code changes, check a pull request for quality, security, bugs, or best practices, or provides a PR number or GitHub PR URL to review.
  • 82review-code
    Use to review code.
  • 98review-code
    Review recent code changes for security issues, PII leaks, and bugs against CodingStyle.md. Triggers on "/review-code" or when called by commit skill.
  • 90reviews
    Review a pull request or code change for code health. Use when a user asks to "code review", "review this PR", or "review this change".
  • 100code-quality-auditor
    审查 git 变更、Review Gate、merge ready、发布前审计以及代码、文档、配置、脚本质量门禁时使用。输出结构化 Pass 或 Reject 结论、问题分级、最低验证矩阵、证据链和复查基线;当用户提到 review、code review、审计、review gate、merge ready、blocker、evidence、pass、reject 时触发。
  • 84review-code
    Review code changes for quality, security, and performance. Use when user says "review my changes", "do a code review", "check this for issues", "analyze code quality", "security review", "performance review", "is this PR ready", or needs architecture, security, performance, and style analysis.

Feedback and reports

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