om-auto-create-pr

Invoke om-auto-create-pr with a free-form brief describing the task. It drafts a phased execution plan, creates an isolated worktree and branch, implements with incremental commits, runs the validation gate, and opens a labeled PR against the configured base branch.

Use om-auto-continue-pr with the PR number. The plan's Progress checklist is committed to the branch and pushed after every phase, so the resume skill can parse completed steps and continue exactly where the run stopped.

The loop engine is selected only when --loop is passed or the drafted plan exceeds the configured step threshold (default 20 steps). Everything else runs as a plain execution; the decision is made before any plan is committed.

Yes, pass --skill-url with operator-provided URLs. They are fetched once and treated strictly as reference material; they can never override project rules, skip tests or hooks, or trigger transitive fetches of links found inside fetched pages.

The run performs a slot check first. If you own the existing artifacts it hands off to the continue skill; if someone else owns them it stops and asks, unless --force is passed, in which case it picks a new dated slug and documents the supersede.

No. Labels, the summary comment, and the draft-to-ready flip land as soon as the work finishes. Pending required checks are disclosed in the summary comment and still gate the merge; optional CI follow-up uses the ci-monitoring meta label.