scope-creep-detector

A skill in Shubhamsaboo/awesome-llm-apps · 145,077 stars on GitHub

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.

Security grade of this SKILL.md: SAFE · how we grade

How to install scope-creep-detector

npx skills add Shubhamsaboo/awesome-llm-apps --skill scope-creep-detector -a claude-code

The skills CLI copies this one skill into Claude Code (use -a for another agent). Or read its SKILL.md on GitHub.

What the SKILL.md says

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. 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. 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.

Other skills in Shubhamsaboo/awesome-llm-apps

  • advisor-orchestrator-worker Use when a task is too large for one model pass, needs parallel research or generation across many subtasks (like researching a dozen compe…
  • commit-archaeologist Reconstructs why code exists from local git history, including the introducing commit, later changes, current authors, repeated companion f…
  • dependency-doctor Checks requirements.txt, pyproject.toml, and package.json dependency manifests for surface-level direct-dependency footguns: standard-libra…
  • first-reader Beta readers for any draft, run by simulating how a real reader experiences it, moment by moment. A skim gate, a no-lookahead timed read pr…
  • project-graveyard Scans the developer's machine for dead side projects, autopsies each one from its git history (died at the payments wall, killed by a newer…
  • thinking-out-loud A contract for what the agent does when a long, messy, stream-of-consciousness ramble arrives (usually voice dictation): act on nothing unt…