Stable
drift

Your code changed. Your docs didn't.

01/

The Problem

Your code changed. Your docs didn't. JSDoc says one param, function takes three. @example blocks reference APIs you removed last sprint. Markdown docs import exports that no longer exist. Nobody knows until a user files an issue.
[ terminal ]
 
02/

The Solution

21 commands. Two surfaces, one engine — composed commands for humans, primitives for agents. 15 drift types across 4 categories: structural (JSDoc vs code), semantic (deprecation, broken links), example (code errors), and prose (stale markdown references).
[ terminal ]
 
03/

The Output

All commands output {ok, data, meta} JSON to stdout. Every drift issue includes filePath and line — agents read the diagnosis, then edit code directly. Detection is the tool's job. Mutation is the agent's job.
[ terminal ]
 
04/

Agent Usage

Ships as a Claude Code skill. Install it, then /drift inside any TypeScript project. The CLI outputs structured JSON with location data — agents use it to fix your docs automatically. Every primitive is individually addressable. scan is a convenience, not a gate.
[ terminal ]
 
05/

Get Started

Entry auto-detects from package.json. Just drift scan in any TypeScript project. Compose primitives in CI or let agents use them directly.
[ terminal ]