# Spec Kitty.merge

> Merge an accepted mission

- Skill: `spec-kitty/spec-kitty-merge` (Agent Skill)
- Install (CLI): `npx skillmds@latest add spec-kitty/spec-kitty-merge`
- Raw SKILL.md: https://api.skillmd.com/api/skills/spec-kitty/spec-kitty-merge/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: spec-kitty (https://skillmd.com/u/spec-kitty)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/spec-kitty/spec-kitty-merge

---


## Startup Upgrade Check

Run this at most once per active agent session before the first Spec Kitty command workflow.
If you already ran `spec-kitty upgrade --agent-check --json` in this session, reuse that result and skip this block.
Do not run or announce an upgrade check again for later Spec Kitty commands in the same session.
Otherwise, before continuing, run:

```bash
spec-kitty upgrade --agent-check --json
```

If JSON `action` is `none`, continue.
If `action` is `auto_upgrade`, run `upgrade_command` before continuing. If it fails, tell the user and continue with the current Spec Kitty version.
If `action` is `guidance`, show `upgrade_note` briefly, then continue.
If `action` is `prompt`, ask the user with the host-native question UI when available:

`Spec Kitty {latest_version} is available. You are on {installed_version}. Upgrade now?`

Use these choices:

1. Upgrade now (recommended) - record `upgrade_now`, run `upgrade_command`, then continue.
2. Always keep me up to date - record `always`, run `upgrade_command`, then continue.
3. Not now - record `not_now`, then continue.
4. Never ask again - record `never_ask`, then continue.

Record the selected choice before continuing:

```bash
spec-kitty upgrade --agent-choice <upgrade_now|always|not_now|never_ask> --agent-latest <latest_version> --json
```

If no host-native question UI is available, present the same four choices in plain text and wait for the user.
In non-interactive hosts, choose `not_now` and continue.


# /spec-kitty.merge - Merge an accepted mission

## Purpose

Run the canonical Spec Kitty CLI command for this workflow and treat its output as authoritative.

Do not rediscover mission context from branches, files, prompt contents, or separate charter loads. If mission selection is required, pass `--mission <handle>` where `<handle>` is a mission_id, mid8, or mission_slug.

## User Input

The content of the user's message that invoked this skill is the User Input. Consider it before proceeding. If it contains CLI arguments, append them to the command below.

## Steps

Run this command from the repository root:

```bash
spec-kitty merge <user-provided-args-if-any>
```

Report the command output and follow any next-step instructions it prints.