AkiDevRule 3.x: install with npx, hooks that block skipped steps

AkiDevRule went from 3.0.0 (2026-09-13) to 3.7.0 (2026-10-08) in one consistent direction: turning rule reading from a reminder into something that can be checked. Install shrank to a single npx command, and agents skipping a required step is now stopped by a hook instead of asked politely.

How do I install and update AkiDevRule since 3.0?

Since 3.0.0 the main install path is npx @akinet/akidevrule@latest, with no clone, and running the same command again updates it. The installer was rewritten in plain Node.js, so Python is no longer required, and a fresh install produces the same 121 files as the old installer. Since 3.2.0 it finds every Claude config directory (~/.claude*), and 3.7.0 adds a resident rule block for Codex CLI.

How does the hook that blocks edits before the rules are read work?

The aki-route-guard hook (3.6.0) denies the first Edit or Write of each file type in a session until the matching rule files have been read, and the denial names the files to read. The reason: measurements on real transcripts showed the [RULES] receipt was present while the second step, actually reading the rules, was still skipped. Version 3.7.0 counts only reads made after the last context compaction, because rules read before it are no longer in the model's context.

What changed in 3.7.0 for Claude Opus 5.5 and Sonnet 5.5?

• ◆agent.B7 states that your rules win over the harness's own instructions, with a [SKIP] penalty card for a mandatory step that was compressed.
• ◆The aki-compact-reread hook says once after each compaction that the rules read earlier are no longer in context.
• ◆RULE-test.md and test_lint.py set the root rule of writing as few tests as possible and ban tests that overwrite real data, after a fully green 51-test suite rewrote a live app data directory.
• ◆Every open item in a report carries a short stable code, and an agent removes the worktrees and build directories it created.

What else did 3.1 to 3.6 add?

• ◆3.1.0: /akiship activates on an explicit release order, and deep-think runs on its own at defined triggers.
• ◆3.3.0: /akiship must load the rules, writes a receipt for every step, and carries a migration doctrine plus post-deploy verification.
• ◆3.5.0: agents may no longer git stash, reset --hard or clean on their own, and docs/ref/fact-* fact docs carry their verification trail.
• ◆3.6.0: the pattern.A9 law keeps a draft separate from the record, and the CLAUDE.md template shrinks to two imports.

Where should I start?

Run npx @akinet/akidevrule@latest on a machine that uses Claude Code, then open a new session: the behavior rules and the router are already in context, and the rest loads when a task matches. The package only installs Markdown files, skills and hooks into your config directory and runs no background service. The article Rules for AI coding agents explains how the layers fit together.