peek

Periodic documentation review — checks docs/ hygiene, verifies features.md / planned.md / architecture.md / README.md / CLAUDE.md match implementation, and audits the mdbook manual against actual CLI flags, keybindings, and shipped file-type support.

Analyze a target — a crate, a module within a crate, or a single file — for its surface within peek, its place in the architecture, its API, its correctness, and its efficiency. Produces an overview followed by findings. Catches obvious bugs, not a deep edge-case bug hunt.

Periodic architectural review — critically re-examines existing design choices, hunts duplication, flags refactor candidates, checks conventions

Scoped code review — determines the change scope (explicit, discussion, or git), picks a source of truth (discussion, new docs, or code), then reviews the changes for correctness, doc agreement, doc coverage, convention adherence, duplicated shapes that want a shared abstraction, hand-rolled complex logic that wants a named/shared function, and unit-test coverage of complex logic.

Generate a 1-3 sentence user-facing highlight blurb for the next release. Reads commits since the last tag, filters out internal refactors / docs / tests / CI / chores, summarises only what a peek user would notice. Output is text the user pastes into the release workflow input after review. Use when user says "release highlight", "highlight for next release", "what's new", "release notes blurb", "/release-highlight".