jasonkneen/agent-skills · Archived

code-review

Automated code review against project conventions (CLAUDE.md) and best practices

First seen May 25, 2026

Installation

$ npx skills add jasonkneen/agent-skills --skill code-review

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 20
License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,266 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Code Review Skill

Purpose

Provide consistent, high-signal code reviews by focusing on correctness, clarity, maintainability, security, performance, tests, and developer experience.

Inputs

  • PR description and linked issues
  • Code diffs and file context
  • Existing conventions in the repository

Review Checklist

Correctness

  • Does the change satisfy the requirements?
  • Are edge cases handled?
  • Are errors propagated/handled appropriately?

Readability & Maintainability

  • Is the code easy to follow?
  • Are names clear and consistent?
  • Is complexity justified?
  • Are public APIs documented?

Security

  • Validate/encode untrusted input
  • Avoid leaking secrets/PII
  • Check authZ/authN boundaries

Performance

  • Watch for N+1 queries, unnecessary allocations, inefficient loops
  • Ensure any tradeoffs are explained

Testing

  • Are tests added/updated?
  • Do tests cover failure cases and boundaries?
  • Are tests deterministic and fast?

Style & Consistency

  • Follows project lint/format rules
  • No dead code or commented-out blocks

Output Format

  • Summary of change
  • Key issues (must-fix)
  • Suggestions (nice-to-have)
  • Questions/uncertainties

Tone

Be constructive and specific. Prefer actionable suggestions with examples.