agents-sync

Your instructions point at files that are not there.

CLAUDE.md, AGENTS.md and .cursorrules tell your assistant which files to read. Those files move. Nothing errors — the instruction just quietly stops meaning anything.

$ agents-sync

 broken-ref CLAUDE.md:3
  docs/architeture.md — not found
    →    docs/architecture.md  (did you mean?)

 broken-ref CLAUDE.md:4
  src/config.ts — not found
    →    src/config/index.ts  (moved — fixable)

2 broken-ref

It found real ones

Pointed at six public repositories carrying a CLAUDE.md, it reported three dead references and nothing else.

All three were real.

haddock3 moved docs/ to docs/pages/, leaving two instructions pointing at files that no longer existed.

react-data-table-component converted api.md to api.astro and kept telling its assistant to edit the old one.

The other four repositories came back clean — no noise.

How it stays quiet

A linter that cries wolf gets uninstalled. A reference is only reported when the tool can say something useful about it.

Reads prose, not just markup

“read docs/architecture.md first” counts, the same as a backticked path, a markdown link or a [[wikilink]]. Bracket syntax inside backticks does not — [[redirects]] in a TOML note is a table header, not a link.

Guesses where the file went

Exact name elsewhere, same name with a new extension, a file that grew into a folder (src/config.tssrc/config/index.ts), a typo, or a plural.

Partial paths are fine

Naming the tail of a path and leaving the root to context is something a reader follows without trouble, so it counts as resolved rather than broken.

Same name is not enough

A candidate has to live in a folder the reference actually names, so notes/core.md is never “fixed” to a core.md sitting in some cache directory.

Fix it without opening a terminal

A weekly background run raises a notification only when something new turns up — and the notification carries the fix.

It waits for you

The notification stays on screen until you deal with it, with Fix, Open report and Remind me tomorrow on it.

A missed week is not skipped

If the machine was off at the scheduled time, the run happens the next time you log in.

It does not nag

Findings are remembered between runs. Something you decided to live with stays quiet.

A page that explains itself

The HTML report says what each problem means and what it costs you, with a fix button per finding.

The scheduled run, the notification and its buttons are Windows-only. Everywhere else the CLI behaves identically — put it in cron and you get the weekly run without the toast.

Install

Zero dependencies, no build step. Node 18+.

git clone https://github.com/berkdemir18/agents-sync.git
cd agents-sync
npm link
CommandWhat it does
agents-syncReport problems. Exits 1 if it finds any, so it drops straight into CI.
agents-sync reportBuild a self-contained HTML page you can actually look at.
agents-sync applyRewrite what is unambiguous, keeping a backup of every edited file.
agents-sync scheduleRun it weekly in the background (Windows).