# Merge Sweep

> Single-command dispatch shim. Runs the canonical omnibase_infra merge_sweep skill CLI because the declarative skill CLI is provided by omnibase_infra. The command resolves the skill->node mapping, dispatches node_pr_lifecycle_orchestrator in receipt mode, and prints one typed ModelSkillResult. No inline logic; markdown only.

- Skill: `omninode-ai/merge-sweep` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add omninode-ai/merge-sweep`
- Raw SKILL.md: https://api.skillmd.com/api/skills/omninode-ai/merge-sweep/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: OmniNode-ai (https://skillmd.com/u/omninode-ai)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/omninode-ai/merge-sweep

---


# /onex:merge_sweep — one command, one typed result

**Skill ID**: `onex:merge_sweep` · **Command**: `cd "$OMNI_HOME/omnibase_infra" && uv run onex skill merge_sweep` · **Backing node**: `node_pr_lifecycle_orchestrator` (omnimarket) # local-path-ok: merge_sweep dispatches from the canonical omnibase_infra checkout, not a ticket worktree

A dispatch skill IS one CLI call. Payload construction, node dispatch, and
result extraction all live in the `onex skill` entrypoint (declarative
`skill_mapping.yaml` registry in omnibase_infra) — there is no procedure to learn here. The
command prints exactly one typed `ModelSkillResult[ModelPrLifecycleResult]` JSON to
stdout carrying the FULL handler result; RuntimeLocal logs and intermediate
context go to a capture file + the artifact store, never to you.

See `prompt.md` for the one command and how to present the typed result.

## Routing Contract

The `cd "$OMNI_HOME/omnibase_infra" && uv run onex skill merge_sweep` entrypoint publishes to `onex.cmd.omnimarket.pr-lifecycle-orchestrator-start.v1` # local-path-ok: merge_sweep dispatches from the canonical omnibase_infra checkout, not a ticket worktree
through receipt-mode dispatch. If routing fails, surface `SkillRoutingError` directly; do not produce prose.

## What this skill does NOT do

- Construct a payload file, `cd` anywhere, or `cat` a workflow_result.json (all internal to `onex skill`)
- Run any inline scan, probe, or orchestration — the backing node owns all logic
- Contain executable logic in this directory — markdown only

## Related

- **CLI entrypoint**: `omnibase_infra/src/omnibase_infra/cli/cli_skill.py`
- **Skill→node mapping**: `omnibase_infra/src/omnibase_infra/cli/skill_mapping.yaml`
- **Result model**: `omnimarket.nodes.node_pr_lifecycle_orchestrator.handlers.handler_pr_lifecycle_orchestrator.ModelPrLifecycleResult`