Menu
Deploy docs for the current release by updating the release branch, without publishing a new version
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/rjdellecese/confect --skill release-docsThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
| name | release-docs |
| description | Deploy docs for the current release by updating the release branch, without publishing a new version |
Deploy the docs on main (or the ref given in $ARGUMENTS, if any) by triggering
the "Docs Release" workflow (.github/workflows/docs-release.yml), which
force-pushes that ref to the release branch. Mintlify deploys docs from
release, so this publishes docs updates without cutting a new npm release.
Follow these steps:
git fetch origin main release and show what would be deployed:
git log --oneline origin/release..<ref> -- apps/docsgit log --oneline origin/release..<ref> -- ':!apps/docs'origin/release and the ref, tell me the
release branch is already up to date and stop.packages/ or pending changesets in .changeset/), point
them out and warn me that any docs written for those unreleased changes
would go live too. Ask me to confirm before proceeding.gh workflow run docs-release.yml --ref <ref>
(default ref: main).gh run list --workflow=docs-release.yml, then
gh run watch <run-id>) and report whether the release branch was
updated successfully.