review-scope

Classifies code changes as minor or major to determine the appropriate code review scope.

Updated Jan 1, 2026
One-click install
npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill review-scope-sarkarshivaditya-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-scope
Source: https://github.com/sarkarshivaditya-lab/WellMate/tree/main/.engineering-skills/troykelly-claude-skills/skills/review-scope
Command: npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill review-scope-sarkarshivaditya-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often waste effort reviewing too much code for trivial changes or miss critical issues by reviewing too little for large changes. This Skill classifies a change as minor or major so reviewers know exactly which code, callers, and integration points to examine. ## Core Features & Use Cases - Change Classification: Uses file count, API changes, and behavioral impact indicators to classify changes as minor (review new code only) or major (review impacted code too). - Impact Analysis Guidance: Provides grep-based techniques to find callers, dependencies, and call chains affected by changed code. - Scope Documentation Templates: Supplies ready-to-use markdown templates and checklists for documenting review scope before starting. - Use Case: Before reviewing a pull request that touches the authentication flow across five files, use this Skill to classify it as major and generate a checklist covering all callers, integration points, and end-to-end flows. ## Quick Start Ask the AI to determine whether the current change is minor or major and define the review scope before starting the code review.

Frequently Asked Questions about review-scope

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

FAQPage Schema
How do I determine the scope of a code review?▼

Classify the change as minor or major based on file count, API changes, and behavioral impact. Minor changes require reviewing only new code, while major changes require reviewing all impacted callers, callees, and integration points.

What is the difference between a minor and major code change?▼

A minor change touches 1-3 files with isolated, internal modifications and no API or dependency changes. A major change spans 4+ files, modifies public APIs, adds dependencies, or alters existing behavior across modules.

How do I find code impacted by a change?▼

Use grep to find all files importing the changed module and all usages of changed functions. Then trace the call chain upward to callers and downward to callees to identify the full impact surface.

What should I do when unsure if a change is minor or major?▼

Default to treating it as a major change. Over-reviewing is safer than missing issues, especially for small changes with wide behavioral impact such as modifying shared constants or default values.

Does a large refactor always require a full behavioral review?▼

No. A large refactor with no behavior change, such as renaming a variable across many files, is still classified as major for structural review, but the behavioral review portion can be lighter.