skills.rest
LAF-US
LAF-USOFFICIAL
Explore all skills by this author →
GitHub

review

Review pull request diffs and report actionable bugs with remediation steps.

Updated Dec 17, 2024
Search Tags:#diff#code-review#pull-request#structured-feedback#security-analysis#bug-spotting
One-click install
npx skills add https://github.com/LAF-US/IDAHO-VAULT --skill review-laf-us
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/LAF-US/IDAHO-VAULT/tree/main/.factory/plugins/cache/factory-plugins/core/5e938b7ef9e3/skills/review
Command: npx skills add https://github.com/LAF-US/IDAHO-VAULT --skill review-laf-us

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review code changes and identify high-confidence, actionable bugs. This skill helps engineers quickly surface defects, security issues, and correctness problems in diffs and PRs.

Core Features & Use Cases

  • Diff analysis & triage: Inspect pull requests and branch diffs to locate defects and quality issues.
  • Structured findings: Produce a concise, prioritized list of actionable bugs with remediation steps.
  • Quality gates: Check for security vulnerabilities, edge-case failures, and contract violations across changes.
  • Use Case: When a teammate submits a PR, generate a structured review summary highlighting critical bugs and suggested fixes.

Quick Start

Provide the current PR diff and target/base branches and I will generate a structured review report.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review a pull request for bugs and security issues?▼

To review a pull request, provide the current PR diff and target/base branches to generate a structured review report. This process surfaces high-confidence, actionable bugs, security vulnerabilities, and correctness problems with clear remediation steps.

What is the best way to analyze branch diffs for correctness problems?▼

The best way to analyze branch diffs for correctness problems is applying structured code review to inspect changes. This identifies functional correctness issues, edge-case failures, and contract violations across the provided code changes.

Can I get structured feedback on my code changes before merging?▼

Yes, you can get structured feedback on code changes by submitting your pull request diffs. The review generates a concise, prioritized list of actionable bugs and quality issues with suggested fixes before merging.

Does this code review process check for edge-case failures and performance issues?▼

Yes, this code review process checks for edge-case failures and performance issues. It acts as a quality gate to ensure results cover functional correctness, security vulnerabilities, and edge-case handling across all changes.

How do I surface security vulnerabilities in a diff?▼

You surface security vulnerabilities in a diff by providing the code changes to the review process. It inspects the pull request to locate defects and produces a structured summary highlighting critical vulnerabilities with remediation steps.

Related Skills

Explore More Software Engineering Skills→
rioX432rioX432
2

review

Review branch changes against the base branch for bugs, security, architecture, and quality issues.

Community
Advanced
Srain021Srain021

kestrel-mcp-role-code-reviewer

Identify code-quality issues with file:line pointers and severity labels.

Community
Advanced
giuseppe-trisciuogliogiuseppe-trisciuoglio
322

unit-test-utility-methods

Test static utility methods with JUnit 5 and AssertJ.

Community
Basic
ajsai47ajsai47
11

review

Analyze git diffs for SQL injection, race conditions, and shell injection risks.

Community
Advanced