Affaan MustafaandGitHub
c05b2d6614
* chore: retire the Everything Claude Code name, ECC only Replace the expanded product name and the everything-claude-code slug with ECC across READMEs, translated docs, harness folders, skills, commands, scripts and examples. Repo URLs now point at affaan-m/ECC. Rename repo-internal artifacts to ecc forms (ecc-conventions skill, ecc-guardrails, ecc-research-playbook, ecc-team-config, ecc-instincts with ecc-* ids) and update .claude/ecc-tools.json. Legacy install ids, plugin dirs, package names and MCP prefixes stay where existing installs resolve against them. The codex global-state check and harness-audit repo detection accept the new name first and the legacy one as a fallback. The Discord bot prefers ~/GitHub/ECC and falls back to the nested legacy checkout path. Refresh the skill-triggers registryDigest for the changed skill text. * fix(ecc-tools): drop managed paths to the removed Claude repo skill .claude/skills/<repo-skill>/SKILL.md was deleted in #2770 but stayed listed in ecc-tools.json and the team config. Remove those entries and point the Claude Code adapter at the existing .agents/skills/ecc-conventions/SKILL.md.
3.0 KiB
Migrating From ECC 1.x To 2.0
ECC 2.0 renamed the repo (affaan-m/everything-claude-code → affaan-m/ECC) and the plugin identifier (everything-claude-code@everything-claude-code → ecc@ecc). If you installed 1.x, follow this guide to upgrade cleanly. See also the Naming + Migration Note in the README.
TL;DR
# 1. Install 2.0
/plugin marketplace add https://github.com/affaan-m/ECC
/plugin install ecc@ecc
# 2. Remove the old plugin
/plugin uninstall everything-claude-code@everything-claude-code
Then remove any leftover 1.x folders (see below) and restart the session.
"I now see two ECC plugins"
Expected. ecc@ecc and everything-claude-code@everything-claude-code are treated as separate plugins by Claude Code. Uninstall the old one; keep only ecc@ecc. Running both duplicates skills, commands, and hook executions.
Leftover folders after uninstalling 1.x
/plugin uninstall removes the plugin from the active list, but can leave the old directory in the Claude plugin cache and any manual copies in your home directory.
Safe to delete after the old plugin no longer appears in /plugin list:
- The old plugin folder under the Claude plugins directory (e.g.
~/.claude/plugins/...everything-claude-code...) - A 1.x manual install in your home folder (a cloned
everything-claude-code/directory), if you are not using it as a working checkout - Old manually-copied surfaces under
~/.claude/(skills/,commands/,agents/entries that came from 1.x) — the 2.0 plugin provides current versions
Do NOT delete ~/.claude/rules/ content you copied intentionally, or personal memory/state files.
Does removing 1.x affect my existing projects?
No. ECC is a harness layer: skills, commands, agents, hooks. It does not alter your project code or git history. Everything ECC produced in your repos (commits, files, PRs) is untouched. Your next session simply loads 2.0 surfaces instead of 1.x ones. Slash-command namespaces changed from everything-claude-code:* to ecc:*.
One install path only
Do not stack the plugin install with the manual installer (install.sh / install.ps1 / npx ecc-universal install --profile full). Pick one path; stacking creates duplicate skills and duplicate hook runs. If you already stacked, see Reset / Uninstall ECC.
Using 2.0 across harnesses (Codex, Antigravity/agy, OpenCode, Cursor)
2.0 is cross-harness. Use the manual installer with a target:
npx ecc-universal install --profile core --target codex # Codex CLI
npx ecc-universal install --profile core --target opencode # OpenCode
npx ecc-universal install --profile core --target cursor # Cursor
Run npx ecc-universal consult "<what you need>" --target <harness> to preview which components fit before installing. Harness-specific guides: ANTIGRAVITY-GUIDE.md, HERMES-SETUP.md, QWEN-GUIDE.md, JOYCODE-GUIDE.md.