How do I install the Release Merge skill?

Run npx skillmds@latest add quarto-dev/release-merge in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Release Merge safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Release Merge?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Release Merge free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Release Merge?

quarto-dev (@quarto-dev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Release Merge by quarto-dev — Agent Skill

Name: Release Merge
Author: quarto-dev

Release Merge

Use when merging the quarto-web prerelease branch into main for a Quarto release (publishing new stable docs), or when a release-time merge hits conflicts, backport-action noise, or _freeze hook failures. Not for ordinary PRs to main.

quarto-dev a7dc136 2 files · 2.8 KB Updated Sep 17, 2026

File contents

Release merge (prerelease → main)

Overview

At release time the prerelease branch is merged into main to publish the new stable docs. Rare operation, with a few quarto-web-specific hazards worth knowing before you start.

When to use

Doing a Quarto release — bringing new-stable docs onto main.
A release merge hit conflicts, backport-action noise, or a _freeze hook block.

Not for ordinary content PRs — those follow the normal Stable → Prerelease flow (see .claude/rules/quarto-web-workflow.md).

Canonical checklist

The authoritative release steps live in quarto-cli dev-docs/checklist-make-a-new-quarto-release.md. This skill covers only the quarto-web merge mechanics.

Steps

Choose the merge path — direct push, or a PR to main for CI build verification.
Resolve conflicts to the new-stable content.
Handle _freeze conflicts.
Regenerate cli-info.json against the stable tag.
Sync main back into prerelease.

Details

REQUIRED: read references/release-merge.md before executing — it carries the label, merge-commit, conflict, and freeze specifics.

Frequently asked questions