skills.rest
allen-hsu
allen-hsuCOMMUNITY
Explore all skills by this author →
GitHub

reviewing-code

Identify critical issues in repository diffs against the base branch.

1|Updated Dec 31, 2025
Search Tags:#auto-fix#code-review#pr-review#diff-analysis#two-pass-review#sql-safety#llm-trust
One-click install
npx skills add https://github.com/allen-hsu/agent-arsenal --skill reviewing-code-allen-hsu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reviewing-code
Source: https://github.com/allen-hsu/agent-arsenal/tree/main/plugins/engineering-core/skills/reviewing-code
Command: npx skills add https://github.com/allen-hsu/agent-arsenal --skill reviewing-code-allen-hsu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR reviews that catch structural issues before merging, reducing risk and bug surface.

Core Features & Use Cases

  • Detects SQL safety issues, LLM trust boundary problems, race conditions, and conditional side effects in diffs.
  • Performs a two-pass review (critical then informational) with fix-first methodology.
  • Guides engineers to verify changes before shipping and to assess scope drift and requirement coverage.

Quick Start

Run the pre-landing review on the current diff to surface critical issues and recommended fixes.

Frequently Asked Questions about reviewing-code

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

FAQPage Schema
How do I catch race conditions and SQL safety issues in a PR review?▼

Pre-landing PR review analyzes your repository diff against the base branch to detect critical race conditions and SQL safety issues. It also operates across LLM trust boundaries and conditional side effects to surface actionable findings.

What is a two-pass review methodology for diffs?▼

A two-pass review evaluates code changes sequentially, first identifying critical issues and then reviewing informational findings. This fix-first methodology guides engineers to verify changes and assess scope drift before shipping.

How do I review LLM trust boundaries and conditional side effects before merging?▼

Pre-landing reviews evaluate LLM trust boundaries and conditional side effects by classifying findings from the repository diff. This process guides remediation to verify changes and assess requirement coverage before shipping.

Can I use diff analysis to guide auto-fixes for pre-landing code reviews?▼

Yes, diff analysis classifies findings against a review checklist to guide auto-fixes. By evaluating the repository diff and base branch, it provides actionable remediation steps for structural issues.

What do I need to provide to run a pre-landing PR review on my changes?▼

You need to provide the repository diff, the base branch, and a review checklist. The review uses these inputs to classify findings and guide remediation for scope drift and requirement coverage.

Related Skills

Explore More Software Engineering Skills→
AkbarDevopAkbarDevop

review

Identify production-risk findings in a code diff before merging.

Community
Advanced
trailofbitstrailofbits
6.5k

fix-review

Map security audit findings to commits and rate fix quality.

Official
Advanced
bennybennisonbennybennison

verification-loop

Run sequential build, type, lint, test, security, and diff checks.

Community
Intermediate
Serg28Serg28

security-reviewer

Automate security audits with semgrep, trivy, gitleaks, and dependency scanners.

Community
Intermediate