silent-changelisted
Install: claude install-skill PowerpBoxCaptain/silent-change
# silent-change
`git status` does not read your files. When a file's size and timestamps match what git recorded, git assumes
the content matches too. If the bytes change underneath, git keeps saying "clean", and most filesystems keep no
checksum of file data, so nothing else will say otherwise.
`check.mjs` reads every tracked file, hashes it exactly as git does, and compares that with the hash git holds.
## Run it
```sh
node <skill-dir>/check.mjs # the current repository
node <skill-dir>/check.mjs path/a path/b # these repositories
node <skill-dir>/check.mjs --all ~/code # every repository under a folder (4 levels, skips node_modules)
node <skill-dir>/check.mjs --json # machine-readable
```
Exit codes: `0` no silent change · `1` at least one · `2` none found, but something could not be checked ·
`3` the check broke. Treat `2` as "not a pass".
## What to do with a finding
1. **Do not restore the file yet.** Copy it as found, keeping its timestamp, to a dated folder outside the repository:
`~/silent-change-findings/<YYYY-MM-DD>/<repo-name>/<path>`. Write the path out in full, not through a variable.
For example: `mkdir -p ~/silent-change-findings/2026-11-15/myrepo/src && cp -p src/a.txt ~/silent-change-findings/2026-11-15/myrepo/src/`.
This copy is the only thing the skill writes.
2. Look at it: size, timestamp, what the bytes are (`xxd file | head`). Noise followed by zeros points at storage;
readable but different text points