Jamkris · Jamkris · Apr 22, 2026 · Apr 22, 2026 · Apr 22, 2026
diff --git a/README.md b/README.md
@@ -129,13 +129,13 @@ Use custom commands to automate workflows (see [Full Command List](docs/en/comma
 
 ```bash
 # Plan a feature implementation
-/ecc-plan "Add user authentication with JWT"
+/egc-plan "Add user authentication with JWT"
 
 # Start Test-Driven Development workflow
-/tdd "Create a user service"
+/egc-tdd "Create a user service"
 
 # Run a code review
-/code-review
+/egc-code-review
 ```
 
 ### Agents

diff --git a/agents/chief-of-staff.md b/agents/chief-of-staff.md
@@ -144,7 +144,7 @@ gemini /schedule-reply "Reply to Sarah about the board meeting"
 
 ## Prerequisites
 
-- [Gemini CLI](https://ai.google.dev/gemini-api/docs/cli)
+- [Gemini CLI](https://ai.google.dev/gemini-api/egc-docs/cli)
 - Gmail CLI (e.g., gog by @pterm)
 - Node.js 18+ (for calendar-suggest.js)
 - Optional: Slack MCP server, Matrix bridge (LINE), Chrome + Playwright (Messenger)
diff --git a/agents/conversation-analyzer.md b/agents/conversation-analyzer.md
@@ -1,6 +1,6 @@
 ---
 name: conversation-analyzer
-description: Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Triggered by /hookify without arguments.
+description: Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Triggered by /egc-hookify without arguments.
 tools: [read_file, search_file_content]
 ---
 

diff --git a/agents/doc-updater.md b/agents/doc-updater.md
@@ -1,6 +1,6 @@
 ---
 name: doc-updater
-description: Documentation and codemap specialist. Use PROACTIVELY for updating codemaps and documentation. Runs /update-codemaps and /update-docs, generates docs/CODEMAPS/*, updates READMEs and guides.
+description: Documentation and codemap specialist. Use PROACTIVELY for updating codemaps and documentation. Runs /egc-update-codemaps and /egc-update-docs, generates docs/CODEMAPS/*, updates READMEs and guides.
 tools: ["read_file", "write_file", "run_shell_command"]
 ---
 
@@ -335,12 +335,12 @@ function findEntrypoints(files: SourceFile[]) {
 }
 ```
 
-### scripts/docs/update.ts
+### scripts/egc-docs/update.ts
 
 ```typescript
 /**
  * Update documentation from code
- * Usage: tsx scripts/docs/update.ts
+ * Usage: tsx scripts/egc-docs/update.ts
  */
 
 import * as fs from 'fs'

diff --git a/agents/e2e-runner.md b/agents/e2e-runner.md
@@ -295,7 +295,7 @@ export class MarketsPage {
 ### Example Test with Best Practices
 
 ```typescript
-// tests/e2e/markets/search.spec.ts
+// tests/egc-e2e/markets/search.spec.ts
 import { test, expect } from '@playwright/test'
 import { MarketsPage } from '../../pages/MarketsPage'
 
@@ -525,7 +525,7 @@ test('user can place trade with sufficient balance', async ({ page }) => {
 import { defineConfig, devices } from '@playwright/test'
 
 export default defineConfig({
-  testDir: './tests/e2e',
+  testDir: './tests/egc-e2e',
   fullyParallel: true,
   forbidOnly: !!process.env.CI,
   retries: process.env.CI ? 2 : 0,
@@ -682,7 +682,7 @@ use: {
 ### GitHub Actions Workflow
 
 ```yaml
-# .github/workflows/e2e.yml
+# .github/workflows/egc-e2e.yml
 name: E2E Tests
 
 on: [push, pull_request]
@@ -762,7 +762,7 @@ jobs:
 ## Failed Tests
 
 ### 1. search with special characters
-**File:** `tests/e2e/markets/search.spec.ts:45`
+**File:** `tests/egc-e2e/markets/search.spec.ts:45`
 **Error:** Expected element to be visible, but was not found
 **Screenshot:** artifacts/search-special-chars-failed.png
 **Trace:** artifacts/trace-123.zip
@@ -777,7 +777,7 @@ jobs:
 ---
 
 ### 2. user can place sell order
-**File:** `tests/e2e/trading/sell.spec.ts:28`
+**File:** `tests/egc-e2e/trading/sell.spec.ts:28`
 **Error:** Timeout waiting for API response /api/trade
 **Video:** artifacts/videos/sell-order-failed.webm
 

diff --git a/agents/harness-optimizer.md b/agents/harness-optimizer.md
@@ -12,7 +12,7 @@ Raise agent completion quality by improving harness configuration, not by rewrit
 
 ## Workflow
 
-1. Run `/harness-audit` and collect baseline score.
+1. Run `/egc-harness-audit` and collect baseline score.
 2. Identify top 3 leverage areas (hooks, evals, routing, context, safety).
 3. Propose minimal, reversible configuration changes.
 4. Apply changes and run validation.

diff --git a/agents/pytorch-build-resolver.md b/agents/pytorch-build-resolver.md
@@ -116,4 +116,4 @@ Final: `Status: SUCCESS/FAILED | Errors Fixed: N | Files Modified: list`
 
 ---
 
-For PyTorch best practices, consult the [official PyTorch documentation](https://pytorch.org/docs/stable/) and [PyTorch forums](https://discuss.pytorch.org/).
+For PyTorch best practices, consult the [official PyTorch documentation](https://pytorch.org/egc-docs/stable/) and [PyTorch forums](https://discuss.pytorch.org/).
diff --git a/commands/docs.toml b/commands/docs.toml
diff --git a/commands/agent-sort.toml → commands/egc-agent-sort.toml b/commands/agent-sort.toml → commands/egc-agent-sort.toml
@@ -2,7 +2,7 @@ description = "Legacy slash-entry shim for the agent-sort skill. Prefer the skil
 prompt = '''
 # Agent Sort (Legacy Shim)
 
-Use this only if you still invoke `/agent-sort`. The maintained workflow lives in `skills/agent-sort/SKILL.md`.
+Use this only if you still invoke `/egc-agent-sort`. The maintained workflow lives in `skills/egc-agent-sort/SKILL.md`.
 
 ## Canonical Surface
 

diff --git a/commands/aside.toml → commands/egc-aside.toml b/commands/aside.toml → commands/egc-aside.toml
@@ -19,12 +19,12 @@ Ask a question mid-task and get an immediate, focused answer — then continue r
 ## Usage
 
 ```
-/aside <your question>
-/aside what does this function actually return?
-/aside is this pattern thread-safe?
-/aside why are we using X instead of Y here?
-/aside what's the difference between foo() and bar()?
-/aside should we be worried about the N+1 query we just added?
+/egc-aside <your question>
+/egc-aside what does this function actually return?
+/egc-aside is this pattern thread-safe?
+/egc-aside why are we using X instead of Y here?
+/egc-aside what's the difference between foo() and bar()?
+/egc-aside should we be worried about the N+1 query we just added?
 ```
 
 ## Process
@@ -33,7 +33,7 @@ Ask a question mid-task and get an immediate, focused answer — then continue r
 
 Before answering anything, mentally note:
 - What is the active task? (what file, feature, or problem was being worked on)
-- What step was in progress at the moment `/aside` was invoked?
+- What step was in progress at the moment `/egc-aside` was invoked?
 - What was about to happen next?
 
 Do NOT touch, edit, create, or delete any files during the aside.
@@ -65,7 +65,7 @@ After delivering the answer, immediately continue the active task from the exact
 
 ## Edge Cases
 
-**No question provided (`/aside` with nothing after it):**
+**No question provided (`/egc-aside` with nothing after it):**
 Respond:
 ```
 ASIDE: no question provided
@@ -85,7 +85,7 @@ ASIDE: [answer]
 Wait for the user's decision before resuming.
 
 **Question is actually a task redirect (not a side question):**
-If the question implies changing what is being built (e.g., `/aside actually, let's use Redis instead`), clarify:
+If the question implies changing what is being built (e.g., `/egc-aside actually, let's use Redis instead`), clarify:
 ```
 ASIDE: That sounds like a direction change, not just a side question.
 Do you want to:
@@ -97,7 +97,7 @@ Wait for the user's answer — do not make assumptions.
 **Question is about the currently open file or code:**
 Answer from the live context. If the file was read earlier in the session, reference it directly. If not, read it now (read-only) and answer with a file:line reference.
 
-**No active task (nothing in progress when `/aside` is invoked):**
+**No active task (nothing in progress when `/egc-aside` is invoked):**
 Still use the standard wrapper so the response shape stays consistent:
 ```
 ASIDE: [restate the question briefly]
@@ -113,7 +113,7 @@ Give the essential answer concisely, then offer:
 That's the short version. Want a deeper explanation after we finish [current task]?
 ```
 
-**Multiple `/aside` questions in a row:**
+**Multiple `/egc-aside` questions in a row:**
 Answer each one in sequence. After the last answer, resume the main task. Do not lose task state across a chain of asides.
 
 **Aside answer implies a code change is needed:**
@@ -132,7 +132,7 @@ Ask one clarifying question — the shortest question that gets the information
 ## Example Output
 
 ```
-User: /aside what does fetchWithRetry() actually do?
+User: /egc-aside what does fetchWithRetry() actually do?
 
 ASIDE: what does fetchWithRetry() do?
 
@@ -144,7 +144,7 @@ network errors — 4xx errors are treated as final and not retried.
 ```
 
 ```
-User: /aside is the approach we're taking thread-safe?
+User: /egc-aside is the approach we're taking thread-safe?
 
 ASIDE: is the current approach thread-safe?
 

diff --git a/commands/build-fix.toml → commands/egc-build-fix.toml b/commands/build-fix.toml → commands/egc-build-fix.toml
diff --git a/commands/checkpoint.toml → commands/egc-checkpoint.toml b/commands/checkpoint.toml → commands/egc-checkpoint.toml
@@ -6,13 +6,13 @@ Create or verify a checkpoint in your workflow.
 
 ## Usage
 
-`/checkpoint [create|verify|list] [name]`
+`/egc-checkpoint [create|verify|list] [name]`
 
 ## Create Checkpoint
 
 When creating a checkpoint:
 
-1. Run `/verify quick` to ensure current state is clean
+1. Run `/egc-verify quick` to ensure current state is clean
 2. Create a git stash or commit with checkpoint name
 3. Log checkpoint to `.gemini/checkpoints.log`:
 
@@ -56,15 +56,15 @@ Show all checkpoints with:
 Typical checkpoint flow:
 
 ```
-[Start] --> /checkpoint create "feature-start"
+[Start] --> /egc-checkpoint create "feature-start"
    |
-[Implement] --> /checkpoint create "core-done"
+[Implement] --> /egc-checkpoint create "core-done"
    |
-[Test] --> /checkpoint verify "core-done"
+[Test] --> /egc-checkpoint verify "core-done"
    |
-[Refactor] --> /checkpoint create "refactor-done"
+[Refactor] --> /egc-checkpoint create "refactor-done"
    |
-[PR] --> /checkpoint verify "feature-start"
+[PR] --> /egc-checkpoint verify "feature-start"
 ```
 
 ## Arguments

diff --git a/commands/claw.toml → commands/egc-claw.toml b/commands/claw.toml → commands/egc-claw.toml
@@ -11,7 +11,7 @@ Start an interactive AI agent session with persistent markdown history and opera
 ## Usage
 
 ```bash
-node scripts/claw.js
+node scripts/egc-claw.js
 ```
 
 Or via npm:
@@ -34,7 +34,7 @@ npm run claw
 /help                          Show help
 /clear                         Clear current session history
 /history                       Print full conversation history
-/sessions                      List saved sessions
+/egc-sessions                      List saved sessions
 /model [name]                  Show/set model
 /load <skill-name>             Hot-load a skill into context
 /branch <session-name>         Branch current session
@@ -48,7 +48,7 @@ exit                           Quit
 ## Notes
 
 - NanoClaw remains zero-dependency.
-- Sessions are stored at `~/.gemini/claw/<session>.md`.
+- Sessions are stored at `~/.gemini/egc-claw/<session>.md`.
 - Compaction keeps the most recent turns and writes a compaction header.
 - Export supports markdown, JSON turns, and plain text.
 

diff --git a/commands/code-review.toml → commands/egc-code-review.toml b/commands/code-review.toml → commands/egc-code-review.toml
diff --git a/commands/context-budget.toml → commands/egc-context-budget.toml b/commands/context-budget.toml → commands/egc-context-budget.toml
@@ -11,7 +11,7 @@ Analyze your Gemini CLI setup's context window consumption and produce actionabl
 ## Usage
 
 ```
-/context-budget [--verbose]
+/egc-context-budget [--verbose]
 ```
 
 - Default: summary with top recommendations
@@ -21,7 +21,7 @@ $ARGUMENTS
 
 ## What to Do
 
-Run the **context-budget** skill (`skills/context-budget/SKILL.md`) with the following inputs:
+Run the **context-budget** skill (`skills/egc-context-budget/SKILL.md`) with the following inputs:
 
 1. Pass `--verbose` flag if present in `$ARGUMENTS`
 2. Assume a 1M context window (Gemini default) unless the user specifies otherwise

diff --git a/commands/cpp-build.toml → commands/egc-cpp-build.toml b/commands/cpp-build.toml → commands/egc-cpp-build.toml
@@ -18,7 +18,7 @@ This command invokes the **cpp-build-resolver** agent to incrementally fix C++ b
 
 ## When to Use
 
-Use `/cpp-build` when:
+Use `/egc-cpp-build` when:
 - `cmake --build build` fails with errors
 - Linker errors (undefined references, multiple definitions)
 - Template instantiation failures
@@ -42,7 +42,7 @@ cppcheck --enable=all src/
 ## Example Session
 
 ```text
-User: /cpp-build
+User: /egc-cpp-build
 
 Agent:
 # C++ Build Resolution
@@ -165,9 +165,9 @@ The agent will stop and report if:
 
 ## Related Commands
 
-- `/cpp-test` - Run tests after build succeeds
-- `/cpp-review` - Review code quality
-- `/verify` - Full verification loop
+- `/egc-cpp-test` - Run tests after build succeeds
+- `/egc-cpp-review` - Review code quality
+- `/egc-verify` - Full verification loop
 
 ## Related
 

diff --git a/commands/cpp-review.toml → commands/egc-cpp-review.toml b/commands/cpp-review.toml → commands/egc-cpp-review.toml
@@ -19,7 +19,7 @@ This command invokes the **cpp-reviewer** agent for comprehensive C++-specific c
 
 ## When to Use
 
-Use `/cpp-review` when:
+Use `/egc-cpp-review` when:
 - After writing or modifying C++ code
 - Before committing C++ changes
 - Reviewing pull requests with C++ code
@@ -66,7 +66,7 @@ cmake --build build -- -Wall -Wextra -Wpedantic
 ## Example Usage
 
 ```text
-User: /cpp-review
+User: /egc-cpp-review
 
 Agent:
 # C++ Code Review Report
@@ -123,10 +123,10 @@ Recommendation: ❌ Block merge until CRITICAL issue is fixed
 
 ## Integration with Other Commands
 
-- Use `/cpp-test` first to ensure tests pass
-- Use `/cpp-build` if build errors occur
-- Use `/cpp-review` before committing
-- Use `/code-review` for non-C++ specific concerns
+- Use `/egc-cpp-test` first to ensure tests pass
+- Use `/egc-cpp-build` if build errors occur
+- Use `/egc-cpp-review` before committing
+- Use `/egc-code-review` for non-C++ specific concerns
 
 ## Related
Original file line number	Diff line number	Diff line change
Expand Up		@@ -116,4 +116,4 @@ Final: `Status: SUCCESS/FAILED \| Errors Fixed: N \| Files Modified: list`

		---

		For PyTorch best practices, consult the [official PyTorch documentation](https://pytorch.org/docs/stable/) and [PyTorch forums](https://discuss.pytorch.org/).
		For PyTorch best practices, consult the [official PyTorch documentation](https://pytorch.org/egc-docs/stable/) and [PyTorch forums](https://discuss.pytorch.org/).