Skill

review-standards

Use when performing formal code review on PRs

Install

npx claudepluginhub jacobpevans/claude-code-plugins --plugin code-standards

Tool Access

This skill uses the workspace's default tool permissions.

Preview

When reviewing code, prioritize:

SKILL.md

Similar Skills

angular-new-app

Creates new Angular apps using Angular CLI with flags for routing, SSR, SCSS, prefixes, and AI config. Follows best practices for modern TypeScript/Angular development. Use when starting Angular projects.

angular-angular-1

100.1k

angular-developer

20 files

Generates Angular code and provides architectural guidance for projects, components, services, reactivity with signals, forms, dependency injection, routing, SSR, ARIA accessibility, animations, Tailwind styling, testing, and CLI tooling.

angular-angular-1

100.1k

context7-cli

3 files

Executes ctx7 CLI to fetch up-to-date library documentation, manage AI coding skills (install/search/generate/remove/suggest), and configure Context7 MCP. Useful for current API refs, skill handling, or agent setup.

upstash-context7-1

53.8k

Stats

Parent Repo Stars2

Parent Repo Forks0

Last CommitMar 22, 2026

Actions

View Source View Plugin View on GitHub View README

Code Review Standards

Review Focus Areas

When reviewing code, prioritize:

Security vulnerabilities and hardcoded secrets

Performance implications of algorithmic choices

Maintainability and code clarity

Test coverage and TDD compliance

Documentation accuracy and completeness

DRY violations and code duplication

Standards compliance per code-quality-standards

PR Review Principles

Be pragmatic: Perfect security that blocks all work is worse than reasonable security that enables productivity.

Trust context: If a permission is requested for a legitimate workflow, assume good faith.

Quantify risk: Ask "how often would this actually cause harm?" not "could this ever cause harm?"

Permission & Configuration Reviews

Focus on likely failures, not theoretical edge cases. Do not reject based on contrived scenarios unlikely in practice. Balance security with usability — overly restrictive permissions that impede workflows are themselves a failure.

Related Skills

code-quality-standards (code-standards) — Use when writing or reviewing code and documentation

pr-standards (git-standards) — PR & issue standards, PR guards, issue linking

finalize-pr (github-workflows) — Manage your PR through the full author flow

Code Review Standards

Review Focus Areas

When reviewing code, prioritize:

Security vulnerabilities and hardcoded secrets
Performance implications of algorithmic choices
Maintainability and code clarity
Test coverage and TDD compliance
Documentation accuracy and completeness
DRY violations and code duplication
Standards compliance per code-quality-standards

PR Review Principles

Be pragmatic: Perfect security that blocks all work is worse than reasonable security that enables productivity.
Trust context: If a permission is requested for a legitimate workflow, assume good faith.
Quantify risk: Ask "how often would this actually cause harm?" not "could this ever cause harm?"

Permission & Configuration Reviews

Related Skills

code-quality-standards (code-standards) — Use when writing or reviewing code and documentation
pr-standards (git-standards) — PR & issue standards, PR guards, issue linking
finalize-pr (github-workflows) — Manage your PR through the full author flow