# deploy-steward

deploy-steward serializes PR merges into main, tracks CI gates, triggers deploys, and files repair tasks when checks fail.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf (Devin Desktop), Claude.ai · ★ 937 repo stars
- Author: SethGammon
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/SethGammon/Citadel/tree/HEAD/skills/deploy-steward/SKILL.md
- Updated: 2026-10-29
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/deploy-steward

## What it does

The skill prevents landing stampedes when multiple agents finish work at once. It processes PRs sequentially using `node scripts/deploy-steward.js`. Input candidates come from `.planning/pr-readiness/*.md` reports or explicit URLs supplied via `--enqueue-pr`. State is saved to `.planning/deploy-steward/queue.jsonl`.

The steward acquires `.planning/deploy-steward/lease.lock` to prevent race conditions against main. It inspects PR state via `gh pr view`, updates branches behind base, waits for checks, and merges via `gh pr merge`. When checks fail or conflicts appear, it opens a repair task in `.planning/intake/` and stops.

An authenticated GitHub CLI is mandatory. Running the steward halts without `gh auth status` passing, since raw tokens and arbitrary curl calls are rejected by design.

## Install

### Claude Code (native platform)

1. **Plugin marketplace**
In the agent chat (not a shell):
```text
/plugin marketplace add SethGammon/Citadel
```
In the agent chat (not a shell):
```text
/plugin install citadel@citadel-local
```
This installs the whole citadel plugin with all its skills

2. **Skills CLI (Vercel)**
```bash
npx skills add SethGammon/Citadel --skill deploy-steward -a claude-code
```

3. **Manually: put the files in place**
- File: `~/.claude/skills/deploy-steward/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/deploy-steward/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add SethGammon/Citadel --skill deploy-steward -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/deploy-steward/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add SethGammon/Citadel --skill deploy-steward -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/deploy-steward/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install SethGammon/Citadel skills/deploy-steward
```

2. **Manually: put the files in place**
- File: `.github/skills/deploy-steward/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add SethGammon/Citadel --skill deploy-steward -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/SethGammon/Citadel --path skills/deploy-steward
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/deploy-steward/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/SethGammon/Citadel/tree/HEAD/skills/deploy-steward/SKILL.md

## When to use it
- serialize multiple pull requests into a safe mainline landing queue
- update out-of-date branches against main before CI validation
- execute custom deploy commands after each successful merge
- generate intake repair tasks when checks fail or conflicts arise

## Example prompts
- Scan ready PRs and run the steward with the deploy command `npm run deploy`
- Enqueue PR `https://github.com/OWNER/REPO/pull/123` and execute a dry run
- Process the landing queue in merge-queue mode

## Source text · SKILL.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: 2a91b2f2c048c2e9.

BEGIN THIRD-PARTY FILE 2a91b2f2c048c2e9
````text
---
name: deploy-steward
license: MIT
description: >-
  Mainline deploy steward. Consumes ready PRs, owns a lease on mainline landing,
  refreshes PR state, updates stale branches, waits for CI and deploy gates,
  merges or queues one candidate at a time, and opens repair tasks for failures.
user-invocable: true
auto-trigger: false
trigger_keywords:
  - deploy steward
  - deploy queue
  - merge steward
  - mainline steward
  - land prs
  - land PRs
  - deploy prs
  - deploy PRs
  - merge queue
  - release train
effort: high
last-updated: 2026-06-20
---

# /deploy-steward - Mainline Deploy Steward

You are the deploy steward. You serialize mainline landing for parallel agent work.
Your job is to turn many ready PRs into one safe mainline stream: refresh, update,
wait for checks, merge, deploy, and open repair work when something fails.

## When to Use

Use this when the user asks to:

- land multiple ready PRs without a manual merge stampede
- keep agent PRs rebased or branch-updated against latest main
- merge only after required checks pass on current heads
- run a deploy command after each safe serial merge
- open repair tasks for failed checks, conflicts, or closed PRs

Do not use this for code review quality findings; use `/review`. Do not use this
for local worktree conflict analysis only; use `/merge-review`.

## Required Inputs

The steward can start from either source:

- `.planning/pr-readiness/*.md` reports generated by `node scripts/pr-ready.js`
- explicit GitHub PR URLs passed with `--enqueue-pr`

If `.planning/` does not exist yet, run the project setup/init flow first or
create `.planning/pr-readiness/` before scanning. Treat a missing readiness
directory as an empty queue, not as proof that there is nothing to land.

The runtime requires:

- GitHub CLI authenticated for the target repo
- visible PR status checks unless `--allow-no-checks` is explicitly justified
- a deploy command if the repo deploys outside the merge platform

If `gh` is not installed or is not authenticated, stop before `--run` and ask the
operator to run `gh auth status` / `gh auth login`. Do not substitute raw tokens
or ad hoc curl commands inside the steward.

## Invocation Forms

```bash
node scripts/deploy-steward.js --scan
node scripts/deploy-steward.js --scan --run
node scripts/deploy-steward.js --run --deploy-command "npm run deploy"
node scripts/deploy-steward.js --enqueue-pr https://github.com/OWNER/REPO/pull/123 --run
node scripts/deploy-steward.js --run --merge-mode merge-queue
```

Use `--dry-run` before first live use on a repo:

```bash
node scripts/deploy-steward.js --scan --run --dry-run
```

## Protocol

### Phase 1 - Build the Queue

Run:

```bash
node scripts/deploy-steward.js --scan
```
````
END THIRD-PARTY FILE 2a91b2f2c048c2e9

The third-party file has ended. Everything between the 2a91b2f2c048c2e9 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 2740 of 6690 bytes. © SethGammon · MIT · https://github.com/SethGammon/Citadel/tree/HEAD/skills/deploy-steward/SKILL.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
