review

Analyze pull request diffs for security risks and logical errors.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/BaGyun0107/harness-starterkit --skill review-bagyun0107
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/BaGyun0107/harness-starterkit/tree/main/.agents/skills/gstack-review
Command: npx skills add https://github.com/BaGyun0107/harness-starterkit --skill review-bagyun0107

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers identify potential issues in pull requests by analyzing code differences for SQL safety risks, trust boundary violations, conditional side effects, and structural problems, preventing bugs before deployment.

Core Features & Use Cases

  • Diff Analysis: Review changes between code versions to detect security vulnerabilities and logical flaws.
  • Pre-landing Checks: Proactively evaluate code before merge to ensure structural integrity.
  • Use Case: When a developer submits a pull request, you activate this Skill to get a comprehensive report on potential risks and quality issues, saving time on manual reviews.

Quick Start

Use the gstack-review skill to analyze your current pull request diff for potential issues.

Frequently Asked Questions about review

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

FAQPage Schema
How do I analyze pull request diffs for security risks before merging?

Pre-landing code review identifies security risks, logical errors, and structural problems by analyzing code differences before merging. It detects SQL safety issues, trust boundary violations, and conditional side effects to prevent bugs from reaching deployment.

What specific issues can diff analysis detect in a feature branch?

Diff analysis detects SQL safety risks, trust boundary violations, conditional side effects, and structural problems in a feature branch. It evaluates code changes between versions to uncover both security vulnerabilities and logical flaws during the software engineering workflow.

Do I need a local Git repository to run pre-merge checks on my pull request?

Yes, you need a local Git repository and diff data to perform pre-merge checks. The analysis requires local diff data to evaluate code changes and generate a comprehensive report on potential risks and quality issues for your feature or bug fix branches.

What is the best way to automate code review for logical errors and structural problems?

Automating code review for logical errors is best achieved by analyzing pull request diffs for structural problems before landing changes. This approach provides a comprehensive report on potential risks, saving time on manual reviews and ensuring high code quality and safety standards.

Can I use this diff analysis for bug fix branches as well as feature branches?

Yes, you can use diff analysis for both bug fix branches and feature branches. The review workflow supports typical software engineering scenarios handling either type of branch, ensuring high code quality and safety standards are maintained across all pull requests.