scope-check

Name: scope-check
Availability: InStock
Author: ChazzCoin

Scan repositories to count touched files, modules, tests, and public API surfaces.

Updated Apr 28, 2026

Search Tags:#drift #report #code-scan #phasing #scope-check #surface-area

Ready to run

npx skills add https://github.com/ChazzCoin/claude-kit --skill scope-check-chazzcoin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scope-check
Source: https://github.com/ChazzCoin/claude-kit/tree/main/kit/skills/scope-check
Command: npx skills add https://github.com/ChazzCoin/claude-kit --skill scope-check-chazzcoin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scan and quantify the true surface area of planned changes by tallying touched files, modules, tests, type/interface references, and public API impact, so teams can calibrate scope accurately.

Core Features & Use Cases

Surface area measurement: files touched, modules affected, symbols impacted, tests, docs references.
Drift assessment and rechunking: compare estimates against measured scope and suggest phased work.
Output reporting: writes a docs/scope/<date>-<slug>.md report with counts and insights for retrospective.

Quick Start

Trigger scope-check on a planned change to generate a scope report.

Frequently Asked Questions about scope-check

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

FAQPage Schema

How do I measure the true surface area of a planned code change before starting development?▼

Repository scope assessment works by scanning the codebase to quantify affected files, modules, tests, and public API surfaces. It outputs a detailed scope report with a drift verdict and optional rechunking notes to guide architecture planning decisions.

How do I check if a planned migration or refactor scope has drifted from the original estimate?▼

A scope drift assessment compares your planned change estimates against actual measured surface area counts. It outputs a drift verdict and rechunking notes under docs/scope to help calibrate scope accurately before coding begins.

Can I evaluate PR scoping and public API impact for multi-module repositories?▼

Evaluating PR scoping across multi-module repositories involves scanning public API surfaces and counting impacted symbols and tests. This quantifies the true scope of planned changes from small refactors to large migrations, aiding accurate PR calibration.

What is the best way to generate a retrospective report for architectural planning and code scanning?▼

Generating a retrospective scope report requires scanning the repository to tally affected files, modules, tests, and API surfaces. It writes a dated markdown report with counts and insights under docs/scope to calibrate future team planning accurately.

When do I need a scope check and rechunking notes for planned repository changes?▼

A scope check is needed before coding planned changes like large migrations or small refactors to measure true surface area. It provides a drift verdict and rechunking notes to suggest phased work, preventing scope creep in multi-module repositories.

Does scope-check require any specific dependencies or components to scan repository surface area?▼

Scanning repository surface area requires no external dependencies or components to function. It independently quantifies touched files, modules, and public API impact, outputting a counts-based scope report with a drift verdict directly under docs/scope.