Generated from the binary

Command registry

This page is not maintained by hand. A graph-owned recipe runs hypermake commands --json at build time and this page renders the projection (public://_hypermake/site/commands.json). If the binary's command surface changes, this page changes on the next build — the list below and the registry cannot disagree.

Registry totals

From the registry envelope: the projection self-describes as complete.

MeasureCount
Registered commands150
Help-visible (carry a summary)44
Shared verbs11
Specialists33
Developer commands106

Shared verbs

The product surface: one grammar over typed subjects. The command doctrine page explains how these chain.

Shared verbs

VerbSummary
inspectidentify target, URL, route, owner, authority, and next affordances
explainexplain recipe ownership, freshness, and buildability
checkvalidate diagnostics/readiness for a target, source, or scope
buildmaterialize graph-owned targets
serveserve graph-backed output and optional live inspector runtime
profilemeasure target/runtime performance and write evidence
comparecompare reports, evidence runs, images, or artifacts
proverun a promotion proof or canary and persist evidence
editinspect source-owned edit guidance for a subject
syncsynchronize state between authorities
cleanprune explicitly scoped derived state

Specialists

Named tools that workflows still reach for directly. The shape column is the most honest invocation hint the registry carries for each row: an explicit usage line, a subcommand list, or just the name.

Specialist commands

CommandShapeSummary
rootrootshow or initialize project identity
versionversionshow tool and adapter information
statusstatussummarize project readiness
watchwatchrebuild targets when source files change
branchesbranchesinspect git worktrees and registered backends
diagnosticsdiagnostics inspect template or target graph diagnostics
cachecacheinspect and prune rebuildable cache artifacts
evidenceevidence status|ingest|recent|latest|metrics|compare|gate|export|export-status|pruneinspect and compare the project-local evidence store
statechartstatechart compilecompile and validate SCXML statecharts into graph-owned IR artifacts
authauth owner-ceremony|owner-exchange-refreshrun explicit owner authentication ceremonies
graph-canvasgraph-canvas buildmaterialize canonical graph-canvas artifacts from input-v2
batchesbatchesinspect cached batch manifests
commandscommandsproject the full Hypermake command registry for tools and agents
image-parityimage-paritycompare raster image output trees
resolveresolve canonicalize a target, protocol, or path
matchmatchshow the owning recipe
graphgraphinspect the build graph
valuevalueinspect persisted virtual target values
affected-byaffected-by show targets affected by a changed source
pspslist root-bound Hypermake processes
attachattachattach to the project daemon or report fallback
front-doorfront-doorkeep a thin CLI request front door open on stdin/stdout
daemondaemon status|start|stop|run-oncemanage the root-bound project daemon
agent-briefagent-briefsummarize target state for agent work
edit-guidanceedit-guidanceshow likely source files and edit constraints
inspect-urlinspect-urlmap a browser URL/path back to graph targets
doctordoctordiagnose project readiness and migration debt
scaffoldscaffolddraft or write a local recipe
skill-validateskill-validatevalidate the agent skill command surface
lzrlzr scope-mapinspect LZR binding lineage and scope ambiguity
lzr-renderlzr-renderrender LZR templates through the CLI
744-campaign-audit744-campaign-auditinspect 744 campaign migration signals
email-mjml-auditemail-mjml-auditinspect MJML usage before email migration

Developer commands

Internal plumbing: recipe helpers, migration shims, profiling probes, and asset pipeline steps. For these 106 commands the registry reliably carries name and class only — they are marked help-hidden and ship no summary, and this page will not invent descriptions the binary does not make. Depth here is honestly "run hypermake <command>" territory: most answer a bare invocation with a usage line or a typed diagnostic, though a few registered names fall through to recipe dispatch instead. The names are the reliable surface; nothing more is promised.

project bundle-status recipe-bundle bundle bundle-diff ide protocols plugins action-packs components recipe can-build check-overlap list patterns examples list-admissible audit-churn audit-phase1 profile-graph-segment impact scope-force-json wr-scope-impact lzr-render-result lzr-corpus package-manifest package-zip-from-manifest campaign-package-manifest campaign-package-zip-from-manifest cdn-manifest cdn-prepare-from-manifest cdn-publish-manifest cdn-publish-from-manifest svg-public-deps xd-localize-svg composite-shell-svg composite-postprocess-svg js-concat isolated-svg-postprocess newsletter-renderids profile-composite-materialize profile-browser-deps profile-current-campaign-deps graphics-corpus graphics-manifest graphics-build-artifact reverse-index invalidate invalidate-bundle-diff state-summary manifest-summary manifest-audit benchmark-compare benchmark inspector client-graph architecture-gates compat-audit validate-delivery 744-campaign-convert ensure-fresh open-fresh deploy-static deploy asset-refs plan ensure validate normalize-json normalize-dom svginfo-lite svginfo-query-all animin-css animax-css svg-postprocess campaign-ad-hash campaign-ad-svg-alias campaign-ad-raster-alias campaign-ad-gif fig-adjusted-asset-alias d-prereqs d-manifest canonicalize explain-target lanes registry lease subscribe scratch proposal agent packet packet-tool agent-primer agent-init docs-index up service logs dev-service dev-caddy dev-hosts dev-route dev-site dev-sites expressions
Verify this yourself shell
hypermake commands --json
hypermake explain public://_hypermake/site/commands.json
hypermake explain rendered/public/docs/cli-commands.html