How do I install the Merge Sweep skill?

Run npx skillmds@latest add omninode-ai/merge-sweep in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Merge Sweep safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Merge Sweep?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Merge Sweep free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Merge Sweep?

OmniNode-ai (@omninode-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Merge Sweep by omninode-ai — Agent Skill

Name: Merge Sweep
Author: OmniNode-ai

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.

OmniNode-ai 10bb884 3 files · 4.5 KB Updated Sep 17, 2026

File contents

/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

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

---name: merge-sweepdescription: 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.---# /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 worktreeA dispatch skill IS one CLI call. Payload construction, node dispatch, andresult extraction all live in the `onex skill` entrypoint (declarative`skill_mapping.yaml` registry in omnibase_infra) — there is no procedure to learn here. Thecommand prints exactly one typed `ModelSkillResult[ModelPrLifecycleResult]` JSON tostdout carrying the FULL handler result; RuntimeLocal logs and intermediatecontext 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 ContractThe `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 worktreethrough 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`

Frequently asked questions