code-review

Analyze GitHub PR diffs and surrounding code to generate actionable review feedback.

6|2|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/v1-io/v1tamins --skill code-review-v1-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/v1-io/v1tamins/tree/main/claude/skills/code-review
Command: npx skills add https://github.com/v1-io/v1tamins --skill code-review-v1-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR reviews can be time-consuming and error-prone; this skill provides staff-level analysis and a structured feedback loop to improve code quality on GitHub.

Core Features & Use Cases

  • Context-aware review: extracts PR details, diffs, and surrounding code to deliver precise feedback.
  • Automated posting: formats and posts the review back to GitHub as a comment.
  • Use Case: use on large PRs to identify risk factors (auth, migrations, performance) and suggest concrete changes.

Quick Start

Invoke the /code-review command with a PR URL or number to generate and publish a thorough PR review.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate a GitHub pull request review?

You can automate a GitHub pull request review by invoking the /code-review command with a PR URL or number. It analyzes diffs and surrounding code to generate actionable feedback and posts it directly as a GitHub comment.

Can I use automated code review for large refactors and complex PRs?

Yes, automated code review handles large refactors and complex PRs across repositories of varying sizes and languages. It identifies risk factors like auth, migrations, and performance issues while emphasizing correctness, security, and readability.

How does context-aware code review work for a diff?

Context-aware code review works by extracting PR details, diffs, and surrounding repository code to deliver precise feedback. This ensures the analysis understands the broader codebase environment rather than evaluating changes in isolation.

What is the best way to identify security risks in a pull request?

The best way to identify security risks in a pull request is using an automated review tool that analyzes diffs for auth vulnerabilities and risk factors. It provides structured feedback to improve code security before merging.

Do I need a specific programming language to run automated PR analysis?

No, you do not need a specific programming language to run automated PR analysis. The review process applies to repositories of varying languages, handling both small fixes and large refactors with language-agnostic context awareness.