code-review-session

Identify and prioritize issues in code diffs for pre-merge reviews.

Updated Apr 24, 2026

Search Tags:#checklist #security #quality #review #diff #code #pull-request

Ready to run

npx skills add https://github.com/SpencerGoss/agent-engineering --skill code-review-session

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review-session
Source: https://github.com/SpencerGoss/agent-engineering/tree/main/code-review-session
Command: npx skills add https://github.com/SpencerGoss/agent-engineering --skill code-review-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams ensure that code changes are reviewed efficiently by focusing on diffs, surfacing critical issues, and guiding reviewers through a deterministic checklist to improve merge safety and code quality.

Core Features & Use Cases

Review only the changed code in diffs (git diff / git diff --staged).
Produce a severity-ranked finding list (CRITICAL, HIGH, MEDIUM, LOW) and a concise remediation path.
Enforce a structured pre-merge review workflow with a built-in adversarial check to challenge assumptions and catch edge cases.

Quick Start

Review the current git diff to produce a prioritized, structured review report that you can act on before merging.

Frequently Asked Questions about code-review-session

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

FAQPage Schema

How do I review only the changed code in a git diff before merging?▼

Pre-commit code review focuses on diffs to prevent faulty commits by scrutinizing only the changed code. It surfaces critical issues in pull requests using a deterministic checklist and severity-based findings.

What is the best way to prioritize code review findings for a pull request?▼

Code review findings are prioritized by severity levels like CRITICAL, HIGH, MEDIUM, and LOW. This ranking guides reviewers through a structured pre-merge workflow to address the most impactful bugs first.

How does an adversarial check catch edge cases during a code review?▼

An adversarial check challenges assumptions during pre-merge reviews to catch edge cases. It enforces a structured workflow that tests the durability of code changes before they are merged.

Can I automate pre-merge code reviews for feature work?▼

Pre-merge code reviews produce a standardized output suitable for both human reviewers and automation. This allows you to automate checks on diffs during feature work and pull requests.

Does code review on staged diffs improve merge safety?▼

Reviewing staged diffs improves merge safety by applying a deterministic checklist to identify issues. It provides a concise remediation path that guides reviewers through the changed code efficiently.