code-review_skill

This skill guides you through a comprehensive code review checklist to ensure functionality, quality, tests, security, performance, and documentation.

JavaScript

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill block/agent-skills --skill code-review

SKILL.md1.0 KB

Overview

This skill is a concise, actionable code review checklist tailored for pull request reviewers working on JavaScript projects. It helps reviewers evaluate functionality, quality, tests, security, performance, and documentation to accelerate reliable merges. Use it to standardize reviews and reduce regressions.

How this skill works

The skill presents a checklist grouped by review focus areas: Functionality, Code Quality, Testing, Security, Performance, and Documentation. For each PR you inspect, run through the checklist items and mark pass/fail or leave comments on violations. The checklist is designed to be lightweight so it fits into common PR workflows and review tools.

When to use it

When performing manual code reviews for pull requests.
During peer review rotations to ensure consistent standards.
Before merging features or bug fixes to catch regressions.
When onboarding new reviewers to teach review priorities.
To audit critical changes for security and performance risks.

Best practices

Start by validating the PR description and reproducing the claimed behavior.
Prioritize tests and error handling — failing tests or unhandled errors block merges.
Leave focused, constructive comments tied to checklist items, not personal style.
Require documentation or README updates for public API or UX changes.
Use the checklist as a minimum; escalate complex concerns to the author or a tech lead.

Example use cases

A reviewer verifies a bug fix PR: confirm behavior, run tests, and check edge cases.
A team runs a pre-merge audit on a performance-sensitive endpoint for query optimization.
Security-focused review for a PR that touches authentication or data access.
Release blockers: ensure all new features include meaningful tests and documentation.

FAQ

Treat the checklist as minimum standards. Some items may be context-dependent; use reviewer judgment and escalate when unsure.

How do I handle style issues versus functional problems?

Prioritize functional, security, and test failures. Minor style issues can be addressed with automated linters or follow-up commits unless they affect readability or correctness.