Skip to content

Fix created mode rules firing on modified files - #83

Merged
nhorton merged 2 commits into
mainfrom
claude/fix-created-mode-rules-zfMvU
Jan 20, 2026
Merged

Fix created mode rules firing on modified files#83
nhorton merged 2 commits into
mainfrom
claude/fix-created-mode-rules-zfMvU

Conversation

@nhorton

@nhorton nhorton commented Jan 20, 2026

Copy link
Copy Markdown
Contributor

The capture_prompt_work_tree.sh script was incorrectly capturing only "changed files" (git diff) instead of "all tracked files" (git ls-files) as the baseline for compare_to: prompt mode.

This caused created: mode rules to incorrectly fire when existing files were modified, because those files weren't in the baseline (they weren't "changed" at prompt time, just existing).

Fix: Change baseline capture to use git ls-files which captures ALL tracked files. This ensures:

  • Newly created files (not in baseline) -> trigger created: rules
  • Modified existing files (in baseline) -> do NOT trigger created: rules

Also adds a manual test case for created mode to verify this behavior.

The capture_prompt_work_tree.sh script was incorrectly capturing only
"changed files" (git diff) instead of "all tracked files" (git ls-files)
as the baseline for compare_to: prompt mode.

This caused created: mode rules to incorrectly fire when existing files
were modified, because those files weren't in the baseline (they weren't
"changed" at prompt time, just existing).

Fix: Change baseline capture to use git ls-files which captures ALL tracked
files. This ensures:
- Newly created files (not in baseline) -> trigger created: rules
- Modified existing files (in baseline) -> do NOT trigger created: rules

Also adds a manual test case for created mode to verify this behavior.
The function was incorrectly subtracting the baseline files from the
current staged files, which meant modified files were never detected
(they appear in both sets and get subtracted out).

Now the function simply returns ALL files with staged changes, which
is what trigger/safety, set, and pair mode rules need to detect file
modifications during the agent response.

The baseline file is only used by get_created_files_prompt() to detect
truly NEW files for created: mode rules.

This completes the fix for the created mode rules bug - both issues
are now resolved:
1. Baseline captures ALL tracked files (not just changed)
2. Changed files detection returns ALL staged files (not just new)
@nhorton
nhorton merged commit 8d78553 into main Jan 20, 2026
4 checks passed
@nhorton
nhorton deleted the claude/fix-created-mode-rules-zfMvU branch January 20, 2026 21:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants