mergelisted

# Merge Land an open change request into the default branch. `/anchor:prepare-review` opens the CR and `/anchor:resolve-feedback` drives its threads to done; `/anchor:merge` checks that the CR is actually ready to land, merges it, and cleans up the branch behind it. The job is a **safe merge**: never land a CR that a gate says isn't ready, and never leave the local checkout stranded on a branch that no longer exists. Publishing what landed is `/anchor:release`, and this skill **names it without running it**. Releasing is a deliberate act on its own schedule — several merges commonly batch into one release — so the choice of when to cut one belongs to the author, not to whichever merge happened to be last. CR = change request: a pull request on GitHub, a merge request on GitLab. Pick the forge tool by the `origin` remote. **Don't narrate your work.** Every step below is an operating instruction, not a script to read aloud — follow the execute-quietly discipline: `${CLAUDE_PLUGIN_ROOT}/guides/execute-quietly.md`. For this skill, the only things worth surfacing are the resolved repo and CR in one line, any gate that blocks, the merge-method decision, and the one-line result. ```mermaid %%{ init: { 'look': 'handDrawn' } }%% flowchart TD Start(["/merge"]) --> Repo["Resolve repo + CR"] subgraph "Step 1: Gates" Repo --> Ready{Marked ready?} Ready -->|Draft| StopDraft["Ask to mark ready"] Ready -->|Ready| Mergeable{Mergeable?} Mergeable -