om-fix-issue-multi-optimized — Claude Code skill: setup and usage
om-fix-issue-multi-optimized — a skill for Claude Code runs issue resolution via the multi-optimized profile with separate workers and review advisors. It leaves verified changes staged without publishing to Git.
MIT 500 installs ★ 282 updated 2026-10-22
npx skills add open-mercato/skills --skill om-fix-issue-multi-optimized -a claude-codeWhat om-fix-issue-multi-optimized does
The skill acts as an alias that runs om-fix-issue using the multi-optimized profile. It accepts a required {issueId}, an optional {repo}, and an execution flag: --interactive by default or --autonomous.
Tasks split between implementation workers and independent reviewer councils. Feedback from models within the worker's family counts as a self-check rather than an external vote. The workflow enforces a stage-only rule: it never commits, pushes, or publishes code, ending by outputting the WORKTREE= path with indexed files.
Execution halts when the agentHarness setup fails its probe or lacks required model bindings. Users must run om-setup-agent-harness to configure workers, as an optimized profile cannot proceed on reviewer models alone.
What it helps with
- resolve issues using separate implementation and reviewer models
- keep verified fixes staged without automatic git commits
- enforce independent model council critique across model families
Example prompts for the agent
- multi optimized issue fix for issue 142
- workers plus model council fix for #89 --autonomous
- cheap cross-model staged fix for issue 305
How to install om-fix-issue-multi-optimized
1Skills CLI (Vercel)
npx skills add open-mercato/skills --skill om-fix-issue-multi-optimized -a claude-code2Manually: put the files in place
~/.claude/skills/om-fix-issue-multi-optimized/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/om-fix-issue-multi-optimized/
1Skills CLI (Vercel)
npx skills add open-mercato/skills --skill om-fix-issue-multi-optimized -a codex2Manually: put the files in place
.agents/skills/om-fix-issue-multi-optimized/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add open-mercato/skills --skill om-fix-issue-multi-optimized -a cursor2Manually: put the files in place
.cursor/skills/om-fix-issue-multi-optimized/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install open-mercato/skills skills/om-fix-issue-multi-optimized2Manually: put the files in place
.github/skills/om-fix-issue-multi-optimized/SKILL.md1Skills CLI (Vercel)
npx skills add open-mercato/skills --skill om-fix-issue-multi-optimized -a gemini-cli2Platform CLI
gemini skills install https://github.com/open-mercato/skills --path skills/om-fix-issue-multi-optimizedManually: put the files in place
.devin/skills/om-fix-issue-multi-optimized/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add open-mercato/skills --skill om-fix-issue-multi-optimized -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about om-fix-issue-multi-optimized
How to install om-fix-issue-multi-optimized in Claude Code?
Run npx skills add open-mercato/skills --skill om-fix-issue-multi-optimized -a claude-code. The file will be placed at ~/.claude/skills/om-fix-issue-multi-optimized/SKILL.md.
What does om-fix-issue-multi-optimized do?
It triggers om-fix-issue under the multi-optimized profile, pairing coding workers with an independent reviewer council. Changes remain staged in Git and are never committed or pushed automatically.
What is required to run om-fix-issue-multi-optimized?
It requires om-fix-issue and an audited agentHarness configuration with working model bindings. If checks fail, run om-setup-agent-harness to configure workers.
Source text
SKILL.md · MIT
---
name: om-fix-issue-multi-optimized
description: Thin combined alias for om-fix-issue that uses configured implementation workers and independent review advisors, then leaves the verified fix staged and unpublished. Use when the user says "multi optimized issue fix", "workers plus model council", "cheap cross-model staged fix", or "napraw issue multi optimized".
---
# Fix Issue — Multi Optimized
Select the `multi-optimized` profile without duplicating the base workflow.
## Arguments
- `--interactive` (default) or `--autonomous` — pass the execution mode to the base workflow; never enable publication. Reject both together.
- `{issueId}` (required) — pass through to `om-fix-issue`.
- `{repo}` and `--force` (optional) — pass through unchanged.
## Chaining
Consume the issue or brief and requested profile. Invoke the base workflow and its lower-level companions by name; stop with the missing name if one is unavailable. Emit the staged handoff, optional `Issue:`/`Spec:` references, and final `WORKTREE=` line. Publication is a separate human-authorized step.
## Workflow
**Claims:** `references/claim-pr.md` governs atomic/fallback ownership and release.
**ALWAYS check first:** Apply `.ai/skills/om-fix-issue-multi-optimized/SKILL.md` when present; safety rules still win.
0. **Agentic setup** — follow `references/agentic-setup.md` before any action: load approved configuration, apply local extensions and shared rules, and preserve the untrusted-content boundary.
1. Read and execute `om-fix-issue` in full with `--profile multi-optimized`.
2. Preserve its worker packets, diagnosis and final councils, same-family independence rule, stage-only boundary, claim handling, and report.
## Rules
- Shared communication, marker, label, and safety rules: `references/rules.md`. They always apply.
- Do not restate or replace any base workflow phase.
- Treat review from the implementation worker's family as a self-check, not an independent vote.
- When `agentHarness` or the requested profile is missing or fails its probe, stop, tell the user this variant needs configured model bindings, and run `om-setup-agent-harness` interactively — an optimized profile needs an audited implementation worker; adding a reviewer alone cannot unblock it — then re-run with the originally requested profile. Continue under another profile only on the user's explicit, informed request; never substitute one silently.
- Never commit, push, or publish.
© open-mercato · MIT · open-mercato/skills