skills.rest
aspelldenny
aspelldennyCOMMUNITY
Explore all skills by this author →
GitHub

review

Review code diffs for logic errors, security holes, and performance regressions before merging.

Updated Apr 4, 2026
Search Tags:#security#quality#code-review#ci#bug-detection#pre-merge
One-click install
npx skills add https://github.com/aspelldenny/sos-kit --skill review-aspelldenny
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/aspelldenny/sos-kit/tree/main/skills/attic/review
Command: npx skills add https://github.com/aspelldenny/sos-kit --skill review-aspelldenny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-merge code review — find bugs that CI misses — logic errors, security holes, performance regressions, and missing edge cases.

Core Features & Use Cases

  • Systematic diff analysis and risk assessment before merging.
  • Stepwise review guidance covering scope understanding, critical checks, and quality gates.
  • Use Case: before merging a feature branch, run a structured review to surface potential issues and ensure compliance with the project's quality standards.

Quick Start

Run a pre-merge review by inspecting the diff and applying the security, data-safety, and logic checks before shipping.

Frequently Asked Questions about review

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

FAQPage Schema
How do I catch logic errors and security holes that CI misses before merging a pull request?▼

Perform a pre-merge code review to catch bugs that CI misses by applying a structured checklist to your pull request diff. This surfaces logic errors, security holes, and performance regressions before merging.

What is the best way to run a structured pre-merge code review on a feature branch?▼

Run a structured pre-merge code review by inspecting the feature branch diff and applying security, data-safety, and logic checks. This stepwise process ensures compliance with quality standards before shipping.

Does pre-merge code review work for hotfixes and performance regressions?▼

Pre-merge code review works across feature branches, pull requests, and hotfixes to surface performance regressions. It enforces quality gates and blocking criteria to prevent problematic code from merging.

How do I enforce quality gates and blocking criteria during a code review?▼

Enforce quality gates and blocking criteria during code review by applying a stepwise checklist covering scope understanding and critical checks. This process identifies missing edge cases and provides non-blocking improvement suggestions.

Why does CI pass but my code still has hidden bugs and missing edge cases?▼

CI passes but hidden bugs remain because CI often misses logic errors, security holes, and missing edge cases. A pre-merge code review applies a structured checklist to surface these issues before merging.

Related Skills

Explore More Software Engineering Skills→
edobryedobry
6

review-pr

Analyze pull requests and post structured GitHub PR reviews.

Community
Advanced
ibalasiteibalasite

land-and-deploy

Merge pull requests, wait for CI, and verify production health via canary checks.

Community
Advanced
LuisSambranoLuisSambrano
7

code-review

Perform systematic code review and static analysis across multiple programming languages.

Community
Advanced
nazrulsoftwaredevnazrulsoftwaredev

ai-regression-testing

Automates AI-assisted regression testing for API routes and sandbox/production parity using Vitest and mock-based architecture.

Community
Advanced