Skip to main content
affpapa.org
RU EN
skill CX Codex

scoping-changes — Claude Code skill: scope and install

Keeps a fix tied to the problem that triggered it and makes partial delivery explicit. Use it when a task starts growing or an approved plan needs to be split.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add riekelt/principal-engineer --skill scoping-changes -a claude-code
Open on GitHub

What scoping-changes does

The skill helps size a change to its underlying defect. It treats unrelated improvements as separate work, even when they turn up in the same file. If the same defect appears along another path, that path belongs in the fix too.

When an approved task proves too large, split it into named parts and state what will ship. Record deferred work in a tracker with an owner, or mark it for triage. A blocker on one part should not hold up the parts that can still move forward.

The principal-engineering skill is required. Before adding code, check what the codebase, standard library, platform, and installed dependencies already provide. The owner can change the task’s scope, but separate tasks should remain separate changes.

What it helps with

  • keep a fix focused on its triggering defect
  • move unrelated improvements into separate tracked work
  • split an oversized approved task and name the cut line
  • assign deferred work or flag it for triage
  • continue unblocked work while another part is stalled

Example prompts for the agent

  • Fix the defect wherever else it appears, and leave unrelated refactoring out of this change.
  • Split this approved task into named parts and report what will ship now.
  • Review this diff; track out-of-scope findings separately and address findings within the diff.

How to install scoping-changes

1Skills CLI (Vercel)

npx skills add riekelt/principal-engineer --skill scoping-changes -a claude-code

2Manually: put the files in place

~/.claude/skills/scoping-changes/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/scoping-changes/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about scoping-changes

How do I install scoping-changes in Claude Code?

Run npx skills add riekelt/principal-engineer --skill scoping-changes -a claude-code. The skill file is at ~/.claude/skills/scoping-changes/SKILL.md.

What does scoping-changes do?

It guides agents to match a fix to its cause, separate unrelated improvements, and make partial delivery clear when a task must be divided.

What does scoping-changes require?

It requires the principal-engineering skill.

Similar skills

All skills for Code review and refactoring →
improve-codebase-architecture Matt Pocock This skill scans a codebase for architectural friction, then builds a visual HTML report with refactoring candidates. Use it before a deeper architecture review. 1,163,035installs tdd Matt Pocock Guides the red-green TDD loop: ensures tests are written first, keep them at public interfaces, and avoid coupling to implementation details. 1,141,062installs triage Matt Pocock This skill moves issues and external PRs through triage states, verification, and agent briefs. It fits maintainers managing an issue queue. 990,453installs codebase-design Matt Pocock This skill helps design modules with small interfaces and hidden complexity. Use it when refactoring code, choosing a seam, or making tests easier to write. 850,344installs code-review Matt Pocock Reviews changes from a chosen reference point against repository standards and the originating spec. Use it for a branch, PR, or work in progress. 789,521installs implement Matt Pocock Implements work from a specification or tickets, following a test-driven flow and ending with review and a commit. Use it when a coding task needs a defined delivery routine. 774,700installs

From the same set9

guarding-architecture Enforces system boundaries by turning structural invariants into breaking build tests. Useful when code crosses module limits or adds unwanted cross-package imports. CX Codex +1 18,000installs verifying-before-done An agent skill that forces a check on the changed code's real surface and a pasted verify output before any completion claim goes out. CX Codex +1 17,800installs principal-engineering Enforces core engineering discipline for AI agents: mandates pre-change checkpoints, bans silent error suppression, and requires evidence from real code. CX Codex +1 18,000installs writing-unit-tests Guides an agent through writing or revising unit tests around observable behavior. Useful for flaky tests, confusing cases, and new test coverage. CX Codex +1 17,800installs adding-dependencies This skill helps decide whether a project needs a dependency and how to assess and update it. Use it before adding a package, SDK, or GitHub Action. CX Codex +1 17,700installs operating-safely Sets safety guards for destructive commands, secret handling, and parallel edits. It activates before dangerous operations like deleting data or restarting live processes. CX Codex +1 17,900installs keeping-one-source-of-truth An agent skill that keeps each fact in exactly one place and stops copies from drifting apart. Useful the moment a value begs to be pasted elsewhere. CX Codex +1 17,700installs testing-changes Defines test requirements for code changes, enforcing regression tests for bug fixes, edge-case coverage, and strict checks against empty test diffs. CX Codex +1 17,900installs

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor