InstructionLintAgent Docs Drift Checker

01 Repository truth, checked locally

Your agent docs are making promises. Does the repo agree?

Find stale commands, moved paths, and contradictory setup guidance before an AI agent follows the wrong instruction.

Check a repository
  • ✓ Runs in your browser
  • ✓ No repository upload
  • ✓ Exportable evidence

02 Local scan

Bring the repository.
Keep the repository.

The archive is inspected in this browser tab. Nothing is sent to a server.

REPOSITORY ARCHIVEMAX 10 MB

Drop a .zip file here

or choose a local repository archive

Supported: instruction Markdown, package manifests, config files, and repository paths.

03 Evidence report

See what an evidence report looks like.

—Total conflicts
—Critical
—Docs checked
—Coverage
01
CriticalREADME.md:42 ↔ package.json:6
CLAIM

README promises `npm run verify` before every merge.

FACT

No `verify` script exists in package.json.

REPAIR

Add the script or remove the instruction from README.md.

02
ReviewAGENTS.md:18 ↔ src/cli
CLAIM

AGENTS.md names `src/commands` as the CLI entry point.

FACT

The directory moved to `src/cli` in the current tree.

REPAIR

Update the path and the two linked examples.

03
NoticeCONTRIBUTING.md:9 ↔ package.json:14
CLAIM

CONTRIBUTING.md lists Node 20 as the supported runtime.

FACT

The repository engine now requires Node 22 or newer.

REPAIR

Align setup instructions with package.json engines.

No scan yet.

04 The method

Not another vague
“docs look stale” warning.

  1. 01
    Read the claims

    Extract commands, paths, versions, and operational rules from agent-facing Markdown.

  2. 02
    Test repository facts

    Resolve each claim against manifests, configuration, and the actual file tree.

  3. 03
    Show the repair order

    Return evidence, severity, and the smallest useful correction—not a generic score.

05 Rules and boundaries

Small rule set.
Inspectible conclusions.

The Preview checks only claims it can compare with concrete repository evidence. It does not use an LLM or infer undocumented intent.

R-01

Relative paths

Markdown links and path-like inline code are checked against the archive file tree.

R-02

Package scripts

Explicit npm, pnpm, and yarn commands are checked against scripts in package.json.

R-03

Package manager

Commands are compared with packageManager declarations and supported lockfiles.

R-04

Document conflict

Conflicting explicit package-manager guidance is reported across supported instruction files.

06 FAQ

Before you choose a ZIP.

Does the repository leave my browser?

No. The ZIP is decompressed and inspected in this tab. Repository contents are not uploaded, stored, or sent to an AI model.

Does the checker execute code?

No. It does not run scripts, binaries, package managers, installers, or source files. Files are treated only as bytes and supported text evidence.

What does a clean report prove?

Only that the implemented deterministic rules found no covered conflict. It does not prove the documentation is complete, the code is correct, or the repository is secure.

Which files are supported?

Agent-facing AGENTS.md, CLAUDE.md, README.md, and SKILL.md files, plus package.json and npm, pnpm, or Yarn lockfiles used as project evidence.

Why was a file skipped?

A supported text file may be skipped when it exceeds 256 KB, is not valid UTF-8, or would push analyzed text above 2 MB. Every skip appears in report coverage.