How does this skill distinguish between minor and major changes?

It uses a logical decision flow evaluating the number of files changed (typically >3), whether public APIs were modified, and if there are significant behavioral changes in the system.

Can it help find code affected by my changes?

Yes, it includes specific strategies and grep patterns to identify callers, dependencies, and integration points that may be impacted by major changes.

Why should I use this before starting a code review?

It ensures you don't miss regressions in high-impact areas while keeping the review process fast and efficient for small, isolated updates.

What happens if the scope of a change is ambiguous?

The skill follows a safety-first principle: if you are uncertain whether a change is minor or major, it defaults to a Major scope to ensure maximum code quality.

Review Scope Manager

Name: Review Scope Manager
Author: troykelly

bytroykelly

Collaboration Tools

Evaluates the complexity and impact of code changes to determine the appropriate depth for code reviews.

About

The Review Scope skill automates the assessment of code changes within Claude Code, classifying updates as either minor or major based on file count, API modifications, and behavioral impact. It provides a structured decision flow and specific checklists for each scope, ensuring that high-impact changes receive a thorough review of both new and dependent code, while localized updates remain efficient. By identifying callers, dependencies, and integration points, this skill helps developers maintain high code quality and prevent regressions in complex systems.

Key Features

0 GitHub stars
Automated classification of minor vs. major code changes
Impact analysis to identify callers and downstream dependencies
Standardized scope documentation for PR communication
Customized review checklists for different change magnitudes
Structured decision flow based on file count and API impact

Use Cases

Determining whether to review only new lines or the entire call chain during a pull request
Optimizing review time for small bug fixes and internal implementation changes
Identifying impacted modules and integration points for architectural refactors

About

Key Features

0 GitHub stars
Automated classification of minor vs. major code changes
Impact analysis to identify callers and downstream dependencies
Standardized scope documentation for PR communication
Customized review checklists for different change magnitudes
Structured decision flow based on file count and API impact

Use Cases

Determining whether to review only new lines or the entire call chain during a pull request
Optimizing review time for small bug fixes and internal implementation changes
Identifying impacted modules and integration points for architectural refactors