Scan repositories to count touched files, modules, tests, and public API surfaces.
npx skills add https://github.com/ChazzCoin/claude-kit --skill scope-check-chazzcoin
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
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.
Trigger scope-check on a planned change to generate a scope report.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
JuanTaco4YouPlan software changes that preserve baseline behavior with minimal file diffs.
kirich1409Coordinate parallel expert investigations into a review-ready research report.
jassicsReview Infrastructure-as-Code for security misconfigurations across Terraform, CloudFormation, ARM/Bicep, Pulumi, Ansible, and Helm.
sncollectiveIdentify code duplication, complexity, and pattern drift in a codebase.
