code-review

Reviews branch diffs against the remote origin base branch for quality, bugs, and security.

1|Updated Feb 16, 2025
One-click install
npx skills add https://github.com/yellow-seed/my-portfolio --skill code-review-yellow-seed
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/yellow-seed/my-portfolio/tree/main/.github/skills/code-review
Command: npx skills add https://github.com/yellow-seed/my-portfolio --skill code-review-yellow-seed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually reviewing every change before merging a pull request is time-consuming and easy to get wrong. This Skill automates a structured review of the diff between your current branch and its remote origin base branch, surfacing issues before they reach production. ## Core Features & Use Cases - Multi-Dimensional Review: Evaluates code quality, best practices, potential bugs, performance, security, and test coverage across six defined review perspectives. - Structured Findings: Reports issues per file with severity levels (Critical / High / Medium / Low) plus concrete improvement suggestions and code examples. - Merge Recommendation: Produces a summary with changed file counts, added/removed lines, impact assessment, and an overall merge-or-fix verdict. - Use Case: Before opening a pull request, run a review of your feature branch against origin/main to catch logic errors, missing tests, and security concerns, then fix them before requesting human review. ## Quick Start Review the diff between my current branch and its remote origin base branch and give me a full code review with severity-rated findings.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review code changes before creating a pull request?▼

Run a diff-based review comparing your current branch against its remote origin base branch. The review inspects each changed file for quality, bugs, performance, security, and test coverage, then reports findings with severity levels and a merge recommendation.

What does an automated code review check for?▼

It checks six dimensions: code quality (readability, naming, complexity), best practices and design patterns, potential bugs and edge cases, performance inefficiencies, security vulnerabilities and input validation, and test coverage adequacy.

Can I use code review for reviewing my own changes?▼

Yes, diff-based review works for self-review of your own branch changes. For a dedicated self-review workflow with detailed checklists, a specialized self-review skill is referenced as the more thorough option.

What are the limitations of diff-based code review?▼

Diff-based review only sees changed lines and their immediate context, so it may miss issues in untouched code that interacts with the changes. It also requires the branch to have a remote origin base branch to compute the diff.

How are code review findings prioritized?▼

Findings are rated by severity as Critical, High, Medium, or Low for each changed file. The final summary highlights priority items to address first and gives an overall merge-or-fix recommendation.