change-scope
From the author
Decide whether an addition belongs in the thing being changed at all, for any language, project or task. Use before adding, changing, reviewing or fixing anything - creating a feature or a new unit, changing an existing one, reviewing a change, or fixing code after a review. Domain skills supply the concrete boundary rules; this skill supplies the concept, the outcomes and how each activity applies them.
Install
npx skills add modulestf/modulestf --skill change-scope -a claude-code
Installs to .claude/skills/change-scope/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 86
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- scopesuboss87/FDEOpsAssess a new customer request against agreed scope, trade-offs and ownership. Use when an engagement expands or a custom feature needs a commitment decision.Other★ 856
- fable-scope-disciplineDizzyMii/fable-skillsUse when implementing any change in existing code — when tempted to clean up nearby code, add unrequested validation or options, fix something "arguably in scope", or when the diff is growing past what was asked.Engineering★ 56
- refinewellwelwel/laguneConfronts a scope with the engineering, testing, and writer skills, each where it applies, and with the architecture a long-lived project needs, then brings it into line. It removes what should not exist, simplifies, decouples, sharpens responsibilities and names, and places files and directories where they belong. The scope is the unstaged, staged, or current work, commits, a branch, paths, a focus, or the whole workspace, named in any language.Testing★ 173
- scoped-changescarletkc/agentsJudgment rules for locating the correct boundary of a requested change: staying inert outside it while completing every required site inside it. Use when scope is ambiguous, a diff touches neighboring surfaces, required dependent edits are unclear, or a proposed compatibility layer, migration, fallback, flag, abstraction, or parallel implementation may exceed the request.Writing★ 227
- change-impact-analysisnaodeng/awesome-qa-skillsUse this skill when you need to analyze how a code, configuration, or requirement change affects quality scope; triggers include 变更影响分析 and change impact analysis.Planning★ 297
- review-codeavibebuilder/claude-primeReview code for quality, correctness, and fit. Use when the user wants judgment on code that already exists — their own changes, a teammate's patch, a PR, branch, commit, diff, staged changes, or one or more files to look over. Activate on requests like review, look over, sanity check, critique, code review, or 'is this good?' The key signal is that the user wants evaluation of existing code and its tradeoffs, not implementation, debugging, or explanation. This skill works independently, but when plans, specs, task artifacts, or prior discussion exist, use them to understand why the code exists before judging it.Engineering★ 120
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in