Catch drift before the PR
Until now, Erode only ran in CI. You found out about drift after pushing a PR and after someone already reviewed the code.
0.6.0 adds local detection. Three things shipped:
erode check
Section titled “erode check”A new command that runs the same AI pipeline as analyze but operates on local git diffs instead of fetching PR data from a platform API.
erode check ./model # unstaged changeserode check ./model --staged # staged changeserode check ./model --branch main # branch diffNo platform tokens needed. No PR required. Just a local git repo and an AI provider key. Wire it into git hooks with --fail-on-violations for automatic checking. See CLI Commands for all flags and options.
Claude Code skill
Section titled “Claude Code skill”A custom skill that runs erode check during Claude Code sessions. When Claude Code writes code that introduces a new import, API call, or service connection, the skill flags undeclared dependencies and surfaces them in the conversation.
The skill triggers on new integrations and before commits. It skips changes that cannot introduce dependencies (docs, tests, config). A violation is not an error. Claude Code shows what it found so you can decide: fix the code or update the model.
npm publishing
Section titled “npm publishing”Erode is now published as @erode-app/cli on npm. Run it with npx @erode-app/cli check ./model, no global install needed. This is what makes the Claude Code skill work. See Getting Started for setup.
What’s next
Section titled “What’s next”- CLI Commands: all
erode checkflags and options - Claude Code integration: setup guide for the skill
- Getting Started: CI setup for
erode analyze