Skill

code-review

Systematic code review workflow with checklist, security scan, and feedback templates. Use when user says "review code", "code review", or "review PR".

Install

npx claudepluginhub monty1985/adams-mind --plugin dev-code-review

Tool Access

This skill uses the workspace's default tool permissions.

Preview

- Read the PR description and linked ticket before looking at the diff

SKILL.md

Similar Skills

using-git-worktrees

Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.

superpowers

166.1k

subagent-driven-development

3 files

Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.

superpowers

166.1k

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

166.1k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitApr 1, 2026

Actions

View Source View Plugin View on GitHub View README

Code Review

Phase 1: Overview

Read the PR description and linked ticket before looking at the diff

Understand the intent and scope of the change

Check that the PR is appropriately sized (prefer small, focused PRs)

Confirm the branch is up to date with main/trunk

Phase 2: Review Checklist

Correctness: Does the code do what the ticket/story requires?

Readability: Is the code clear and well-named?

Tests: Are unit and integration tests present and passing?

Security: Check for SQL injection, XSS, auth bypasses, exposed secrets

Performance: Flag N+1 queries, unnecessary re-renders, or heavy computations

Error handling: Are edge cases and failure modes handled gracefully?

Documentation: Are public APIs, complex logic, and config changes documented?

Phase 3: Feedback

Lead with praise for good patterns before raising concerns

Use "nit:" prefix for non-blocking style suggestions

Clearly mark blocking issues that must be resolved before merge

Suggest alternatives rather than just pointing out problems

Approve once all blocking issues are resolved

Code Review

Phase 1: Overview

Read the PR description and linked ticket before looking at the diff
Understand the intent and scope of the change
Check that the PR is appropriately sized (prefer small, focused PRs)
Confirm the branch is up to date with main/trunk

Phase 2: Review Checklist

Correctness: Does the code do what the ticket/story requires?
Readability: Is the code clear and well-named?
Tests: Are unit and integration tests present and passing?
Security: Check for SQL injection, XSS, auth bypasses, exposed secrets
Performance: Flag N+1 queries, unnecessary re-renders, or heavy computations
Error handling: Are edge cases and failure modes handled gracefully?
Documentation: Are public APIs, complex logic, and config changes documented?

Phase 3: Feedback

Lead with praise for good patterns before raising concerns
Use "nit:" prefix for non-blocking style suggestions
Clearly mark blocking issues that must be resolved before merge
Suggest alternatives rather than just pointing out problems
Approve once all blocking issues are resolved