Agent skill · software engineering · shubhamsaboo
scope-creep-detector
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad pull requests, changes that grew beyond a fix, dependency additions, public API renames, config or CI edits, oversized hunks, and formatting-only files. Use when the user asks whether a change grew beyond the fix, a PR is too broad, or what unrelated stuff they touched, and wants keep, split, or justify guidance. Operates locally and offline.
Why this skill is useful
Adds a Python script that automates the detection of scope creep in git diffs, providing actionable insights that the AI cannot generate on its own.
What it needs
Requires python3 installed locally. About 3k tokens when loaded. Last updated 2026-08-03. 131,141 stars on the source repository.
What this skill does
Scope Creep Detector A one-line fix should not require a reviewer to reverse-engineer fourteen files across three subsystems. This skill compares a git diff with its stated intent, surfaces scope signals, and turns them into keep, split, or justify decisions. Everything runs locally. The script makes no network calls and does not change the working tree, index, commits, or branches. When to use Before opening a pull request whose diff may have grown beyond its intent When a bug fix touches unexpected files or subsystems When the user asks whether staged changes are too broad When a diff includes dependency, public API, config, CI, or build changes When the user wants a concrete split plan for a mixed change When not to use Formatting code, running a linter, or writing a commit message Reviewing correctness, security, or test quality inside an agreed scope Measuring historical project growth across many commits Editing or reverting files without the user's approval Establish the intent Use the user's one-line intent when available. Keep it concrete, such as fix null dereference in parser or add retry limit to webhook delivery. If no intent was given, the script falls back to the current branch name. If that name is generic, detached, or unrelated to the work, ask for one line of intent before treating relatedness as meaningful. Run the classifier Run from this skill directory and point --repo at the target repository. Working tree diff: Staged diff: Branch diff against a merge base: Saved diff or stdin: Use --hunk-threshold only when the repository has a documented reason to change the default churn threshold. Do not tune the threshold merely to make a warning disappear. Interpret the JSON Read references/scope-signals.md before making a recommendation. Treat the classifier as triage evidence, not proof of authorial intent. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills shubhamsaboo/scope-creep-detector