Repository navigation
v2.5.0
gaze init now keeps the /gaze command up to date. Until now, .opencode/commands/gaze.md was written once and never refreshed, so most projects were running an old copy of Gaze's main command. A survey of 10 repos found stale copies, some with two conflicting version markers. If you need your own version of the command, there's now a separate gaze-local.md file for it.
Upgrading
Run gaze init once in each project. Your first run brings /gaze up to date with everything it has missed: the <protect> block (#221), the rendered AI report from spec 040, and analyzer and language detection. It also fixes duplicate version markers.
Behavior change: gaze init now overwrites .opencode/commands/gaze.md whenever it differs from the current version, without needing --force. This matches how gaze-fix.md already worked. If you edited gaze.md, move your changes to .opencode/commands/gaze-local.md (see below) before running gaze init.
Highlights
/gaze stays current (#356, closes #353)
All nine files gaze init writes under .opencode/ are now owned by Gaze and updated when they change. The CI workflow file is still yours: it's written only if missing, and re-written only with --force.
gaze-local.md for your own /gaze variant (#356)
gaze init never writes .opencode/commands/gaze-local.md, even with --force. OpenCode exposes it as /gaze-local, so you can keep a customized command there next to the managed /gaze. When gaze init updates gaze.md, it prints a one-line tip pointing to this file.
Plain re-runs of gaze init no longer suggest --force, since no file under .opencode/ can be skipped any more. The hint still appears when the CI workflow is skipped.