Thin Codex skill shim for node_pr_polish. Use to polish a PR toward merge readiness through the OmniMarket runtime adapter.
66%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./src/omnimarket/adapters/codex/skills/pr-polish/SKILL.mdThe canonical home for this skill is pr-polish in OmniNode-ai/omnimarket
This skill is a thin Codex runtime adapter shim over the OmniMarket
node_pr_polish node. The node owns conflict resolution, CI repair,
review-comment handling, local review, push, and automerge behavior. Do not add
GitHub scripting, shell repair loops, local-review logic, or merge logic to this
skill.
This section is generated from the Codex adapter contract and the target node contract. Keep the two surfaces distinct:
pr_polishscripts/run_codex_runtime_request.pyonex.cmd.omnimarket.pattern-b-dispatch.v1onex.evt.omnimarket.pattern-b-dispatch-completed.v1--compile-only to validate the request and binding
without publishing an event or starting a runtime. This is adapter preflight,
not evidence that a target runtime executed the command.runtime_evidence.runtime_observation and
runtime_evidence.adapter_dispatch_binding; compile-only is UNOBSERVED
with reason compile_only.runtime_evidence.schema_version is
runtime-evidence/v2; v2 requires runtime_observation and carries the
resolved node contract under adapter_dispatch_binding.node_contract.adapter_dispatch_binding reports
adapter_command_topic, requested_response_topic,
selected_terminal_topic, and terminal_selection (NODE_CONTRACT,
DIRECT_DELEGATE_SKILL_CONTRACT, or EXPLICIT_RESPONSE_OVERRIDE); its
node_contract is the resolved, typed contract binding.node_pr_polishpr_polishonex.cmd.omnimarket.pr-polish-start.v1onex.evt.omnimarket.pr-polish-completed.v1The skill must use the request wrapper for dispatch. It must not publish the target node command topic directly as its generic adapter transport; the target topics above are contract metadata selected by the runtime adapter.
| Argument | Description | Default |
|---|---|---|
repo | GitHub repo slug such as OmniNode-ai/omnimarket | Optional |
pr_number | Pull request number to polish | Optional |
ticket_id | Linear ticket ID for traceability | Optional |
required_clean_runs | Consecutive clean local-review passes required before done | 4 |
max_iterations | Maximum local-review cycles before stopping | 10 |
skip_conflicts | Skip merge conflict resolution | false |
skip_pr_review | Skip PR review comments and CI repair | false |
skip_local_review | Skip local review | false |
no_ci | Skip CI fetch in the PR review phase | false |
no_push | Apply fixes locally without pushing | false |
no_automerge | Skip enabling GitHub automerge at the end | false |
dry_run | Run without side effects | false |
worktree_path | Explicit worktree path override for live polish | Optional |
run_dir | Explicit state directory for breadcrumbs and result.json | Optional |
target_runtime_address | Optional runtime://... runtime target | Uses ONEX_TARGET_RUNTIME_ADDRESS when set |
Run from the omnimarket repo or an omnimarket worktree:
env -u PYTHONPATH uv run python scripts/run_codex_runtime_request.py \
--command-name "pr_polish" \
--payload '<json-payload>' \
--timeout-ms 300000If the user supplies a runtime://... target, add
--target-runtime-address '<runtime-address>' to the request command. If the
argument is omitted, the wrapper uses ONEX_TARGET_RUNTIME_ADDRESS when set.
For event-bus-free preflight, add --compile-only. This validates the payload,
command topic, response topic, correlation id, timeout, and target runtime
address without publishing to Kafka or starting a runtime.
Map user inputs into a JSON payload using the same field names:
repopr_numberticket_idrequired_clean_runsmax_iterationsskip_conflictsskip_pr_reviewskip_local_reviewno_cino_pushno_automergedry_runworktree_pathrun_dirFor live polish, include both repo and pr_number. For proof or planning
runs, set dry_run: true or use --compile-only when the user only wants to
validate dispatch shape.
If ok is true and output_payloads is present, treat output_payloads[0]
as the primary node result.
If ok is false, surface error.code and error.message directly.
src/omnimarket/nodes/node_pr_polish/scripts/run_codex_runtime_request.pypr_polishonex.cmd.omnimarket.pr-polish-start.v1onex.evt.omnimarket.pr-polish-completed.v1Prefer output_payloads[0]. Render final_phase, conflicts_resolved,
ci_fixes_applied, comments_addressed, error_message, and any state or
run artifact paths emitted by the node. All readiness decisions come from
node_pr_polish.
OmniNode-ai/omnimarket
13a7e30
Canonical home
since Nov 7, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.