JSPM

Note: this package is in an early alpha. Any bugs can be submitted as GitHub issues

A toolkit for tracking and visualizing AI-assisted code changes with structured reasoning, known as logical changes.

What is a "Logical Change"?

A logical change is a group of code modifications that serve a single purpose. A single commit often contains multiple logical changes - for example, adding a feature might involve:

• Adding a new component (logical change #1)
• Updating the router to include it (logical change #2)
• Adding styles (logical change #3)

Traditional diffs show these as a flat list of file changes, making it hard to understand which parts go together. Codewalk groups related hunks across files by their shared reasoning, so reviewers see changes organized by intent rather than by file path.

Visualizer

Interactive TUI for viewing logical changes on the current branch:

npx codewalk visualize   # or viz

or

bunx codewalk visualize   # or viz

Groups all changes by their reasoning text across commits, sorted chronologically (oldest first). Shows the current branch, tracking directory, and actual diff hunks.

Claude Code Plugin

Installation

/plugin marketplace add lukecrum/codewalk

/plugin install codewalk

Once installed, Claude will automatically create tracking files for every commit via a stop hook that enforces tracking before session exit.

Configuration

Run the interactive configuration wizard:

/codewalk-config

Or manually create .claude/codewalk.local.md:

---
storage: global
globalDir: ~/.codewalk
---

Settings

Storage Modes

Global storage (storage: global) - Default:

• Tracking files stored in <~ or path>/.codewalk/<repo-name>/<hash>.json
• Best for: Personal tracking without adding files to the repo

Local storage (storage: local):

• Tracking files stored in .codewalk/<hash>.json in the project
• Best for: Projects where team visibility of tracking data is important

Appendix A - Tracking files

Schema

type Changeset = {
  // Git commit SHA this changeset describes
  commit: string;

  // List of logical changes, each with its own reasoning
  changes: Change[];
};

type Change = {
  // Human-readable explanation of why this change was made.
  // Should explain the intent, not just describe what changed.
  reasoning: string;

  // Files affected by this logical change
  files: FileChange[];
};

type FileChange = {
  // Path to the file, relative to repo root
  path: string;

  // Which hunks from `git show <commit>` belong to this change.
  // 1-indexed, in order of appearance in the diff.
  hunks: number[];
};

Example

{
  "commit": "a1b2c3d",
  "changes": [
    {
      "reasoning": "Add dark mode toggle that persists to localStorage",
      "files": [
        { "path": "src/App.tsx", "hunks": [1, 2] },
        { "path": "src/styles.css", "hunks": [1] }
      ]
    }
  ]
}

Appendix B - Visualizer controls