mcpField
C
changeset

changeset

github.com/venhdevDevelopment1140 installsUpdated today
Repository

About changeset

changeset is a skill for planning the file impact of a settled software direction. It inspects relevant code and contracts, maps required changes and cascades, then presents a staged changeset without modifying files.

Key features

  1. 01Traces callers and dependencies
  2. 02Identifies direct and indirect cascades
  3. 03Plans create, move, update, and delete actions
  4. 04Flags stale or conflicting plans
  5. 05Produces a staged file tree

Use cases

  1. 01Mapping code changes before implementation
  2. 02Finding tests affected by a solution
  3. 03Checking whether an implementation plan is stale

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/venhdev/zenforge --skill changeset

After installing, type/changesetin Claude Code to confirm it loaded.

Details

From the project README

changeset — File Impact & Cascade Planning

Domain Rubric

Input & Boundary

Receive a settled direction or solution with outcome, constraints, and available evidence. Ground it against the current checkout and governing contracts; keep planning read-only and preserve the supplied direction.

Trace direct and indirect callers, implementations, imports, schemas, and tests. Inspect only the target and load-bearing cascades; exclude cosmetic churn, speculative files, and unaffected backward-compatible callers. Prune superseded logic: stage explicit removal of dead helpers, obsolete branches, and tests invalidated by the solution. Stop if the input plan is stale or contradictory rather than silently redesigning it.

File Actions
  • [CREATE]: New file required by the solution.
  • [MOVE]: Relocation or rename, including affected references.
  • [UPDATE]: Existing logic, contract, test, or necessary cascade.
  • [DELETE]: Obsolete file whose removal is required by the solution.
State
  • STAGED: The Changeset Tree identifies concrete operations and necessary cascades for the settled direction.
  • UNRESOLVED: Missing, stale, or conflicting direction prevents a reliable changeset; cite the blocker and decision required.

Canonical Output Contract

# Changeset: <Scope> · STAGED

Basis: <Settled solution and supporting proof/reference.>
Acceptance: <Observable criteria and constraints to carry downstream.>

```text
|-- <subsystem>/
|   |-- <file>
|   |   `-- [UPDATE] <Load-bearing change and invariant>.
|   `-- <new-file>
|       `-- [CREATE] <Required component or regression check>.
`-- <deep/path/to/caller>
    `-- [UPDATE] <Necessary cascade>.

Summary: <N> files affected (<C> created, <U> updated, <M> moved, <D> deleted).
```

For UNRESOLVED, replace the tree with a concise blocker, evidence, and required redesign decision; omit invented file operations.

Routing
  • An outdated plan exposes unresolved requirements → (via /clarify).
  • An outdated plan requires a new design direction → (via /architect-decision).
  • The supported changeset is authorized for implementation → (via /forge).
  • The caller wants task decomposition into verifiable slices → (via /split-tasks).
  • The caller wants backlog persistence or issue tracking → (via /track-tasks).

Execution Protocol

  1. Inspect the supplied direction and current code/contracts. Stop on an outdated plan or foundational contradiction and report UNRESOLVED with the required redesign decision.
  2. Build the tree with file actions, direct cascades, acceptance criteria, and evidence provenance. Collapse redundant directories while preserving file hierarchy.
  3. Present STAGED and halt without filesystem mutations. An embedded changeset produced elsewhere uses the same handoff obligations without requiring this skill.

Comments

Markdown supported