fix: rename conflicting commands to egc-* and drop bare duplicates - #39
Merged
Conversation
Gemini CLI auto-renamed our `/plan` and `/docs` to `/everything-gemini-code:plan`
and `/everything-gemini-code:docs` because they conflicted with built-in
commands. The repo also carried two naming schemes side-by-side (`plan.toml`
vs `ecc-plan.toml`, `docs.toml` vs `ecc-docs.toml`), doubling the conflict
surface.
- Delete bare-name duplicates: `commands/plan.toml`, `commands/docs.toml`,
`workflows/plan.md`
- Rename `ecc-*` to `egc-*` to match the current project name (Everything
Gemini Code):
commands/ecc-plan.toml -> commands/egc-plan.toml
commands/ecc-docs.toml -> commands/egc-docs.toml
workflows/ecc-plan.md -> workflows/egc-plan.md
- Update all in-repo references (READMEs, command maps, TOML self-references)
from `ecc-plan`/`ecc-docs` to `egc-plan`/`egc-docs`
…icts
Every extension command now uses the `egc-` prefix (Everything Gemini Code).
Previously bare names like `/plan`, `/docs`, `/build-fix`, `/tdd`, `/verify`,
etc. collided with Gemini CLI built-ins or user-level commands, causing the
CLI to auto-rename them to `/everything-gemini-code:<name>` and emit noisy
conflict/load errors on startup.
Changes:
- Rename all 79 `commands/<name>.toml` files to `commands/egc-<name>.toml`
(plus the previously renamed egc-plan / egc-docs from the earlier commit
on this branch).
- Update every prose reference to slash-prefixed command names across
READMEs (EN / KO / ZH), docs/, workflows/, agents/, skills/, rules/,
COMMAND-AGENT-MAP, and scripts/ — replacing `/<name>` with `/egc-<name>`
only when `<name>` matches one of our commands and is not already part
of a longer identifier (path segments like `tdd-guide` or
`jira-integration` left intact).
Scope note: dynamic pm2 command patterns (`/pm2-all`, `/pm2-{port}`, etc.)
documented in workflows/pm2.md are left unchanged — they reference the
`pm2` process manager's own CLI, not our extension commands.
|
Important Review skippedToo many files! This PR contains 184 files, which is 34 over the limit of 150. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (184)
You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.