review

Review branch changes for code quality, correctness, and cleanup before merge.

1|Updated Apr 22, 2026

Search Tags:#quality assurance #code review #refactoring #edge cases #cleanup #branch analysis #rule compliance

Ready to run

npx skills add https://github.com/AbsolutSystems/absolutpowers --skill review-absolutsystems

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/AbsolutSystems/absolutpowers/tree/main/claude/skills/review
Command: npx skills add https://github.com/AbsolutSystems/absolutpowers --skill review-absolutsystems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill performs a full review of branch changes so you can catch logic bugs, edge cases, rule violations, and leftover code before a merge.

Core Features & Use Cases

Semantic Analysis: Explains how changed functions, methods, and components alter behavior and where the blast radius reaches.
Edge Case Hunting: Checks risky inputs, missing error handling, off-by-one mistakes, and other failure paths that could break production behavior.
Rules and Memory Checks: Verifies the diff against project rules and uses project memory to sharpen the review with recurring lessons.
Garbage Collection: Finds unused code, debug output, commented-out fragments, and other cleanup items across the full changed files.

Quick Start

Ask the assistant to review my current branch against the default base and produce a full four-phase code review report.

Frequently Asked Questions about review

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

FAQPage Schema

How do I catch edge cases and logic bugs in my branch before merge?▼

To catch edge cases and logic bugs before merge, perform a full diff-based code review that analyzes risky inputs, missing error handling, and off-by-one mistakes across modified files. This semantic analysis detects failure paths that could break production behavior.

How do I check my code changes against project rules and memory context?▼

Verify code changes against project rules and memory context by applying a compliance check during your branch review. This uses recurring project lessons to sharpen the review and ensures modified files adhere to established repository conventions.

What is the best way to find unused code and debug output in modified files?▼

The best way to find unused code and debug output is garbage collection analysis across changed files. This cleanup process identifies commented-out fragments, leftover code, and debug statements before you merge the branch.

Can I review branch changes for both correctness and cleanup at the same time?▼

Yes, you can review branch changes for correctness and cleanup simultaneously through a four-phase code review. This process combines semantic analysis, edge case hunting, rules compliance, and garbage collection into a single comprehensive report.

Does semantic code analysis explain the blast radius of modified functions?▼

Yes, semantic code analysis explains the blast radius of modified functions by detailing how changed methods and components alter behavior. This inspection highlights exactly where the impact of your branch changes reaches within the project.

When do I need a full diff-based inspection of my branch?▼

You need a full diff-based inspection of your branch when you want to catch logic bugs, edge cases, rule violations, and leftover code before a merge. This review ensures code quality and correctness prior to integration.