Skip to content
Skills Library
Programming · Review & audit

code-review

/code-review

Use when reviewing AI-generated code for architectural quality, design patterns, and engineering practices

Licence
MIT
Last repository change
15.10.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
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 15.10.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 reviewing AI-generated code for architectural quality, design patterns, and engineering practices

Original author description

Use when reviewing AI-generated code for architectural quality, design patterns, and engineering practices

How it works

  1. Review methodology
  2. Scoring principles
Original SKILL.md headings · 41 lines, 350 words
SKILL.md preview
---
name: code-review
description: Use when reviewing AI-generated code for architectural quality, design patterns, and engineering practices
---

# Code Review for Assessment Evaluation

You are reviewing code produced by an AI coding agent. Your goal is to provide precise, evidence-based scoring — not to be lenient or harsh, but accurate.

## Review methodology

1. **Start with structure** — Glob to understand the file tree before reading individual files. The shape of the codebase tells you about architectural decisions.

2. **Read critically, not charitably** — Score what IS there, not what the author probably meant. If a pattern is half-implemented, score it as half-implemented.

3. **Trace the domain model** — Follow the flow from entry point to persistence. Look for:
   - Are domain concepts explicit types or buried in primitives?
   - Do boundaries between modules/layers exist and hold?
   - Is business logic in the domain or scattered across infrastructure?

4. **Check encapsulation** — Look for:
   - Public fields that should be private
   - Getter/setter pairs that expose internals
   - Domain objects that are just data bags with no behavior
   - Invariants that are enforced externally rather than internally

5. **Evaluate test quality** — Tests that merely exist are not enough. Check:
   - Do tests verify behavior or just call methods?
   - Are edge cases and failure modes covered?
   - Do test names describe the scenario being tested?
   - Are tests testing the unit or the framework?

6. **Look for anti-patterns** — Common problems to flag:
   - Anemic domain models (logic in services, entities are just DTOs)
   - Leaking abstractions (domain depends on infrastructure types)
   - God classes or methods doing too many things
   - Copy-paste with minor variations instead of proper abstraction

## Scoring principles

- **Evidence required** — Every score must cite specific files, classes, or code patterns. "The code generally looks good" is not evidence.
- **Calibration** — A max score means excellent, not merely acceptable. Reserve top scores for genuinely well-crafted code.
- **Partial credit** — If the agent solved the core problem but cut corners on secondary concerns, reflect both in the score and reasoning.
- **Zero scores are valid** — If a dimension was completely ignored by the agent, score 0 with explanation.

Versions

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

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version e8bb11db59e1 (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-reviewing
    Review code for quality, security, and best practices. Use when the user asks for code review, wants feedback on their code, mentions reviewing changes, or asks about code quality.
  • 100reviewing-my-code
    Perform code reviews following my engineering practices. Use when reviewing changes in a branch.
  • 82review-code
    Use to review code.
  • 100review
    Review Playwright tests for quality. Use when user says \"review tests\", \"check test quality\", \"audit tests\", \"improve tests\", \"test code review\", or \"playwright best practices check\".
  • 100review
    Review Playwright tests for quality. Use when user says "review tests", "check test quality", "audit tests", "improve tests", "test code review", or "playwright best practices check".
  • 100coding-best-practices
    Reviews Swift/iOS code for adherence to modern Swift idioms, Apple platform best practices, architecture patterns, and code quality standards. Use when user mentions best practices, code review, clean code, refactoring, or wants to improve code quality.

Feedback and reports

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