hook

change-tracker — Claude Code hook: what it does, how to install

Q: How do I install change-tracker in Claude Code?

Run `npx claude-code-templates@latest --hook development-tools/change-tracker`, then use `.claude/settings.json` for the configuration.

Q: What does change-tracker do?

The hook watches `Edit`, `MultiEdit`, and `Write` activity in Claude Code. It stores modified and created file paths with timestamps in `~/.claude/changes.log`.

Q: Which actions does change-tracker record?

It logs a modified file after `Edit` or `MultiEdit`, and a created file after `Write`. These handlers run on `PostToolUse` events.

This hook logs file changes with timestamps. Use it when you need a simple record of Claude Code edits and file creation.

Install into Claude Code · claude-code-templates All methods and platforms ↓

npx claude-code-templates@latest --hook development-tools/change-tracker

Open on GitHub

What change-tracker does

change-tracker listens to PostToolUse events in Claude Code. After Edit or MultiEdit, it appends the modified file path to a log. After Write, it records the created file instead. Each entry includes the date, time, and action type.

The hook writes to ~/.claude/changes.log, so all activity goes into one fixed file. The log grows when the matching tools run. If ~/.claude/changes.log cannot be written, new entries will not be added.

Install it with npx claude-code-templates@latest --hook development-tools/change-tracker, then use .claude/settings.json for the configuration. The setup is intended for Claude Code.

What it helps with

track files changed by Claude Code
record when a file was edited
separate created files from modified ones
keep a plain activity log for agent actions

Example prompts for the agent

Edit src/app.js and record the change in the activity log.
Create config/local.json, then check that the event was logged.
Update several files with MultiEdit and show the change log.

How to install change-tracker

1claude-code-templates

npx claude-code-templates@latest --hook development-tools/change-tracker

2Manually: put the files in place

.claude/settings.json

The hooks block: event (PreToolUse, PostToolUse, Stop…) → command. Personal ones go to ~/.claude/settings.json

Step by step, with commands for each platform: Claude Code hooks: what they are, where to configure them, how to block a risky command

Questions about change-tracker

How do I install change-tracker in Claude Code?

Run npx claude-code-templates@latest --hook development-tools/change-tracker, then use .claude/settings.json for the configuration.

What does change-tracker do?

The hook watches Edit, MultiEdit, and Write activity in Claude Code. It stores modified and created file paths with timestamps in ~/.claude/changes.log.

Which actions does change-tracker record?

It logs a modified file after Edit or MultiEdit, and a created file after Write. These handlers run on PostToolUse events.

Source text

change-tracker.json · MIT

{
  "description": "Track file changes in a simple log. Records which files were modified and when for easy tracking of Claude Code activity.",
  "hooks": {
    "PostToolUse": [
      {
        "matcher": "Edit|MultiEdit",
        "hooks": [
          {
            "type": "command",
            "command": "echo \"[$(date '+%Y-%m-%d %H:%M:%S')] File modified: $CLAUDE_TOOL_FILE_PATH\" >> ~/.claude/changes.log"
          }
        ]
      },
      {
        "matcher": "Write",
        "hooks": [
          {
            "type": "command",
            "command": "echo \"[$(date '+%Y-%m-%d %H:%M:%S')] File created: $CLAUDE_TOOL_FILE_PATH\" >> ~/.claude/changes.log"
          }
        ]
      }
    ]
  }
}

secrets-scanner official github Scans the files a Copilot coding agent touched during a session for leaked keys and credentials before they get committed. Useful when the agent edits code fast. ★ 40,451repo stars governance-audit official github Scans GitHub Copilot prompts for threat patterns before execution. It records events to a local JSON log and stops destructive actions based on governance settings. ★ 40,451repo stars

From the same set804

The whole set →

mcp-server-architect A subagent that designs and writes MCP servers: tools, transports, sessions, security. Useful when you need a working server, not a sketch. 1,649installs hotfix Creates a Git Flow hotfix branch from main for urgent production fixes. It checks the branch name, repository state, and whether the issue is critical. 1,611installs game-designer Structures gameplay mechanics, calculates economy balance, and shapes progression curves. It drafts design specifications and balance sheets directly in your workspace. 1,598installs project-supervisor-orchestrator A subagent that runs a chain of other agents step by step and returns the result as JSON. Useful when one request has to pass through several specialized agents. 1,563installs competitive-intelligence-analyst A Claude subagent that gathers competitor and market data: company profiles, SWOT, industry trends. Useful before a product launch or when shaping strategy. 1,561installs flow-status Shows which Git Flow branch you are on, how far it has drifted from remote, and where it will merge. 1,514installs security-audit Runs a structured security review on your codebase, dependencies, and configuration. Handy before shipping to production or during code audits. 1,485installs shell-scripting-pro A subagent that writes and fixes shell scripts: strict error mode, quoted variables, portability across Unix-like systems. 1,479installs