Skip to content

docs: note Antigravity-only bare workflow names vs Gemini CLI egc- pr…#41

Merged
Jamkris merged 1 commit intomainfrom
fix/command-name-conflicts
Apr 22, 2026
Merged

docs: note Antigravity-only bare workflow names vs Gemini CLI egc- pr…#41
Jamkris merged 1 commit intomainfrom
fix/command-name-conflicts

Conversation

@Jamkris
Copy link
Copy Markdown
Owner

@Jamkris Jamkris commented Apr 22, 2026

…efix

Only /egc-plan gets the egc- prefix under Antigravity (it would otherwise shadow Antigravity's built-in /plan). Every other workflow installed via scripts/install.sh --antigravity keeps its bare name (/tdd, /build-fix, /code-review, …). Gemini CLI still requires the prefix on every command to avoid its built-in command collisions.

Add this note to the Slash Commands section of the EN/KO/ZH READMEs so users don't assume commands were renamed everywhere.

Summary by CodeRabbit

  • Documentation
    • Added clarification on command naming conventions for Antigravity workflows, explaining that workflows use bare command names (e.g., /tdd, /code-review, /build-fix) with the exception of /egc-plan to avoid conflicts with built-in commands.
    • Updated documentation in English, Korean, and Chinese.

…efix

Only `/egc-plan` gets the `egc-` prefix under Antigravity (it would
otherwise shadow Antigravity's built-in `/plan`). Every other workflow
installed via `scripts/install.sh --antigravity` keeps its bare name
(`/tdd`, `/build-fix`, `/code-review`, …). Gemini CLI still requires
the prefix on every command to avoid its built-in command collisions.

Add this note to the Slash Commands section of the EN/KO/ZH READMEs
so users don't assume commands were renamed everywhere.
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 22, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: cf7fbae7-a7fa-4737-b0c6-37bec02bce4c

📥 Commits

Reviewing files that changed from the base of the PR and between 79a5f0b and d4c8505.

📒 Files selected for processing (3)
  • README.md
  • docs/ko-KR/README.md
  • docs/zh-CN/README.md

Walkthrough

Documentation updates adding clarification notes about Antigravity workflow command naming conventions across English, Korean, and Chinese README files. No functional changes.

Changes

Cohort / File(s) Summary
Documentation updates
README.md, docs/ko-KR/README.md, docs/zh-CN/README.md
Added notes clarifying Antigravity workflow command naming: workflows install with bare command names (e.g., /tdd, /code-review, /build-fix), except /egc-plan which uses prefix to avoid conflict with built-in /plan. Also documents Gemini CLI behavior using consistent egc- prefix.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested labels

docs

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically describes the main change: adding documentation to clarify command naming differences between Antigravity and Gemini CLI.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/command-name-conflicts

Comment @coderabbitai help to get the list of available commands and usage tips.

@Jamkris Jamkris merged commit 21071ff into main Apr 22, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant