All products

Plan a Contentstack release with AI

Prepare related pages and assets as one editorial change. Check which versions belong together and review the same combination in staging before launch.

Plan a Contentstack release with AI when publishing half a change would tell the wrong story. A new price table, a comparison page and a promotional banner may each pass review on their own. Launching the banner while the old table remains visible is the problem the release needs to solve.

The cms-releases guide helps an editorial and delivery team choose what belongs together and select the version of each item. It also explains a subtle point about late edits: bringing an entry up to date is not a promise that a newly referenced image has joined the release. Inspect those dependencies separately.

What it does

  • Identify which changes need a coordinated launch
  • Choose the intended version of each entry and asset
  • Recheck references added late in editing
  • Plan a staging review using the proposed release contents
  • Give the site team notice of multiple publishing events

Install and use

  1. Use the skill with a compatible agent and an inventory of entries, assets and target environments. Advice requires no account connection; deploying the release requires an authorised Contentstack user.
  2. Ask: “Plan a release for this guide, its revised diagram and the homepage feature. Which versions should our editor inspect together in staging?”
  3. Verify the staged set against the inventory. If someone replaces a reference afterwards, repeat the affected check before authorising production deployment.

FAQ

Source

Made by Contentstack. Original skill: cms-releases, published on GitHub under the MIT licence.

View on GitHub