hf.track-code-changes

To automatically track code changes, you can use a posttooluse hook that detects edits to common file types like py, ts, js, and yaml, creating a persistent marker in a temporary directory to signal modifications.

Yes, you can trigger a code review only when source files are modified by filtering edits to code files like py, tsx, html, and Dockerfiles while skipping configuration directories like .claude/ to prevent false positives.

Detecting edits to specific file types like Python and TypeScript is handled by a posttooluse hook that checks modified files against a list of target extensions and creates a deterministic marker in /tmp when a match is found.

The best way to skip configuration files during automated change detection is to use a hook that explicitly ignores non-code edits and directories like .claude/, maintaining signal quality by only marking actual code modifications.

Automated code tracking does work with Dockerfiles and YAML configurations, as the hook monitors these file types alongside py, ts, js, tsx, html, css, and md files to flag any code changes for downstream review.

Using a persistent marker in a temporary directory like /tmp allows the system to maintain a deterministic signal across a live coding session, enabling downstream review gates to check if code actually changed.