Refresh the framework-owned sections of a project's AGENTS.md after a Wagoe upgrade.
wagoe new renders AGENTS.md from a template that evolves with the
framework (new pitfalls, conventions, modules). This command re-renders the
marker-delimited blocks from the currently installed CLI's template and
splices them into the project file, leaving everything the user wrote
outside the markers untouched.
Synced blocks:
<!-- gen:fc-is --> FC/IS rules <!-- gen:naming --> case conventions <!-- gen:pitfalls --> common pitfalls <!-- wagoe:available-modules --> module tableNOT synced (project state): <!-- wagoe:installed-modules -->. Rows for
already-installed modules are re-removed from the refreshed available
table, mirroring what wagoe add did at install time.
Refresh the framework-owned sections of a project's AGENTS.md after a Wagoe upgrade. `wagoe new` renders AGENTS.md from a template that evolves with the framework (new pitfalls, conventions, modules). This command re-renders the marker-delimited blocks from the currently installed CLI's template and splices them into the project file, leaving everything the user wrote outside the markers untouched. Synced blocks: <!-- gen:fc-is --> FC/IS rules <!-- gen:naming --> case conventions <!-- gen:pitfalls --> common pitfalls <!-- wagoe:available-modules --> module table NOT synced (project state): <!-- wagoe:installed-modules -->. Rows for already-installed modules are re-removed from the refreshed available table, mirroring what `wagoe add` did at install time.
wagoe doctor — the one answer to "something is wrong".
Six commands could tell you something was wrong (bb doctor, bb doctor:env, bb doctor --all, bb check, bb smoke-check, bb guide next) and nothing said which to reach for first. This runs the diagnostic
ones in the order their answers depend on each other and ends with one next
action (BOU-324).
It orchestrates rather than diagnoses. Every check still lives in
wagoe-tools behind its bb task — those remain the machinery, and CI calls
them directly with --ci. This reads their --edn output, which is why that
mode exists: picking one action out of formatted terminal text would mean
parsing colour codes and column padding.
Ordering is not cosmetic. A missing Java makes every later answer noise, and an unparseable config makes the command smoke checks fail for a reason that has nothing to do with the commands. So a stage with errors stops the run and says so, rather than burying its own finding under three more screens.
`wagoe doctor` — the one answer to "something is wrong". Six commands could tell you something was wrong (`bb doctor`, `bb doctor:env`, `bb doctor --all`, `bb check`, `bb smoke-check`, `bb guide next`) and nothing said which to reach for first. This runs the diagnostic ones in the order their answers depend on each other and ends with one next action (BOU-324). It orchestrates rather than diagnoses. Every check still lives in wagoe-tools behind its `bb` task — those remain the machinery, and CI calls them directly with `--ci`. This reads their `--edn` output, which is why that mode exists: picking one action out of formatted terminal text would mean parsing colour codes and column padding. Ordering is not cosmetic. A missing Java makes every later answer noise, and an unparseable config makes the command smoke checks fail for a reason that has nothing to do with the commands. So a stage with errors stops the run and says so, rather than burying its own finding under three more screens.
Shared template helpers for the wagoe CLI: template loading, {{var}}
rendering, and the module-row pattern used to keep AGENTS.md's available-
modules table in sync (wagoe add removes a row at install time;
wagoe agents update keeps it removed on refresh).
Shared template helpers for the wagoe CLI: template loading, {{var}}
rendering, and the module-row pattern used to keep AGENTS.md's available-
modules table in sync (`wagoe add` removes a row at install time;
`wagoe agents update` keeps it removed on refresh).cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |