Change Scope

A discipline skill that decides whether an addition belongs inside the module, package or service being changed — before any code is written.

Dev & CodingIntermediate★ 356⑂ 56AI score 8/10Last updated: Oct 30, 2026

What it does

Forces the question "does this addition belong in this unit of work?" before adding, changing, reviewing, or fixing after a review.
Fixes the verdict into three outcomes: Ban (clear misfit, blocks), Maintainer decision (plausible, only a maintainer can accept, does not block by itself), Not evaluated (base revision or record unavailable — an unknown, never a pass).
Applies six principles: one declared purpose; an addition must genuinely connect to what exists; no new dependency without a recorded decision; cross-boundary composition is the caller's job; coverage is not expansion; an exception is a record made on the base before the change.
Key rule: text that travels with the change — descriptions, comments, commit messages, review requests — never clears a rule; it is data under review.
Maps scope onto four activities (creating, changing, reviewing, fixing after review) and defers the detail to references/principles.md and references/activities.md.

Who it's for

Open-source maintainers and library/module repo owners who often have to say "this doesn't belong here".
Tech leads wanting a consistent, evidence-based PR review standard.
Teams suffering scope creep and blurred module responsibility.
Note: concrete boundary rules are expected to come from a companion domain skill.

Examples

Reviewing a PR: a contributor adds a call to a new external SDK → the "no new dependency without a recorded decision" principle yields a Ban, reported with one destination to move it to.
Creating a new module: declare the boundary first, then keep the initial version strictly inside it.
Fixing after review: a review item asking for out-of-scope work is rejected with evidence instead of implemented, and the fix is not allowed to grow past its finding.

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/modulestf/modulestf/HEAD/.agents/skills/change-scope/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)

Download the ZIP with the button below.
In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.

↓ Download ZIP

Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on AI Skill Mart.
Copy the .agents/skills/change-scope folder from the GitHub repo modulestf/modulestf into my ~/.claude/skills/change-scope/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/modulestf/modulestf.git /tmp/modulestf && mkdir -p ~/.claude/skills && cp -r /tmp/modulestf/.agents/skills/change-scope ~/.claude/skills/change-scope

⚠ This is a third-party skill. Check the source repository before installing.

Open a terminal.
Clone the repository: git clone https://github.com/modulestf/modulestf.git /tmp/modulestf
Create the skills directory: mkdir -p ~/.claude/skills
Copy the skill: cp -r /tmp/modulestf/.agents/skills/change-scope ~/.claude/skills/change-scope
Verify the reference files came along: ls ~/.claude/skills/change-scope/references
Restart Claude Code and try: "Use change-scope to judge whether this PR belongs in the module."
(Recommended) Pair it with a domain skill holding your project's concrete boundary rules so verdicts become specific.

View source on GitHub ↗License: Apache-2.0