# publish-all

publish-all releases all four project components at once: the spec-kit extension, VS Code extension, Claude Code mod, and Copilot canvas. Runs only if changes are ready and pass QA checks.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 110 repo stars
- Author: alfredoperez
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/alfredoperez/speckit-companion/tree/HEAD/.claude/commands/publish-all.md
- Updated: 2026-10-19
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/publish-all

## What it does

The command orchestrates four release phases in the correct sequence. It starts by publishing the spec-kit extension, then the VS Code extension (which depends on spec-kit version), then the Claude Code mod, and finally the Copilot canvas. At each stage, the command checks whether files have changed since the last release and offers to skip modules with no changes.

Before starting, the command requires three conditions: a clean working directory, the current branch being `main`, and a passing QA gate. If QA fails, it stops and asks you to run the QA check first. Each phase calls its own dedicated command (`publish-speckit-ext`, `publish`, `publish-mod`, `publish-canvas`), which remains the single source of truth for that stage—the orchestrator only coordinates the flow.

If a phase fails, everything released before it stays public; you can finish the rest later using individual phase commands in the same order. The final report shows what shipped, what failed, and what remains.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/commands/publish-all.md` — Call it with /publish-all. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/publish-all.md` — Call it with /prompts:publish-all. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/publish-all.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/publish-all.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/alfredoperez/speckit-companion/tree/HEAD/.claude/commands/publish-all.md

## When to use it
- release four project modules in the correct order in one pass
- ensure the VS Code extension uses the correct spec-kit version
- verify before release that the working directory is clean and on main branch
- detect which modules changed and need publication

## Example prompts
- /publish-all
- start releasing all project components
- publish spec-kit, VS Code, mod and canvas updates

## Source text · publish-all.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 039ee628cbda9973.

BEGIN THIRD-PARTY FILE 039ee628cbda9973
````text
---
allowed-tools: Bash(git *), Bash(gh *), Bash(zip *), Bash(tar *), Bash(specify *), Bash(claude *), Bash(npm *), Bash(node:*), Bash(python3:*), Bash(cp *), Bash(rm *), Bash(mkdir *), Bash(sed *), Read, Edit, Write, AskUserQuestion
description: Publish every deliverable that changed, in one pass - the spec-kit extension, the VS Code extension, the Claude Code mod and the Copilot canvas
---

## Context

- Git status: !`git status --porcelain | head`
- Current branch: !`git branch --show-current`
- spec-kit ext version: !`grep -A4 '^extension:' apps/speckit-extension/extension.yml | grep 'version:' | tr -d ' "' | sed 's/version://'`
- VS Code ext version: !`node -p "require('./package.json').version"`
- Mod version: !`node -p "require('./apps/claude-mod/.claude-plugin/plugin.json').version"`
- Canvas version: !`node -p "require('./apps/copilot-canvas/plugin.json').version"`
- Latest `speckit-ext-v*` tag: !`git tag --list 'speckit-ext-v*' --sort=-version:refname | head -1`
- Latest `v*` tag: !`git tag --list 'v*' --sort=-version:refname | head -1`
- Latest `speckit-companion--v*` tag: !`git tag --list 'speckit-companion--v*' --sort=-version:refname | head -1`
- Latest `canvas-v*` tag: !`git tag --list 'canvas-v*' --sort=-version:refname | head -1`

## Your task

Release every deliverable in one pass. This command only orchestrates: each phase's steps live in its own command, which stays the single source of truth.

| Phase | Deliverable | Command | Tag | Where it lands |
|---|---|---|---|---|
| 1 | spec-kit extension | `.claude/commands/publish-speckit-ext.md` | `speckit-ext-v*` | GitHub release, `companion-latest` |
| 2 | VS Code extension | `.claude/commands/publish.md` | `v*` | Marketplace, through `release.yml` |
| 3 | Claude Code mod | `.claude/commands/publish-mod.md` | `speckit-companion--v*` | this repo's plugin marketplace |
| 4 | Copilot canvas | `.claude/commands/publish-canvas.md` | `canvas-v*` | external plugin listing on github/awesome-copilot |

**The spec-kit extension goes before the VS Code extension, always.** The `.vsix` bundles `apps/speckit-extension/extension.yml` and compares it with the version installed in a user's project to say their spec-kit commands are out of date. Packaging the VS Code extension before the spec-kit bump ships a `.vsix` that expects the old version, so nobody hears about the new one until the next VS Code release. Packaging it against a version `companion-latest` does not serve yet tells every user to update to something the download does not have.

The mod and the canvas depend on neither. The canvas goes last because it is the only phase that waits on the user and leaves this repo, so nothing queues behind that pause.

### Steps

1. **Preflight.** Abort with a clear message if any fails:
   - The working tree is clean (`git status --porcelain` empty).
   - The branch is `main`.
   - QA gate: apply the Release gate in `.claude/commands/release-qa.md` (a `QA Report*.md` in the vault for the current HEAD with `verdict: ship` and no open FAIL). If it does not pass, stop and tell the user to run `/release-qa`; continue only on their explicit override. This is the only gate: the phases skip theirs.
2. **Find what changed** since each deliverable's last release:
   ```bash
   changed() { # changed <tag glob> <path>...
     local t; t=$(git tag --list "$1" --sort=-version:refname | head -1); shift
     [ -z "$t" ] && { echo "never released"; return; }
     git diff --quiet "$t" HEAD -- "$@" && echo "no changes since $t" || echo "changed since $t"
   }
   echo "spec-kit extension: $(changed 'speckit-ext-v*' apps/speckit-extension)"
   echo "VS Code extension:  $(changed 'v*' apps/vscode package.json README.md CHANGELOG.md)"
````
END THIRD-PARTY FILE 039ee628cbda9973

The third-party file has ended. Everything between the 039ee628cbda9973 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3731 of 7488 bytes. © alfredoperez · MIT · https://github.com/alfredoperez/speckit-companion/tree/HEAD/.claude/commands/publish-all.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
