Skip to Content
DocumentationFeaturesCommandsamend

gtmesh amend

Re-opens a sealed or published page for a light re-seal after a body edit that isn’t a prose rewrite — moving it to needs_update.

gtmesh amend <slugs…>         # re-open for a light re-seal (e.g. after image placement)

What it does

gtmesh amend handles body edits that change the page’s files but not its prose. The canonical example is image placement: the writer authors art-direction briefs, and the image-director skill later generates and places the real asset files into the bundle. That’s a body change, so the page has to re-seal — but it isn’t a rewrite, because the prose is untouched.

amend moves the named pages to needs_update, the status that says “this body changed; re-seal it.” You then seal to re-validate with the assets present and re-stamp the body hash, and publish to ship.

# (the image-director skill generates and places the asset files into the bundle)
gtmesh amend <slug>      # body changed (assets placed) → needs_update  (the skill runs this)
gtmesh seal <slug>       # re-validates with assets present, re-stamps the body hash → review
gtmesh publish <slug>    # → published, now with images

A prose rewrite is a different path — that’s a rewrite action that reruns the writer (and it keeps placed assets, so image work is never undone). For a full re-author from scratch, see recreate.

Arguments & flags

ArgumentDescriptionDefault
<slugs…>Page slugs to amend (required)—

There are no command-specific flags. The global options (--project, --json, --quiet) apply.

Reads & writes

  • Consumes: the named page bundles and their current status in the registry.
  • Produces: the row moved to needs_update, ready for a re-seal.
  • Commits: the registry change — commit it with the placed assets.
Last updated on
recreatestatus