code-reviewer

Review pull requests for bugs, security vulnerabilities, and design issues.

105|16|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/jordanhubbard/loom --skill code-reviewer-jordanhubbard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/jordanhubbard/loom/tree/main/personas/default/code-reviewer
Command: npx skills add https://github.com/jordanhubbard/loom --skill code-reviewer-jordanhubbard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces the risk of defective software by enabling automated, security-aware reviews that catch bugs, vulnerabilities, and design gaps before code ships.

Core Features & Use Cases

  • Critical code analysis for correctness, security, performance, and readability.
  • Enforcement of coding standards and best practices with concrete, actionable feedback.
  • Use Case: during a PR, identifies a race condition or vulnerable input handling and suggests concrete remediation.

Quick Start

Provide a short, precise code review for the latest PR, focusing on correctness, security, and design.

Frequently Asked Questions about code-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I catch race conditions and security vulnerabilities during a pull request review?

Automated code review identifies race conditions and security vulnerabilities during a pull request by analyzing correctness and design, delivering structured feedback with rationale and suggested fixes to ensure post-merge quality.

What is the best way to enforce coding standards and best practices across multi-language repositories?

Enforcing coding standards across multi-language repositories requires automated code analysis that checks for inconsistent API usage and inadequate input validation, providing concrete actionable feedback to maintain code quality before merge.

Can I get design feedback and design issue identification before merging code?

Design feedback is generated before merge by applying critical code analysis to performance, readability, and design gaps, supplying rationale and follow-up checks to ensure post-merge quality.

Does automated code review work for spotting inadequate input validation and inconsistent API usage?

Automated code review works for spotting inadequate input validation and inconsistent API usage by applying security-aware analysis to pull requests, delivering structured feedback including suggested fixes and follow-up checks.

What limitations should I expect from automated security-aware code analysis?

Automated security-aware code analysis focuses on correctness, security, performance, and readability but requires a short, precise prompt for the latest PR to deliver structured feedback effectively without replacing human review.