code-scrutiny

Review recent code changes to surface bugs and refactoring opportunities.

1|Updated Apr 8, 2026

Search Tags:#git #refactoring #review #static-analysis #code-review #bug-detection #diff-analysis

Ready to run

npx skills add https://github.com/maxenko/claude-skills --skill code-scrutiny

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-scrutiny
Source: https://github.com/maxenko/claude-skills/tree/main/code-scrutiny
Command: npx skills add https://github.com/maxenko/claude-skills --skill code-scrutiny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep code review of recent codebase changes to surface bugs, quality issues, and refactoring opportunities.

Core Features & Use Cases

Thoroughly examine diffs across commits and uncommitted changes to surface defects.
Detect inconsistencies in comments, duplicated logic, and potential refactoring targets.
Provide structured feedback that can be applied during code reviews, audits, or self-checks.

Quick Start

Provide a scope (files or commit range) or review all uncommitted changes to start the analysis.

Frequently Asked Questions about code-scrutiny

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

FAQPage Schema

How do I perform a deep code review on recent git commits?▼

You can review uncommitted changes by providing a file scope or letting the Skill analyze the entire working directory. It gathers repository state using Bash, Grep, and Read to surface defects and refactoring targets in your modified files.

What is multi-pass diff analysis for bug detection?▼

Multi-pass diff analysis is a technique that repeatedly examines code changes to identify inconsistencies, duplicated logic, and potential bugs. It critiques recent modifications across multiple files to provide structured, actionable feedback.

Can I use static analysis to find refactoring targets in a pull request?▼

Yes, you can use static analysis to find refactoring targets in a pull request by running the Skill against the specific commit range. It detects duplicated logic and quality issues to provide structured feedback for your code review.

Do I need to specify files to review uncommitted changes?▼

No, you do not need to specify files to review uncommitted changes. You can simply instruct the analysis to cover all uncommitted modifications, and it will automatically gather and analyze the repository state.

What is the best way to automate code review for uncommitted changes?▼

The best way to automate code review for uncommitted changes is to run a multi-pass analysis tool that reads git diffs and repository state. This surfaces defects and refactoring opportunities without requiring manual file comparisons.