Problem: Multiple same/near-name repos for "oh-my-claudecode" — installing the wrong fork —— Trove problem library

What you will run into

Searching "oh-my-claudecode" finds multiple same-name/near-name projects, and you install the wrong version. Tutorials come from different forks, commands don't line up, and after install it's not what you wanted.

Why this happens

Upstream has multiple forks/same-name repos (e.g. AustinElite-family forks) with similar names, and search engines easily mix them in. Stick to two hard indicators: the original repo + the npm package name.

"Same-name / similar-name repos" on GitHub are a byproduct of the fork ecosystem: any open-source project can be forked, and forks keep the original name or a close variant;

search engines mix forks, derivatives and the original in results, ranked by popularity — the original isn't necessarily first.

But identity doesn't travel with the name: judging whether it's the original repo means checking two name-independent hard indicators — the org/author (Yeachan-Heo, the repo's owner) and the distribution anchor (the npm package name oh-my-claude-sisyphus, what installs actually address).

The npm name is especially reliable: names on npm are registered and unique; the author registered it, so an install command using that name points at the author's package (unless the name itself was squatted — a different attack).

So the verification order is fixed: npm package name first (install addressing matches) -> original repo (source ownership matches) -> version number (content matches).

All three match = the original project.

Step by step

1. Stick to the original repo and package name — Required

Original repo Yeachan-Heo/oh-my-claudecode; npm package name oh-my-claude-sisyphus (don't use fork-family tutorials' install commands).

2. Align to v5.0.0 — Required

npm view oh-my-claude-sisyphus version

Align with the recorded version 5.0.0 (2026-08-24 release).

3. Verify after install — Required

omc --version

How to confirm it works

Version output correct (measured output shape):

omc --version
→ 5.0.0 (measured under isolated HOME, 149 packages added, exit 0)

Other environments

Symptom

Searching "oh-my-claudecode" finds multiple same-name/near-name projects, installing the wrong version.

Cause

Upstream has multiple forks/same-name repos (e.g. the AustinElite fork family) with similar names.

Solution

1. Confirm the original repo: Yeachan-Heo/oh-my-claudecode; npm package oh-my-claude-sisyphus.
2. Align version v5.0.0 (2026-08-24 release); check package info before installing (npm view oh-my-claude-sisyphus version).

Verified install / uninstall in this marketplace (2026-08-28)

Local verification record

• Uninstall (manifest uninstall.cmd + verify): npm rm -g oh-my-claude-sisyphus -> removed 149 packages in 156ms -> verify zero leftovers exit 0.
• local repro log; CLI smoke: local repro log (omc --version 5.0.0; usage output); connectivity: local repro log.
• Not tested: Claude Code plugin form (/plugin install + /omc-setup need a logged-in session), MCP bridge real run, multi-agent real delegation.

Conflict notes

• possible-conflict (inferred): agent-governance-toolkit / ruflo / code-review-graph / cc-switch / claude-mem / skilldock — share ~/.claude.json registration sections / Claude plugin registration surface (see matrix pair evidence).
• possible-compatible (inferred): claude-code-router / deepcode / superpowers etc. (CLI surface isolated, matrix pairs).
• Form reminder: the npm CLI form has the smallest write surface; the Claude Code plugin form writes ~/.claude registration surfaces — mind this when co-installing multiple plugins.

Name confusion

• Three names: npm package oh-my-claude-sisyphus / plugin oh-my-claudecode / command omc (see Symptom 5).
• Distinguish same-name forks (AustinElite etc.) from upstream Yeachan-Heo (see Symptom 7).