Auto Fix Issue Take a tracker issue end to end without disturbing the user's active worktree. This skill classifies the issue, then handles both shapes of work itself: a bug drives the autofix chain ( om-verify-in-repo → om-root-cause → om-fix → om-open-pr → om-auto-review-pr → om-auto-qa-pr for UI-touching fixes) — it makes the go/no-go decision, prepares an isolated worktree, runs each chain step in sequence passing outputs verbatim, and keeps one continuous in-progress lock (issue first, handed off to the PR); a feature request takes the feature route below (spec resolution → om-auto-implement-spec , or om-auto-write-spec then om-auto-implement-spec when no spec exists). The chain skills stay runnable on their own under an external flow runner; this skill is that runner for a single session. Arguments {issueId | brief} (required) — a tracker issue reference (a GitHub issue number by default, e.g. 1234 ,

1234

, or an issue URL), or a free-form problem description — brief mode (step 1) files the issue via om-prepare-issue first, then continues on it. {repo} (optional) — owner/name ; if omitted, infer from the current git remote --interactive (optional, feature route) — opt into human gates: the spec is written with om-spec-writing 's interactive Open Questions hard stop instead of --autonomous defaults. Default is fully autonomous (defaults applied and posted for override). --slug (optional, feature route) — override the derived slug (passed through to the delegated skills) --no-ui (optional) — skip UI verification (bug route: skip step 10; feature route: passed through) --loop (optional, feature route) — forwarded verbatim to om-auto-implement-spec only when the user passed it to this skill ; the route never adds it on its own. Without it the engine self-routes by its configured Step threshold. --force (optional) — bypass the in-progress concurrency check; use only when intentionally taking over an issue another actor already claimed Chaining This skill consumes an {issueId} — or, in brief mode, a problem description it first turns into an issue via om-prepare-issue ( references/brief-mode.md ) — and both opens and finishes a chain. A previous skill may already have opened a PR for the issue — on the bug route the reuse guard in references/pr-finalize.md detects it via search-prs / the issue reference and continues on that PR; on the feature route an open PR referencing the issue means resume/continue, never a duplicate. It ends by reporting the PR: / Issue: chaining reference lines so the next skill in a chain can consume them. Companion skills, invoked verbatim: brief mode — om-prepare-issue ; bug route — om-verify-in-repo , om-root-cause , om-fix , om-open-pr (inline PR-open/label fallback when absent), om-auto-review-pr , om-auto-qa-pr (UI-touching fixes); feature route — om-auto-write-spec and om-auto-implement-spec . A missing required chain skill stops the run and names the skill to install. Workflow Show more Installs 938 Repository open-mercato/skills GitHub Stars 137 First Seen Jul 8, 2026 Security Audits Gen Agent Trust Hub Pass Socket Warn Snyk Warn