What problem does it solve?
Developers often open pull requests where a small fix has grown to touch unrelated files, dependencies, or subsystems, making reviews slow and risky. This Skill compares a git diff against a one-line intent and surfaces the paths, dependencies, API renames, config edits, oversized hunks, and formatting-only files that drifted away from the stated goal.
Core Features & Use Cases
- Intent-based diff classification: Tokenizes the stated intent and changed paths to separate in-scope edits from likely creep.
- Dependency and API rename detection: Parses requirements.txt, package.json, and pyproject.toml for new dependencies, and flags nearby removed and added public function or class declarations as renames.
- Config, CI, and build awareness: Identifies edits to .github, Dockerfile, Makefile, and YAML or TOML files that often hide cross-cutting changes.
- Use Case: Before opening a PR titled "fix null deref in parser", run the detector to confirm the diff only touches parser files and not CI config, lockfiles, or unrelated subsystems.
Quick Start
Ask the agent to run the scope creep detector on my staged changes against the intent of fixing the parser crash.