Claude Code mod

changes-drill

A Changes pane that says which turn changed each file and who (Claude, a subagent, Claude's shell or you), against HEAD, the session's start, the last turn or the base branch; with a guard for sensitive or out-of-scope files, a hunk peek, and a History section (what happened lately, in sentences or as a files tree) with a Branches button that opens branch-drill's pane (your branch against main, every branch as lanes or a subway map). Read-only: it changes nothing in the repository. No model calls, no tokens and no network: local git only, read while the pane is up. Opened by /changes-drill, or by $.changesDrill.open() from another mod (motta-statusline's files).

Pane & dashboard mods Plugin marketplaceValidates on Claude Code 2.1.326 Source

Install

Inside Claude Code
/plugin marketplace add l-a-motta/motta-claude-mods
/plugin install changes-drill@motta-claude-mods

Mods install like plugins. Run /reload-plugins or start a new session to load it.

What it can access

Reach
L2Writes or runs: runs processes, reads files, reads env vars, reads the transcript, reads mod state, persists state, draws, other: $.branchDrill.open
Sees
every tool call
Draws in
Pane
Hooks
engine.createchangesDrill.opensession.startcommand.runturn.starttool.callturn.completeui.render

From a static scan of the mod's code by awesome-claude-code-mods. It shows what the code asks for, not a security review.

How Claude Code mods work

  • A mod is a plugin with a JavaScript or TypeScript module that runs inside Claude Code (version 2.1.287 or later). It can draw panes beside the transcript, a band above the prompt, buttons and toasts, restyle the spinner and tool rows, and watch or rewrite tool calls and prompts.
  • It installs like any plugin: add its marketplace with /plugin marketplace add owner/repo, then /plugin install name@marketplace.
  • Check what a mod can reach before installing: it runs with your permissions. Reach goes from drawing only, to reading files, to writing files or running processes, to the network. Run claude plugin validate on a clone to list its hooks and calls without running it.
  • Turn one off from the Installed tab in /plugin, or start Claude Code with --safe-mode to skip every customization for a session.
Claude Code docs

Details

Folder
plugins/changes-drill
Marketplace
motta-claude-mods
Author
l-a-motta
Last updated
1 November 2026

FAQ

What is changes-drill?

A Changes pane that says which turn changed each file and who (Claude, a subagent, Claude's shell or you), against HEAD, the session's start, the last turn or the base branch; with a guard for sensitive or out-of-scope files, a hunk peek, and a History section (what happened lately, in sentences or as a files tree) with a Branches button that opens branch-drill's pane (your branch against main, every branch as lanes or a subway map). Read-only: it changes nothing in the repository. No model calls, no tokens and no network: local git only, read while the pane is up. Opened by /changes-drill, or by $.changesDrill.open() from another mod (motta-statusline's files). It is a mod for Claude Code, from l-a-motta/motta-claude-mods on GitHub.

What can the changes-drill mod access?

Its widest reach is "writes or runs" (runs processes, reads files, reads env vars, reads the transcript, reads mod state, persists state, draws, other: $.branchDrill.open). It sees every tool call. It draws in Pane. Like any mod, it runs with your permissions.

How do I install changes-drill?

Inside Claude Code (v2.1.287 or later), run /plugin marketplace add l-a-motta/motta-claude-mods and then /plugin install changes-drill@motta-claude-mods.

More pane & dashboard mods

Browse the most popular Claude Code mods, all pane & dashboard mods, or the skills and MCP server directories.