skills.rest
wangfeiv
wangfeivCOMMUNITY
Explore all skills by this author →
GitHub

review

Analyze code diffs against mainline branches for SQL safety, concurrency, and trust boundaries.

Updated Oct 29, 2013
Search Tags:#diff analysis#code review#security#concurrency#pre-merge
One-click install
npx skills add https://github.com/wangfeiv/GitProjects --skill review-wangfeiv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/wangfeiv/GitProjects/tree/main/skills/gstack/review
Command: npx skills add https://github.com/wangfeiv/GitProjects --skill review-wangfeiv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers and reviewers automatically analyze code differences to identify potential structural issues, security risks, and code quality problems before merging.

Core Features & Use Cases

  • Automated Diff Analysis: Compares code changes against the main branch to detect SQL injection risks, trust boundary violations, and structural bugs.
  • Pre-Landing Checklist: Guides users through a comprehensive review process, highlighting critical issues such as data safety and concurrency concerns.
  • Use Case: A team wants to ensure their new code does not introduce SQL vulnerabilities or concurrency problems before merging into production. This Skill automates that process, reducing manual oversight.

Quick Start

Run the review workflow on your current branch to automatically check for issues and receive actionable feedback.

Frequently Asked Questions about review

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

FAQPage Schema
How do I check code diffs for security and concurrency issues before a pull request lands?▼

Automated diff analysis identifies SQL injection risks, concurrency concerns, and trust boundary violations by comparing code changes against the mainline branch before landing. It guides you through a pre-merge checklist to ensure data safety and code consistency.

What is the best way to automate a pre-merge code review for structural bugs?▼

The best way to automate a pre-merge code review for structural bugs is to analyze code differences against the main branch. This approach detects SQL safety issues, trust boundary violations, and concurrency problems with minimal manual oversight required.

Can I detect SQL injection risks and trust boundary violations in my code changes automatically?▼

Yes, you can detect SQL injection risks and trust boundary violations automatically by running a diff analysis workflow on your current branch. The review process evaluates all files involved in the change to ensure code meets safety standards.

How does pre-landing diff analysis handle code consistency across multiple changed files?▼

Pre-landing diff analysis handles code consistency by evaluating all files involved in a change against the mainline branch. It checks for structural issues, data safety, and concurrency concerns to ensure comprehensive quality standards are met before merging.

When do I need to run an automated code review before merging into production?▼

You need to run an automated code review before merging into production when you want to ensure new code does not introduce SQL vulnerabilities or concurrency problems. It provides actionable feedback on structural issues and security risks prior to PR landing.

Related Skills

Explore More Software Engineering Skills→
prince-appiahprince-appiah

find-bugs

Identify bugs, security vulnerabilities, and code quality issues in branch diffs.

Community
Advanced
nikhilsitaramnikhilsitaram
89

pr-merge

Merge reviewed GitHub pull requests and clean up branches and worktrees.

Community
Advanced
JylhisJylhis
1

golang-security

Detect Go vulnerabilities using govulncheck, static analysis, and DREAD scoring.

Community
Advanced
konflux-cikonflux-ci
1

code-review

Evaluate code changes for correctness, security, and style adherence.

Official
Advanced