From cc3c9eb6334b045fd4363948d969ac093d6ee228 Mon Sep 17 00:00:00 2001 From: Jamkris Date: Wed, 22 Apr 2026 15:37:11 +0900 Subject: [PATCH 1/2] fix: rename conflicting commands to egc-* and drop bare duplicates 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` --- README.md | 2 +- commands/docs.toml | 35 ------ commands/{ecc-docs.toml => egc-docs.toml} | 8 +- commands/{ecc-plan.toml => egc-plan.toml} | 4 +- commands/plan.toml | 112 ------------------ docs/en/commands/README.md | 8 +- docs/ko-KR/commands/README.md | 8 +- docs/ko-KR/contributing/COMMAND-AGENT-MAP.md | 2 +- docs/zh-CN/commands/README.md | 4 +- workflows/{ecc-plan.md => egc-plan.md} | 0 workflows/plan.md | 113 ------------------- 11 files changed, 18 insertions(+), 278 deletions(-) delete mode 100644 commands/docs.toml rename commands/{ecc-docs.toml => egc-docs.toml} (90%) rename commands/{ecc-plan.toml => egc-plan.toml} (97%) delete mode 100644 commands/plan.toml rename workflows/{ecc-plan.md => egc-plan.md} (100%) delete mode 100644 workflows/plan.md diff --git a/README.md b/README.md index 5bbf283..f7f2afa 100644 --- a/README.md +++ b/README.md @@ -129,7 +129,7 @@ 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" diff --git a/commands/docs.toml b/commands/docs.toml deleted file mode 100644 index 1f65ace..0000000 --- a/commands/docs.toml +++ /dev/null @@ -1,35 +0,0 @@ -description = '/docs' -prompt = ''' ---- -description: Look up current documentation for a library or topic via Context7. ---- - -# /docs - -## Purpose - -Look up up-to-date documentation for a library, framework, or API and return a summarized answer with relevant code snippets. Uses the Context7 MCP (resolve-library-id and query-docs) so answers reflect current docs, not training data. - -## Usage - -``` -/docs [library name] [question] -``` - -Use quotes for multi-word arguments so they are parsed as a single token. Example: `/docs "Next.js" "How do I configure middleware?"` - -If library or question is omitted, prompt the user for: -1. The library or product name (e.g. Next.js, Prisma, Supabase). -2. The specific question or task (e.g. "How do I set up middleware?", "Auth methods"). - -## Workflow - -1. **Resolve library ID** — Call the Context7 tool `resolve-library-id` with the library name and the user's question to get a Context7-compatible library ID (e.g. `/vercel/next.js`). -2. **Query docs** — Call `query-docs` with that library ID and the user's question. -3. **Summarize** — Return a concise answer and include relevant code examples from the fetched documentation. Mention the library (and version if relevant). - -## Output - -The user receives a short, accurate answer backed by current docs, plus any code snippets that help. If Context7 is not available, say so and answer from training data with a note that docs may be outdated. - -''' diff --git a/commands/ecc-docs.toml b/commands/egc-docs.toml similarity index 90% rename from commands/ecc-docs.toml rename to commands/egc-docs.toml index 963172e..baef4bb 100644 --- a/commands/ecc-docs.toml +++ b/commands/egc-docs.toml @@ -1,10 +1,10 @@ -description = '/ecc-docs' +description = '/egc-docs' prompt = ''' --- description: Look up current documentation for a library or topic via Context7. --- -# /ecc-docs +# /egc-docs ## Purpose @@ -13,10 +13,10 @@ Look up up-to-date documentation for a library, framework, or API and return a s ## Usage ``` -/ecc-docs [library name] [question] +/egc-docs [library name] [question] ``` -Use quotes for multi-word arguments so they are parsed as a single token. Example: `/ecc-docs "Next.js" "How do I configure middleware?"` +Use quotes for multi-word arguments so they are parsed as a single token. Example: `/egc-docs "Next.js" "How do I configure middleware?"` If library or question is omitted, prompt the user for: 1. The library or product name (e.g. Next.js, Prisma, Supabase). diff --git a/commands/ecc-plan.toml b/commands/egc-plan.toml similarity index 97% rename from commands/ecc-plan.toml rename to commands/egc-plan.toml index 11a29ae..71396ed 100644 --- a/commands/ecc-plan.toml +++ b/commands/egc-plan.toml @@ -13,7 +13,7 @@ This command invokes the **planner** agent to create a comprehensive implementat ## When to Use -Use `/ecc-plan` when: +Use `/egc-plan` when: - Starting a new feature - Making significant architectural changes - Working on complex refactoring @@ -34,7 +34,7 @@ The planner agent will: ## Example Usage ``` -User: /ecc-plan I need to add real-time notifications when markets resolve +User: /egc-plan I need to add real-time notifications when markets resolve Agent (planner): # Implementation Plan: Real-Time Market Resolution Notifications diff --git a/commands/plan.toml b/commands/plan.toml deleted file mode 100644 index 89b9206..0000000 --- a/commands/plan.toml +++ /dev/null @@ -1,112 +0,0 @@ -description = "Restate requirements, assess risks, and create step-by-step implementation plan. WAIT for user CONFIRM before touching any code." -prompt = ''' -# Plan Command - -This command invokes the **planner** agent to create a comprehensive implementation plan before writing any code. - -## What This Command Does - -1. **Restate Requirements** - Clarify what needs to be built -2. **Identify Risks** - Surface potential issues and blockers -3. **Create Step Plan** - Break down implementation into phases -4. **Wait for Confirmation** - MUST receive user approval before proceeding - -## When to Use - -Use `/plan` when: -- Starting a new feature -- Making significant architectural changes -- Working on complex refactoring -- Multiple files/components will be affected -- Requirements are unclear or ambiguous - -## How It Works - -The planner agent will: - -1. **Analyze the request** and restate requirements in clear terms -2. **Break down into phases** with specific, actionable steps -3. **Identify dependencies** between components -4. **Assess risks** and potential blockers -5. **Estimate complexity** (High/Medium/Low) -6. **Present the plan** and WAIT for your explicit confirmation - -## Example Usage - -``` -User: /plan I need to add real-time notifications when markets resolve - -Agent (planner): -# Implementation Plan: Real-Time Market Resolution Notifications - -## Requirements Restatement -- Send notifications to users when markets they're watching resolve -- Support multiple notification channels (in-app, email, webhook) -- Ensure notifications are delivered reliably -- Include market outcome and user's position result - -## Implementation Phases - -### Phase 1: Database Schema -- Add notifications table with columns: id, user_id, market_id, type, status, created_at -- Add user_notification_preferences table for channel preferences -- Create indexes on user_id and market_id for performance - -### Phase 2: Notification Service -- Create notification service in lib/notifications.ts -- Implement notification queue using BullMQ/Redis -- Add retry logic for failed deliveries -- Create notification templates - -### Phase 3: Integration Points -- Hook into market resolution logic (when status changes to "resolved") -- Query all users with positions in market -- Enqueue notifications for each user - -### Phase 4: Frontend Components -- Create NotificationBell component in header -- Add NotificationList modal -- Implement real-time updates via Supabase subscriptions -- Add notification preferences page - -## Dependencies -- Redis (for queue) -- Email service (SendGrid/Resend) -- Supabase real-time subscriptions - -## Risks -- HIGH: Email deliverability (SPF/DKIM required) -- MEDIUM: Performance with 1000+ users per market -- MEDIUM: Notification spam if markets resolve frequently -- LOW: Real-time subscription overhead - -## Estimated Complexity: MEDIUM -- Backend: 4-6 hours -- Frontend: 3-4 hours -- Testing: 2-3 hours -- Total: 9-13 hours - -**WAITING FOR CONFIRMATION**: Proceed with this plan? (yes/no/modify) -``` - -## Important Notes - -**CRITICAL**: The planner agent will **NOT** write any code until you explicitly confirm the plan with "yes" or "proceed" or similar affirmative response. - -If you want changes, respond with: -- "modify: [your changes]" -- "different approach: [alternative]" -- "skip phase 2 and do phase 3 first" - -## Integration with Other Commands - -After planning: -- Use `/tdd` to implement with test-driven development -- Use `/build-and-fix` if build errors occur -- Use `/code-review` to review completed implementation - -## Related Agents - -This command invokes the `planner` agent located at: -`~/.gemini/agents/planner.md` -''' diff --git a/docs/en/commands/README.md b/docs/en/commands/README.md index ac77212..003f65d 100644 --- a/docs/en/commands/README.md +++ b/docs/en/commands/README.md @@ -11,8 +11,8 @@ List of available commands provided by `everything-gemini-code`. | `/checkpoint` | Stage all changes and commit them with an AI-generated message. | | `/code-review` | Comprehensive code review of the current changes or specific files using the `code-reviewer` agent. | | `/e2e` | Generate and run end-to-end tests with Playwright. | -| `/ecc-plan` | Restate requirements, assess risks, and create step-by-step implementation plan. (alias: `/everything-gemini-code:plan`) | -| `/ecc-docs` | Look up current documentation for a library or topic via Context7. (alias: `/everything-gemini-code:docs`) | +| `/egc-plan` | Restate requirements, assess risks, and create step-by-step implementation plan. (alias: `/everything-gemini-code:plan`) | +| `/egc-docs` | Look up current documentation for a library or topic via Context7. (alias: `/everything-gemini-code:docs`) | | `/eval` | Manage eval-driven development workflow. | | `/evolve` | Cluster related instincts into skills, commands, or agents. | | `/feature-dev` | Guided feature development with codebase understanding. | @@ -62,7 +62,7 @@ List of available commands provided by `everything-gemini-code`. ## Core Commands -### /ecc-plan +### /egc-plan Restate requirements, assess risks, and create step-by-step implementation plan. WAIT for user CONFIRM before touching any code. @@ -202,7 +202,7 @@ Verification suite, workflow checkpoints, and eval-driven development. Session management - list, save, load, and alias sessions. -### /ecc-docs +### /egc-docs Look up current documentation for a library or topic via Context7. diff --git a/docs/ko-KR/commands/README.md b/docs/ko-KR/commands/README.md index 940a5d9..400e418 100644 --- a/docs/ko-KR/commands/README.md +++ b/docs/ko-KR/commands/README.md @@ -11,8 +11,8 @@ | `/checkpoint` | 모든 변경 사항을 스테이징하고 AI 생성 메시지로 커밋합니다. | | `/code-review` | `code-reviewer` 에이전트를 사용하여 현재 변경 사항에 대한 종합 코드 리뷰를 수행합니다. | | `/e2e` | Playwright로 E2E 테스트를 생성하고 실행합니다. | -| `/ecc-plan` | 요구 사항을 재검토하고 단계별 구현 계획을 수립합니다. (별칭: `/everything-gemini-code:plan`) | -| `/ecc-docs` | Context7을 통해 라이브러리 또는 주제의 최신 문서를 조회합니다. (별칭: `/everything-gemini-code:docs`) | +| `/egc-plan` | 요구 사항을 재검토하고 단계별 구현 계획을 수립합니다. (별칭: `/everything-gemini-code:plan`) | +| `/egc-docs` | Context7을 통해 라이브러리 또는 주제의 최신 문서를 조회합니다. (별칭: `/everything-gemini-code:docs`) | | `/eval` | Eval 기반 개발 워크플로우를 관리합니다. | | `/evolve` | 관련 인스팅트를 스킬, 커맨드 또는 에이전트로 클러스터링합니다. | | `/feature-dev` | 코드베이스 이해 기반 가이드 기능 개발. | @@ -62,7 +62,7 @@ ## 핵심 커맨드 -### /ecc-plan +### /egc-plan 요구 사항을 재검토하고, 위험을 평가하며, 단계별 구현 계획을 수립합니다. 코드 작성 전 사용자 확인을 기다립니다. @@ -194,7 +194,7 @@ Gradle/Android 빌드 오류 및 의존성 문제 수정. 세션 관리 — 나열, 저장, 불러오기, 별칭 설정. -### /ecc-docs +### /egc-docs Context7을 통해 라이브러리 또는 주제의 최신 문서를 조회합니다. diff --git a/docs/ko-KR/contributing/COMMAND-AGENT-MAP.md b/docs/ko-KR/contributing/COMMAND-AGENT-MAP.md index f1a16ff..776297f 100644 --- a/docs/ko-KR/contributing/COMMAND-AGENT-MAP.md +++ b/docs/ko-KR/contributing/COMMAND-AGENT-MAP.md @@ -6,7 +6,7 @@ | 커맨드 | 사용 에이전트 | 설명 | |--------|-------------|------| -| `/ecc-plan` | planner | 기능 구현 계획 수립 | +| `/egc-plan` | planner | 기능 구현 계획 수립 | | `/tdd` | tdd-guide | 테스트 주도 개발 | | `/code-review` | code-reviewer | 코드 품질 리뷰 | | `/build-fix` | build-error-resolver | 빌드 오류 수정 | diff --git a/docs/zh-CN/commands/README.md b/docs/zh-CN/commands/README.md index 0191c85..c3f03b1 100644 --- a/docs/zh-CN/commands/README.md +++ b/docs/zh-CN/commands/README.md @@ -10,8 +10,8 @@ | `/checkpoint` | 暂存所有更改并使用 AI 生成的消息提交。 | | `/code-review` | 使用 `code-reviewer` 代理对当前更改进行全面代码审查。 | | `/e2e` | 使用 Playwright 生成并运行端到端测试。 | -| `/ecc-plan` | 重述需求、评估风险并制定分步实施计划。(别名: `/everything-gemini-code:plan`) | -| `/ecc-docs` | 通过 Context7 查找库或主题的最新文档。(别名: `/everything-gemini-code:docs`) | +| `/egc-plan` | 重述需求、评估风险并制定分步实施计划。(别名: `/everything-gemini-code:plan`) | +| `/egc-docs` | 通过 Context7 查找库或主题的最新文档。(别名: `/everything-gemini-code:docs`) | | `/eval` | 管理 eval 驱动的开发工作流。 | | `/evolve` | 将相关直觉聚类为技能、命令或代理。 | | `/go-build` | 逐步修复 Go 构建错误、go vet 警告和 linter 问题。 | diff --git a/workflows/ecc-plan.md b/workflows/egc-plan.md similarity index 100% rename from workflows/ecc-plan.md rename to workflows/egc-plan.md diff --git a/workflows/plan.md b/workflows/plan.md deleted file mode 100644 index 792d3e6..0000000 --- a/workflows/plan.md +++ /dev/null @@ -1,113 +0,0 @@ ---- -description: Restate requirements, assess risks, and create step-by-step implementation plan. WAIT for user CONFIRM before touching any code. ---- - -# Plan Command - -This command invokes the **planner** agent to create a comprehensive implementation plan before writing any code. - -## What This Command Does - -1. **Restate Requirements** - Clarify what needs to be built -2. **Identify Risks** - Surface potential issues and blockers -3. **Create Step Plan** - Break down implementation into phases -4. **Wait for Confirmation** - MUST receive user approval before proceeding - -## When to Use - -Use `/plan` when: -- Starting a new feature -- Making significant architectural changes -- Working on complex refactoring -- Multiple files/components will be affected -- Requirements are unclear or ambiguous - -## How It Works - -The planner agent will: - -1. **Analyze the request** and restate requirements in clear terms -2. **Break down into phases** with specific, actionable steps -3. **Identify dependencies** between components -4. **Assess risks** and potential blockers -5. **Estimate complexity** (High/Medium/Low) -6. **Present the plan** and WAIT for your explicit confirmation - -## Example Usage - -``` -User: /plan I need to add real-time notifications when markets resolve - -Agent (planner): -# Implementation Plan: Real-Time Market Resolution Notifications - -## Requirements Restatement -- Send notifications to users when markets they're watching resolve -- Support multiple notification channels (in-app, email, webhook) -- Ensure notifications are delivered reliably -- Include market outcome and user's position result - -## Implementation Phases - -### Phase 1: Database Schema -- Add notifications table with columns: id, user_id, market_id, type, status, created_at -- Add user_notification_preferences table for channel preferences -- Create indexes on user_id and market_id for performance - -### Phase 2: Notification Service -- Create notification service in lib/notifications.ts -- Implement notification queue using BullMQ/Redis -- Add retry logic for failed deliveries -- Create notification templates - -### Phase 3: Integration Points -- Hook into market resolution logic (when status changes to "resolved") -- Query all users with positions in market -- Enqueue notifications for each user - -### Phase 4: Frontend Components -- Create NotificationBell component in header -- Add NotificationList modal -- Implement real-time updates via Supabase subscriptions -- Add notification preferences page - -## Dependencies -- Redis (for queue) -- Email service (SendGrid/Resend) -- Supabase real-time subscriptions - -## Risks -- HIGH: Email deliverability (SPF/DKIM required) -- MEDIUM: Performance with 1000+ users per market -- MEDIUM: Notification spam if markets resolve frequently -- LOW: Real-time subscription overhead - -## Estimated Complexity: MEDIUM -- Backend: 4-6 hours -- Frontend: 3-4 hours -- Testing: 2-3 hours -- Total: 9-13 hours - -**WAITING FOR CONFIRMATION**: Proceed with this plan? (yes/no/modify) -``` - -## Important Notes - -**CRITICAL**: The planner agent will **NOT** write any code until you explicitly confirm the plan with "yes" or "proceed" or similar affirmative response. - -If you want changes, respond with: -- "modify: [your changes]" -- "different approach: [alternative]" -- "skip phase 2 and do phase 3 first" - -## Integration with Other Commands - -After planning: -- Use `/tdd` to implement with test-driven development -- Use `/build-and-fix` if build errors occur -- Use `/code-review` to review completed implementation - -## Related Agents - -This command invokes the `planner` agent located at: -`~/.gemini/agents/planner.md` From 474d2a8bff44d8e976c0d23ee3190cdeb0d7c844 Mon Sep 17 00:00:00 2001 From: Jamkris Date: Wed, 22 Apr 2026 15:43:14 +0900 Subject: [PATCH 2/2] refactor: prefix all extension commands with egc- to avoid name conflicts MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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:` and emit noisy conflict/load errors on startup. Changes: - Rename all 79 `commands/.toml` files to `commands/egc-.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 `/` with `/egc-` only when `` 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. --- README.md | 4 +- agents/chief-of-staff.md | 2 +- agents/conversation-analyzer.md | 2 +- agents/doc-updater.md | 6 +- agents/e2e-runner.md | 10 +- agents/harness-optimizer.md | 2 +- agents/pytorch-build-resolver.md | 2 +- .../{agent-sort.toml => egc-agent-sort.toml} | 2 +- commands/{aside.toml => egc-aside.toml} | 26 +-- .../{build-fix.toml => egc-build-fix.toml} | 0 .../{checkpoint.toml => egc-checkpoint.toml} | 14 +- commands/{claw.toml => egc-claw.toml} | 6 +- ...{code-review.toml => egc-code-review.toml} | 0 ...xt-budget.toml => egc-context-budget.toml} | 4 +- .../{cpp-build.toml => egc-cpp-build.toml} | 10 +- .../{cpp-review.toml => egc-cpp-review.toml} | 12 +- commands/{cpp-test.toml => egc-cpp-test.toml} | 10 +- commands/{devfleet.toml => egc-devfleet.toml} | 0 commands/{e2e.toml => egc-e2e.toml} | 22 +-- commands/{eval.toml => egc-eval.toml} | 10 +- commands/{evolve.toml => egc-evolve.toml} | 10 +- ...{feature-dev.toml => egc-feature-dev.toml} | 8 +- ...tter-build.toml => egc-flutter-build.toml} | 10 +- ...er-review.toml => egc-flutter-review.toml} | 16 +- ...lutter-test.toml => egc-flutter-test.toml} | 12 +- .../{gan-build.toml => egc-gan-build.toml} | 6 +- .../{gan-design.toml => egc-gan-design.toml} | 4 +- commands/{go-build.toml => egc-go-build.toml} | 10 +- .../{go-review.toml => egc-go-review.toml} | 12 +- commands/{go-test.toml => egc-go-test.toml} | 10 +- ...radle-build.toml => egc-gradle-build.toml} | 0 ...ness-audit.toml => egc-harness-audit.toml} | 6 +- ...figure.toml => egc-hookify-configure.toml} | 2 +- ...ookify-help.toml => egc-hookify-help.toml} | 8 +- ...ookify-list.toml => egc-hookify-list.toml} | 4 +- commands/{hookify.toml => egc-hookify.toml} | 6 +- ...t-export.toml => egc-instinct-export.toml} | 8 +- ...t-import.toml => egc-instinct-import.toml} | 10 +- ...t-status.toml => egc-instinct-status.toml} | 6 +- commands/{jira.toml => egc-jira.toml} | 30 +-- ...otlin-build.toml => egc-kotlin-build.toml} | 10 +- ...lin-review.toml => egc-kotlin-review.toml} | 12 +- ...{kotlin-test.toml => egc-kotlin-test.toml} | 10 +- .../{learn-eval.toml => egc-learn-eval.toml} | 6 +- commands/{learn.toml => egc-learn.toml} | 4 +- .../{loop-start.toml => egc-loop-start.toml} | 2 +- ...{loop-status.toml => egc-loop-status.toml} | 2 +- ...{model-route.toml => egc-model-route.toml} | 2 +- ...ti-backend.toml => egc-multi-backend.toml} | 2 +- ...ti-execute.toml => egc-multi-execute.toml} | 6 +- ...-frontend.toml => egc-multi-frontend.toml} | 2 +- .../{multi-plan.toml => egc-multi-plan.toml} | 16 +- ...-workflow.toml => egc-multi-workflow.toml} | 4 +- ...{orchestrate.toml => egc-orchestrate.toml} | 10 +- commands/egc-plan.toml | 4 +- commands/{pm2.toml => egc-pm2.toml} | 0 commands/{projects.toml => egc-projects.toml} | 4 +- commands/{promote.toml => egc-promote.toml} | 8 +- ...optimize.toml => egc-prompt-optimize.toml} | 6 +- .../{prp-commit.toml => egc-prp-commit.toml} | 16 +- ...-implement.toml => egc-prp-implement.toml} | 16 +- commands/{prp-plan.toml => egc-prp-plan.toml} | 8 +- commands/{prp-pr.toml => egc-prp-pr.toml} | 4 +- commands/{prp-prd.toml => egc-prp-prd.toml} | 8 +- commands/{prune.toml => egc-prune.toml} | 6 +- ...hon-review.toml => egc-python-review.toml} | 10 +- ...uality-gate.toml => egc-quality-gate.toml} | 2 +- ...tor-clean.toml => egc-refactor-clean.toml} | 0 ...e-session.toml => egc-resume-session.toml} | 26 +-- .../{review-pr.toml => egc-review-pr.toml} | 6 +- ...es-distill.toml => egc-rules-distill.toml} | 4 +- .../{rust-build.toml => egc-rust-build.toml} | 10 +- ...{rust-review.toml => egc-rust-review.toml} | 12 +- .../{rust-test.toml => egc-rust-test.toml} | 10 +- .../{santa-loop.toml => egc-santa-loop.toml} | 2 +- ...ave-session.toml => egc-save-session.toml} | 10 +- commands/{sessions.toml => egc-sessions.toml} | 60 +++--- commands/{setup-pm.toml => egc-setup-pm.toml} | 0 ...kill-create.toml => egc-skill-create.toml} | 18 +- ...kill-health.toml => egc-skill-health.toml} | 8 +- commands/{tdd.toml => egc-tdd.toml} | 14 +- ...t-coverage.toml => egc-test-coverage.toml} | 0 ...codemaps.toml => egc-update-codemaps.toml} | 0 ...{update-docs.toml => egc-update-docs.toml} | 0 commands/{verify.toml => egc-verify.toml} | 0 docs/en/commands/README.md | 176 +++++++++--------- docs/en/contributing/COMMAND-AGENT-MAP.md | 52 +++--- .../en/contributing/SKILL-PLACEMENT-POLICY.md | 4 +- docs/en/contributing/VERIFICATION_GUIDE.md | 12 +- docs/en/contributing/token-optimization.md | 14 +- docs/en/scripts/README.md | 2 +- docs/ko-KR/README.md | 52 +++--- docs/ko-KR/commands/README.md | 172 ++++++++--------- docs/ko-KR/contributing/COMMAND-AGENT-MAP.md | 50 ++--- .../contributing/SKILL-PLACEMENT-POLICY.md | 4 +- docs/ko-KR/contributing/VERIFICATION_GUIDE.md | 8 +- docs/ko-KR/contributing/token-optimization.md | 14 +- docs/ko-KR/scripts/README.md | 2 +- docs/zh-CN/README.md | 8 +- docs/zh-CN/commands/README.md | 60 +++--- examples/GEMINI.md | 8 +- examples/statusline.json | 2 +- mcp-configs/README.md | 4 +- mcp-configs/mcp-servers.json | 2 +- scripts/generate-docs.js | 2 +- scripts/harness-audit.js | 14 +- scripts/hooks/session-start.js | 2 +- scripts/lib/session-manager.js | 2 +- scripts/setup-package-manager.js | 2 +- scripts/skill-create-output.js | 8 +- skills/autonomous-agent-harness/SKILL.md | 6 +- skills/autonomous-loops/SKILL.md | 12 +- skills/context-budget/SKILL.md | 6 +- skills/continuous-agent-loop/SKILL.md | 4 +- skills/continuous-learning-v2/SKILL.md | 18 +- skills/continuous-learning/SKILL.md | 2 +- skills/council/SKILL.md | 2 +- skills/dart-flutter-patterns/SKILL.md | 2 +- skills/design-system/SKILL.md | 2 +- skills/dmux-workflows/SKILL.md | 2 +- skills/e2e-testing/SKILL.md | 6 +- skills/eval-harness/SKILL.md | 8 +- skills/flutter-dart-code-review/SKILL.md | 14 +- skills/hookify-rules/SKILL.md | 12 +- skills/knowledge-ops/SKILL.md | 6 +- skills/kotlin-patterns/SKILL.md | 2 +- skills/laravel-patterns/SKILL.md | 2 +- skills/laravel-security/SKILL.md | 2 +- skills/laravel-tdd/SKILL.md | 10 +- skills/nanoclaw-repl/SKILL.md | 2 +- skills/prompt-optimizer/SKILL.md | 72 +++---- skills/pytorch-patterns/SKILL.md | 2 +- .../remotion-video-creation/rules/tailwind.md | 2 +- .../rules/transcribe-captions.md | 6 +- skills/rules-distill/SKILL.md | 6 +- skills/security-review/SKILL.md | 4 +- .../cloud-infrastructure-security.md | 2 +- skills/token-budget-advisor/SKILL.md | 2 +- skills/verification-loop/SKILL.md | 2 +- skills/video-editing/SKILL.md | 2 +- skills/videodb/reference/capture-reference.md | 2 +- .../videodb/reference/rtstream-reference.md | 2 +- workflows/agent-sort.md | 2 +- workflows/checkpoint.md | 14 +- workflows/e2e.md | 22 +-- workflows/egc-plan.md | 8 +- workflows/eval.md | 10 +- workflows/evolve.md | 10 +- workflows/flutter-build.md | 10 +- workflows/flutter-review.md | 16 +- workflows/flutter-test.md | 12 +- workflows/go-build.md | 10 +- workflows/go-review.md | 12 +- workflows/go-test.md | 10 +- workflows/hookify-configure.md | 2 +- workflows/hookify-help.md | 8 +- workflows/hookify-list.md | 4 +- workflows/hookify.md | 6 +- workflows/instinct-export.md | 10 +- workflows/instinct-import.md | 10 +- workflows/instinct-status.md | 6 +- workflows/jira.md | 30 +-- workflows/learn.md | 4 +- workflows/multi-backend.md | 2 +- workflows/multi-execute.md | 6 +- workflows/multi-frontend.md | 2 +- workflows/multi-plan.md | 16 +- workflows/multi-workflow.md | 2 +- workflows/orchestrate.md | 6 +- workflows/prp-commit.md | 16 +- workflows/prp-implement.md | 18 +- workflows/prp-plan.md | 8 +- workflows/prp-pr.md | 4 +- workflows/prp-prd.md | 8 +- workflows/python-review.md | 10 +- workflows/review-pr.md | 2 +- workflows/santa-loop.md | 2 +- workflows/sessions.md | 54 +++--- workflows/skill-create.md | 18 +- workflows/tdd.md | 14 +- 180 files changed, 993 insertions(+), 993 deletions(-) rename commands/{agent-sort.toml => egc-agent-sort.toml} (81%) rename commands/{aside.toml => egc-aside.toml} (87%) rename commands/{build-fix.toml => egc-build-fix.toml} (100%) rename commands/{checkpoint.toml => egc-checkpoint.toml} (78%) rename commands/{claw.toml => egc-claw.toml} (91%) rename commands/{code-review.toml => egc-code-review.toml} (100%) rename commands/{context-budget.toml => egc-context-budget.toml} (87%) rename commands/{cpp-build.toml => egc-cpp-build.toml} (95%) rename commands/{cpp-review.toml => egc-cpp-review.toml} (93%) rename commands/{cpp-test.toml => egc-cpp-test.toml} (96%) rename commands/{devfleet.toml => egc-devfleet.toml} (100%) rename commands/{e2e.toml => egc-e2e.toml} (94%) rename commands/{eval.toml => egc-eval.toml} (92%) rename commands/{evolve.toml => egc-evolve.toml} (93%) rename commands/{feature-dev.toml => egc-feature-dev.toml} (86%) rename commands/{flutter-build.toml => egc-flutter-build.toml} (95%) rename commands/{flutter-review.toml => egc-flutter-review.toml} (89%) rename commands/{flutter-test.toml => egc-flutter-test.toml} (92%) rename commands/{gan-build.toml => egc-gan-build.toml} (95%) rename commands/{gan-design.toml => egc-gan-design.toml} (95%) rename commands/{go-build.toml => egc-go-build.toml} (95%) rename commands/{go-review.toml => egc-go-review.toml} (93%) rename commands/{go-test.toml => egc-go-test.toml} (96%) rename commands/{gradle-build.toml => egc-gradle-build.toml} (100%) rename commands/{harness-audit.toml => egc-harness-audit.toml} (88%) rename commands/{hookify-configure.toml => egc-hookify-configure.toml} (87%) rename commands/{hookify-help.toml => egc-hookify-help.toml} (77%) rename commands/{hookify-list.toml => egc-hookify-list.toml} (70%) rename commands/{hookify.toml => egc-hookify.toml} (81%) rename commands/{instinct-export.toml => egc-instinct-export.toml} (86%) rename commands/{instinct-import.toml => egc-instinct-import.toml} (92%) rename commands/{instinct-status.toml => egc-instinct-status.toml} (95%) rename commands/{jira.toml => egc-jira.toml} (74%) rename commands/{kotlin-build.toml => egc-kotlin-build.toml} (95%) rename commands/{kotlin-review.toml => egc-kotlin-review.toml} (92%) rename commands/{kotlin-test.toml => egc-kotlin-test.toml} (96%) rename commands/{learn-eval.toml => egc-learn-eval.toml} (95%) rename commands/{learn.toml => egc-learn.toml} (92%) rename commands/{loop-start.toml => egc-loop-start.toml} (95%) rename commands/{loop-status.toml => egc-loop-status.toml} (94%) rename commands/{model-route.toml => egc-model-route.toml} (90%) rename commands/{multi-backend.toml => egc-multi-backend.toml} (98%) rename commands/{multi-execute.toml => egc-multi-execute.toml} (98%) rename commands/{multi-frontend.toml => egc-multi-frontend.toml} (98%) rename commands/{multi-plan.toml => egc-multi-plan.toml} (93%) rename commands/{multi-workflow.toml => egc-multi-workflow.toml} (97%) rename commands/{orchestrate.toml => egc-orchestrate.toml} (94%) rename commands/{pm2.toml => egc-pm2.toml} (100%) rename commands/{projects.toml => egc-projects.toml} (93%) rename commands/{promote.toml => egc-promote.toml} (76%) rename commands/{prompt-optimize.toml => egc-prompt-optimize.toml} (89%) rename commands/{prp-commit.toml => egc-prp-commit.toml} (82%) rename commands/{prp-implement.toml => egc-prp-implement.toml} (94%) rename commands/{prp-plan.toml => egc-prp-plan.toml} (97%) rename commands/{prp-pr.toml => egc-prp-pr.toml} (97%) rename commands/{prp-prd.toml => egc-prp-prd.toml} (97%) rename commands/{prune.toml => egc-prune.toml} (77%) rename commands/{python-review.toml => egc-python-review.toml} (96%) rename commands/{quality-gate.toml => egc-quality-gate.toml} (92%) rename commands/{refactor-clean.toml => egc-refactor-clean.toml} (100%) rename commands/{resume-session.toml => egc-resume-session.toml} (81%) rename commands/{review-pr.toml => egc-review-pr.toml} (84%) rename commands/{rules-distill.toml => egc-rules-distill.toml} (65%) rename commands/{rust-build.toml => egc-rust-build.toml} (95%) rename commands/{rust-review.toml => egc-rust-review.toml} (93%) rename commands/{rust-test.toml => egc-rust-test.toml} (96%) rename commands/{santa-loop.toml => egc-santa-loop.toml} (99%) rename commands/{save-session.toml => egc-save-session.toml} (95%) rename commands/{sessions.toml => egc-sessions.toml} (87%) rename commands/{setup-pm.toml => egc-setup-pm.toml} (100%) rename commands/{skill-create.toml => egc-skill-create.toml} (87%) rename commands/{skill-health.toml => egc-skill-health.toml} (92%) rename commands/{tdd.toml => egc-tdd.toml} (96%) rename commands/{test-coverage.toml => egc-test-coverage.toml} (100%) rename commands/{update-codemaps.toml => egc-update-codemaps.toml} (100%) rename commands/{update-docs.toml => egc-update-docs.toml} (100%) rename commands/{verify.toml => egc-verify.toml} (100%) diff --git a/README.md b/README.md index f7f2afa..7d7a09e 100644 --- a/README.md +++ b/README.md @@ -132,10 +132,10 @@ Use custom commands to automate workflows (see [Full Command List](docs/en/comma /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 index 0d443f9..4f655cd 100644 --- 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 index 54e3b6b..6ee51eb 100644 --- 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 index 6ceaa57..d376de1 100644 --- 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 index 7dc9889..f9b9c6d 100644 --- 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 index 3f2e9c6..552cef5 100644 --- 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 index 7ab1fab..859233c 100644 --- 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/agent-sort.toml b/commands/egc-agent-sort.toml similarity index 81% rename from commands/agent-sort.toml rename to commands/egc-agent-sort.toml index bef4762..732d6da 100644 --- a/commands/agent-sort.toml +++ b/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 b/commands/egc-aside.toml similarity index 87% rename from commands/aside.toml rename to commands/egc-aside.toml index 9481be0..87e27a5 100644 --- a/commands/aside.toml +++ b/commands/egc-aside.toml @@ -19,12 +19,12 @@ Ask a question mid-task and get an immediate, focused answer — then continue r ## Usage ``` -/aside -/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 +/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 b/commands/egc-build-fix.toml similarity index 100% rename from commands/build-fix.toml rename to commands/egc-build-fix.toml diff --git a/commands/checkpoint.toml b/commands/egc-checkpoint.toml similarity index 78% rename from commands/checkpoint.toml rename to commands/egc-checkpoint.toml index ae000c1..3d1e9c3 100644 --- a/commands/checkpoint.toml +++ b/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 b/commands/egc-claw.toml similarity index 91% rename from commands/claw.toml rename to commands/egc-claw.toml index 3729479..ae44236 100644 --- a/commands/claw.toml +++ b/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 Hot-load a skill into context /branch Branch current session @@ -48,7 +48,7 @@ exit Quit ## Notes - NanoClaw remains zero-dependency. -- Sessions are stored at `~/.gemini/claw/.md`. +- Sessions are stored at `~/.gemini/egc-claw/.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 b/commands/egc-code-review.toml similarity index 100% rename from commands/code-review.toml rename to commands/egc-code-review.toml diff --git a/commands/context-budget.toml b/commands/egc-context-budget.toml similarity index 87% rename from commands/context-budget.toml rename to commands/egc-context-budget.toml index 2a0d25f..cbc1899 100644 --- a/commands/context-budget.toml +++ b/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 b/commands/egc-cpp-build.toml similarity index 95% rename from commands/cpp-build.toml rename to commands/egc-cpp-build.toml index 68cb816..0f45c2e 100644 --- a/commands/cpp-build.toml +++ b/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 b/commands/egc-cpp-review.toml similarity index 93% rename from commands/cpp-review.toml rename to commands/egc-cpp-review.toml index 254c37f..a1ca15b 100644 --- a/commands/cpp-review.toml +++ b/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 diff --git a/commands/cpp-test.toml b/commands/egc-cpp-test.toml similarity index 96% rename from commands/cpp-test.toml rename to commands/egc-cpp-test.toml index dc7e473..bb66548 100644 --- a/commands/cpp-test.toml +++ b/commands/egc-cpp-test.toml @@ -19,7 +19,7 @@ This command enforces test-driven development methodology for C++ code using Goo ## When to Use -Use `/cpp-test` when: +Use `/egc-cpp-test` when: - Implementing new C++ functions or classes - Adding test coverage to existing code - Fixing bugs (write failing test first) @@ -38,7 +38,7 @@ REPEAT → Next test case ## Example Session ```` -User: /cpp-test I need a function to validate email addresses +User: /egc-cpp-test I need a function to validate email addresses Agent: # TDD Session: Email Validator @@ -243,9 +243,9 @@ genhtml coverage.info --output-directory coverage_html ## Related Commands -- `/cpp-build` - Fix build errors -- `/cpp-review` - Review code after implementation -- `/verify` - Run full verification loop +- `/egc-cpp-build` - Fix build errors +- `/egc-cpp-review` - Review code after implementation +- `/egc-verify` - Run full verification loop ## Related diff --git a/commands/devfleet.toml b/commands/egc-devfleet.toml similarity index 100% rename from commands/devfleet.toml rename to commands/egc-devfleet.toml diff --git a/commands/e2e.toml b/commands/egc-e2e.toml similarity index 94% rename from commands/e2e.toml rename to commands/egc-e2e.toml index 2759bfd..2bd55a0 100644 --- a/commands/e2e.toml +++ b/commands/egc-e2e.toml @@ -14,7 +14,7 @@ This command invokes the **e2e-runner** agent to generate, maintain, and execute ## When to Use -Use `/e2e` when: +Use `/egc-e2e` when: - Testing critical user journeys (login, trading, payments) - Verifying multi-step flows work end-to-end - Testing UI interactions and navigation @@ -35,7 +35,7 @@ The e2e-runner agent will: ## Example Usage ``` -User: /e2e Test the market search and view flow +User: /egc-e2e Test the market search and view flow Agent (e2e-runner): # E2E Test Generation: Market Search and View Flow @@ -55,7 +55,7 @@ Agent (e2e-runner): ## Generated Test Code ```typescript -// tests/e2e/markets/search-and-view.spec.ts +// tests/egc-e2e/markets/search-and-view.spec.ts import { test, expect } from '@playwright/test' import { MarketsPage } from '../../pages/MarketsPage' import { MarketDetailsPage } from '../../pages/MarketDetailsPage' @@ -158,7 +158,7 @@ test.describe('Market Search and View Flow', () => { ```bash # Run the generated test -npx playwright test tests/e2e/markets/search-and-view.spec.ts +npx playwright test tests/egc-e2e/markets/search-and-view.spec.ts Running 3 tests using 3 workers @@ -233,7 +233,7 @@ open artifacts/search-results.png If a test fails intermittently: ``` -⚠️ FLAKY TEST DETECTED: tests/e2e/markets/trade.spec.ts +⚠️ FLAKY TEST DETECTED: tests/egc-e2e/markets/trade.spec.ts Test passed 7/10 runs (70% pass rate) @@ -264,7 +264,7 @@ Configure in `playwright.config.ts` to adjust browsers. Add to your CI pipeline: ```yaml -# .github/workflows/e2e.yml +# .github/workflows/egc-e2e.yml - name: Install Playwright run: npx playwright install --with-deps @@ -328,10 +328,10 @@ For PMX, prioritize these E2E tests: ## Integration with Other Commands -- Use `/plan` to identify critical journeys to test -- Use `/tdd` for unit tests (faster, more granular) -- Use `/e2e` for integration and user journey tests -- Use `/code-review` to verify test quality +- Use `/egc-plan` to identify critical journeys to test +- Use `/egc-tdd` for unit tests (faster, more granular) +- Use `/egc-e2e` for integration and user journey tests +- Use `/egc-code-review` to verify test quality ## Related Agents @@ -345,7 +345,7 @@ This command invokes the `e2e-runner` agent located at: npx playwright test # Run specific test file -npx playwright test tests/e2e/markets/search.spec.ts +npx playwright test tests/egc-e2e/markets/search.spec.ts # Run in headed mode (see browser) npx playwright test --headed diff --git a/commands/eval.toml b/commands/egc-eval.toml similarity index 92% rename from commands/eval.toml rename to commands/egc-eval.toml index 4d4251c..f0cae98 100644 --- a/commands/eval.toml +++ b/commands/egc-eval.toml @@ -6,11 +6,11 @@ Manage eval-driven development workflow. ## Usage -`/eval [define|check|report|list] [feature-name]` +`/egc-eval [define|check|report|list] [feature-name]` ## Define Evals -`/eval define feature-name` +`/egc-eval define feature-name` Create a new eval definition: @@ -37,7 +37,7 @@ Created: $(date) ## Check Evals -`/eval check feature-name` +`/egc-eval check feature-name` Run evals for a feature: @@ -62,7 +62,7 @@ Status: IN PROGRESS / READY ## Report Evals -`/eval report feature-name` +`/egc-eval report feature-name` Generate comprehensive eval report: @@ -100,7 +100,7 @@ RECOMMENDATION ## List Evals -`/eval list` +`/egc-eval list` Show all eval definitions: diff --git a/commands/evolve.toml b/commands/egc-evolve.toml similarity index 93% rename from commands/evolve.toml rename to commands/egc-evolve.toml index ff3e5ac..0116e30 100644 --- a/commands/evolve.toml +++ b/commands/egc-evolve.toml @@ -24,10 +24,10 @@ Analyzes instincts and clusters related ones into higher-level structures: ## Usage ``` -/evolve # Analyze all instincts and suggest evolutions -/evolve --domain testing # Only evolve instincts in testing domain -/evolve --dry-run # Show what would be created without creating -/evolve --threshold 5 # Require 5+ related instincts to cluster +/egc-evolve # Analyze all instincts and suggest evolutions +/egc-evolve --domain testing # Only evolve instincts in testing domain +/egc-evolve --dry-run # Show what would be created without creating +/egc-evolve --threshold 5 # Require 5+ related instincts to cluster ``` ## Evolution Rules @@ -121,7 +121,7 @@ Files: - ~/.gemini/homunculus/evolved/agents/debugger.md --- -Run `/evolve --execute` to create these files. +Run `/egc-evolve --execute` to create these files. ``` ## Flags diff --git a/commands/feature-dev.toml b/commands/egc-feature-dev.toml similarity index 86% rename from commands/feature-dev.toml rename to commands/egc-feature-dev.toml index 9cd560d..6ccebb8 100644 --- a/commands/feature-dev.toml +++ b/commands/egc-feature-dev.toml @@ -49,13 +49,13 @@ A structured feature-development workflow that emphasizes understanding existing ## Example Usage ``` -/feature-dev Add user profile page with avatar upload +/egc-feature-dev Add user profile page with avatar upload ``` ## Related Commands -- `/plan` — Create implementation plan first -- `/tdd` — Test-driven development workflow -- `/code-review` — Standalone code review +- `/egc-plan` — Create implementation plan first +- `/egc-tdd` — Test-driven development workflow +- `/egc-code-review` — Standalone code review ''' diff --git a/commands/flutter-build.toml b/commands/egc-flutter-build.toml similarity index 95% rename from commands/flutter-build.toml rename to commands/egc-flutter-build.toml index 4df2c3e..6f72748 100644 --- a/commands/flutter-build.toml +++ b/commands/egc-flutter-build.toml @@ -14,7 +14,7 @@ This command invokes the **dart-build-resolver** agent to incrementally fix Dart ## When to Use -Use `/flutter-build` when: +Use `/egc-flutter-build` when: - `flutter analyze` reports errors - `flutter build` fails for any platform - `dart pub get` / `flutter pub get` fails with version conflicts @@ -41,7 +41,7 @@ flutter build web 2>&1 ## Example Session ````text -User: /flutter-build +User: /egc-flutter-build Agent: # Flutter Build Resolution @@ -152,9 +152,9 @@ The agent will stop and report if: ## Related Commands -- `/flutter-test` — Run tests after build succeeds -- `/flutter-review` — Review code quality -- `/verify` — Full verification loop +- `/egc-flutter-test` — Run tests after build succeeds +- `/egc-flutter-review` — Review code quality +- `/egc-verify` — Full verification loop ## Related diff --git a/commands/flutter-review.toml b/commands/egc-flutter-review.toml similarity index 89% rename from commands/flutter-review.toml rename to commands/egc-flutter-review.toml index ed584c6..ed69d21 100644 --- a/commands/flutter-review.toml +++ b/commands/egc-flutter-review.toml @@ -14,15 +14,15 @@ This command invokes the **flutter-reviewer** agent to review Flutter/Dart code ## Prerequisites -Before running `/flutter-review`, ensure: -1. **Build passes** — run `/flutter-build` first; a review on broken code is incomplete -2. **Tests pass** — run `/flutter-test` to confirm no regressions +Before running `/egc-flutter-review`, ensure: +1. **Build passes** — run `/egc-flutter-build` first; a review on broken code is incomplete +2. **Tests pass** — run `/egc-flutter-test` to confirm no regressions 3. **No merge conflicts** — resolve all conflicts so the diff reflects only intentional changes 4. **`flutter analyze` is clean** — fix analyzer warnings before review ## When to Use -Use `/flutter-review` when: +Use `/egc-flutter-review` when: - Before submitting a PR with Flutter/Dart changes (after build and tests pass) - After implementing a new feature to catch issues early - When reviewing someone else's Flutter code @@ -48,7 +48,7 @@ Use `/flutter-review` when: ## Example Session ````text -User: /flutter-review +User: /egc-flutter-review Agent: # Flutter Code Review @@ -103,9 +103,9 @@ Verdict: BLOCK — HIGH issues must be fixed before merge. ## Related Commands -- `/flutter-build` — Fix build errors first -- `/flutter-test` — Run tests before reviewing -- `/code-review` — General code review (language-agnostic) +- `/egc-flutter-build` — Fix build errors first +- `/egc-flutter-test` — Run tests before reviewing +- `/egc-code-review` — General code review (language-agnostic) ## Related diff --git a/commands/flutter-test.toml b/commands/egc-flutter-test.toml similarity index 92% rename from commands/flutter-test.toml rename to commands/egc-flutter-test.toml index 1ec3ca8..a94ad6b 100644 --- a/commands/flutter-test.toml +++ b/commands/egc-flutter-test.toml @@ -14,9 +14,9 @@ This command runs the Flutter test suite and reports results. When failures occu ## When to Use -Use `/flutter-test` when: +Use `/egc-flutter-test` when: - After implementing a feature to verify nothing broke -- After running `/flutter-build` to ensure tests pass +- After running `/egc-flutter-build` to ensure tests pass - To check test coverage on new code - When a specific test file is failing - Before submitting a PR @@ -46,7 +46,7 @@ flutter test --update-goldens 2>&1 ## Example Session ````text -User: /flutter-test +User: /egc-flutter-test Agent: # Flutter Test Run @@ -130,9 +130,9 @@ Test Status: PASS ## Related Commands -- `/flutter-build` — Fix build errors before running tests -- `/flutter-review` — Review code after tests pass -- `/tdd` — Test-driven development workflow +- `/egc-flutter-build` — Fix build errors before running tests +- `/egc-flutter-review` — Review code after tests pass +- `/egc-tdd` — Test-driven development workflow ## Related diff --git a/commands/gan-build.toml b/commands/egc-gan-build.toml similarity index 95% rename from commands/gan-build.toml rename to commands/egc-gan-build.toml index 81440c7..00a2df5 100644 --- a/commands/gan-build.toml +++ b/commands/egc-gan-build.toml @@ -102,8 +102,8 @@ Write the full report to `gan-harness/build-report.md`. ## Related Commands -- `/gan-design` — Design-focused generation loop -- `/code-review` — Standard code review -- `/tdd` — Test-driven development workflow +- `/egc-gan-design` — Design-focused generation loop +- `/egc-code-review` — Standard code review +- `/egc-tdd` — Test-driven development workflow ''' diff --git a/commands/gan-design.toml b/commands/egc-gan-design.toml similarity index 95% rename from commands/gan-design.toml rename to commands/egc-gan-design.toml index 062e956..460483c 100644 --- a/commands/gan-design.toml +++ b/commands/egc-gan-design.toml @@ -38,7 +38,7 @@ The Generator is told: "Your PRIMARY goal is visual excellence. A stunning half- ## Related Commands -- `/gan-build` — Build-focused generation loop -- `/e2e` — End-to-end testing +- `/egc-gan-build` — Build-focused generation loop +- `/egc-e2e` — End-to-end testing ''' diff --git a/commands/go-build.toml b/commands/egc-go-build.toml similarity index 95% rename from commands/go-build.toml rename to commands/egc-go-build.toml index a786097..22bec66 100644 --- a/commands/go-build.toml +++ b/commands/egc-go-build.toml @@ -14,7 +14,7 @@ This command invokes the **go-build-resolver** agent to incrementally fix Go bui ## When to Use -Use `/go-build` when: +Use `/egc-go-build` when: - `go build ./...` fails with errors - `go vet ./...` reports issues - `golangci-lint run` shows warnings @@ -42,7 +42,7 @@ go mod tidy -v ## Example Session ```text -User: /go-build +User: /egc-go-build Agent: # Go Build Resolution @@ -171,9 +171,9 @@ The agent will stop and report if: ## Related Commands -- `/go-test` - Run tests after build succeeds -- `/go-review` - Review code quality -- `/verify` - Full verification loop +- `/egc-go-test` - Run tests after build succeeds +- `/egc-go-review` - Review code quality +- `/egc-verify` - Full verification loop ## Related diff --git a/commands/go-review.toml b/commands/egc-go-review.toml similarity index 93% rename from commands/go-review.toml rename to commands/egc-go-review.toml index 8072c8f..1da6b4d 100644 --- a/commands/go-review.toml +++ b/commands/egc-go-review.toml @@ -15,7 +15,7 @@ This command invokes the **go-reviewer** agent for comprehensive Go-specific cod ## When to Use -Use `/go-review` when: +Use `/egc-go-review` when: - After writing or modifying Go code - Before committing Go changes - Reviewing pull requests with Go code @@ -67,7 +67,7 @@ govulncheck ./... ## Example Usage ```text -User: /go-review +User: /egc-go-review Agent: # Go Code Review Report @@ -135,10 +135,10 @@ Recommendation: ❌ Block merge until CRITICAL issue is fixed ## Integration with Other Commands -- Use `/go-test` first to ensure tests pass -- Use `/go-build` if build errors occur -- Use `/go-review` before committing -- Use `/code-review` for non-Go specific concerns +- Use `/egc-go-test` first to ensure tests pass +- Use `/egc-go-build` if build errors occur +- Use `/egc-go-review` before committing +- Use `/egc-code-review` for non-Go specific concerns ## Related diff --git a/commands/go-test.toml b/commands/egc-go-test.toml similarity index 96% rename from commands/go-test.toml rename to commands/egc-go-test.toml index 6e524ad..99286e1 100644 --- a/commands/go-test.toml +++ b/commands/egc-go-test.toml @@ -15,7 +15,7 @@ This command enforces test-driven development methodology for Go code using idio ## When to Use -Use `/go-test` when: +Use `/egc-go-test` when: - Implementing new Go functions - Adding test coverage to existing code - Fixing bugs (write failing test first) @@ -34,7 +34,7 @@ REPEAT → Next test case ## Example Session ```text -User: /go-test I need a function to validate email addresses +User: /egc-go-test I need a function to validate email addresses Agent: # TDD Session: Email Validator @@ -256,9 +256,9 @@ go test -race -cover ./... ## Related Commands -- `/go-build` - Fix build errors -- `/go-review` - Review code after implementation -- `/verify` - Run full verification loop +- `/egc-go-build` - Fix build errors +- `/egc-go-review` - Review code after implementation +- `/egc-verify` - Run full verification loop ## Related diff --git a/commands/gradle-build.toml b/commands/egc-gradle-build.toml similarity index 100% rename from commands/gradle-build.toml rename to commands/egc-gradle-build.toml diff --git a/commands/harness-audit.toml b/commands/egc-harness-audit.toml similarity index 88% rename from commands/harness-audit.toml rename to commands/egc-harness-audit.toml index 264ce3a..851d624 100644 --- a/commands/harness-audit.toml +++ b/commands/egc-harness-audit.toml @@ -6,7 +6,7 @@ Run a deterministic repository harness audit and return a prioritized scorecard. ## Usage -`/harness-audit [scope] [--format text|json]` +`/egc-harness-audit [scope] [--format text|json]` - `scope` (optional): `repo` (default), `hooks`, `skills`, `commands`, `agents` - `--format`: output style (`text` default, `json` for automation) @@ -16,7 +16,7 @@ Run a deterministic repository harness audit and return a prioritized scorecard. Always run: ```bash -node scripts/harness-audit.js --format +node scripts/egc-harness-audit.js --format ``` This script is the source of truth for scoring and checks. Do not invent additional dimensions or ad-hoc points. @@ -62,7 +62,7 @@ Harness Audit (repo): 66/70 Top 3 Actions: 1) [Security Guardrails] Add prompt/tool preflight security guards in hooks/hooks.json. (hooks/hooks.json) -2) [Tool Coverage] Sync commands/harness-audit.md and .opencode/commands/harness-audit.md. (.opencode/commands/harness-audit.md) +2) [Tool Coverage] Sync commands/egc-harness-audit.md and .opencode/commands/egc-harness-audit.md. (.opencode/commands/egc-harness-audit.md) 3) [Eval Coverage] Increase automated test coverage across scripts/hooks/lib. (tests/) ``` diff --git a/commands/hookify-configure.toml b/commands/egc-hookify-configure.toml similarity index 87% rename from commands/hookify-configure.toml rename to commands/egc-hookify-configure.toml index 4d52d8d..803e614 100644 --- a/commands/hookify-configure.toml +++ b/commands/egc-hookify-configure.toml @@ -4,7 +4,7 @@ Interactively enable or disable existing hookify rules. ## Steps -1. Find all `.gemini/hookify.*.local.md` files +1. Find all `.gemini/egc-hookify.*.local.md` files 2. Read the current state of each rule 3. Present the list with current enabled / disabled status 4. Ask which rules to toggle diff --git a/commands/hookify-help.toml b/commands/egc-hookify-help.toml similarity index 77% rename from commands/hookify-help.toml rename to commands/egc-hookify-help.toml index 58ffd3b..f02d471 100644 --- a/commands/hookify-help.toml +++ b/commands/egc-hookify-help.toml @@ -16,7 +16,7 @@ Hookify creates rule files that integrate with Gemini CLI's hook system to preve ### Rule File Format -Files are stored as `.gemini/hookify.{name}.local.md`: +Files are stored as `.gemini/egc-hookify.{name}.local.md`: ```yaml --- @@ -32,9 +32,9 @@ Supports multiple lines. ### Commands -- `/hookify [description]` creates new rules and auto-analyzes the conversation when no description is given -- `/hookify-list` lists configured rules -- `/hookify-configure` toggles rules on or off +- `/egc-hookify [description]` creates new rules and auto-analyzes the conversation when no description is given +- `/egc-hookify-list` lists configured rules +- `/egc-hookify-configure` toggles rules on or off ### Pattern Tips diff --git a/commands/hookify-list.toml b/commands/egc-hookify-list.toml similarity index 70% rename from commands/hookify-list.toml rename to commands/egc-hookify-list.toml index cd0bb8a..3fa1535 100644 --- a/commands/hookify-list.toml +++ b/commands/egc-hookify-list.toml @@ -4,7 +4,7 @@ Find and display all hookify rules in a formatted table. ## Steps -1. Find all `.gemini/hookify.*.local.md` files +1. Find all `.gemini/egc-hookify.*.local.md` files 2. Read each file's frontmatter: - `name` - `enabled` @@ -16,6 +16,6 @@ Find and display all hookify rules in a formatted table. | Rule | Enabled | Event | Pattern | File | |------|---------|-------|---------|------| -4. Show the rule count and remind the user that `/hookify-configure` can change state later. +4. Show the rule count and remind the user that `/egc-hookify-configure` can change state later. ''' diff --git a/commands/hookify.toml b/commands/egc-hookify.toml similarity index 81% rename from commands/hookify.toml rename to commands/egc-hookify.toml index 8a97a46..9924d70 100644 --- a/commands/hookify.toml +++ b/commands/egc-hookify.toml @@ -4,7 +4,7 @@ Create hook rules to prevent unwanted Gemini CLI behaviors by analyzing conversa ## Usage -`/hookify [description of behavior to prevent]` +`/egc-hookify [description of behavior to prevent]` If no arguments are provided, analyze the current conversation to find behaviors worth preventing. @@ -30,7 +30,7 @@ Show the user: ### Step 3: Generate Rule Files -For each approved rule, create a file at `.gemini/hookify.{name}.local.md`: +For each approved rule, create a file at `.gemini/egc-hookify.{name}.local.md`: ```yaml --- @@ -45,6 +45,6 @@ Message shown when rule triggers. ### Step 4: Confirm -Report created rules and how to manage them with `/hookify-list` and `/hookify-configure`. +Report created rules and how to manage them with `/egc-hookify-list` and `/egc-hookify-configure`. ''' diff --git a/commands/instinct-export.toml b/commands/egc-instinct-export.toml similarity index 86% rename from commands/instinct-export.toml rename to commands/egc-instinct-export.toml index 957fa9b..67b6fb1 100644 --- a/commands/instinct-export.toml +++ b/commands/egc-instinct-export.toml @@ -10,10 +10,10 @@ Exports instincts to a shareable format. Perfect for: ## Usage ``` -/instinct-export # Export all personal instincts -/instinct-export --domain testing # Export only testing instincts -/instinct-export --min-confidence 0.7 # Only export high-confidence instincts -/instinct-export --output team-instincts.yaml +/egc-instinct-export # Export all personal instincts +/egc-instinct-export --domain testing # Export only testing instincts +/egc-instinct-export --min-confidence 0.7 # Only export high-confidence instincts +/egc-instinct-export --output team-instincts.yaml ``` ## What to Do diff --git a/commands/instinct-import.toml b/commands/egc-instinct-import.toml similarity index 92% rename from commands/instinct-import.toml rename to commands/egc-instinct-import.toml index f3379b4..aa68adb 100644 --- a/commands/instinct-import.toml +++ b/commands/egc-instinct-import.toml @@ -25,9 +25,9 @@ Import instincts from: ## Usage ``` -/instinct-import team-instincts.yaml -/instinct-import https://github.com/org/repo/instincts.yaml -/instinct-import --from-skill-creator acme/webapp +/egc-instinct-import team-instincts.yaml +/egc-instinct-import https://github.com/org/repo/instincts.yaml +/egc-instinct-import --from-skill-creator acme/webapp ``` ## What to Do @@ -106,7 +106,7 @@ original_source: "session-observation" # or "repo-analysis" When importing from Skill Creator: ``` -/instinct-import --from-skill-creator acme/webapp +/egc-instinct-import --from-skill-creator acme/webapp ``` This fetches instincts generated from repo analysis: @@ -134,6 +134,6 @@ Skipped: 3 instincts (2 duplicates, 1 conflict) New instincts saved to: ~/.gemini/homunculus/instincts/inherited/ -Run /instinct-status to see all instincts. +Run /egc-instinct-status to see all instincts. ``` ''' diff --git a/commands/instinct-status.toml b/commands/egc-instinct-status.toml similarity index 95% rename from commands/instinct-status.toml rename to commands/egc-instinct-status.toml index 20ba3e9..585dcff 100644 --- a/commands/instinct-status.toml +++ b/commands/egc-instinct-status.toml @@ -21,9 +21,9 @@ python3 ~/.gemini/skills/continuous-learning-v2/scripts/instinct-cli.py status ## Usage ``` -/instinct-status -/instinct-status --domain code-style -/instinct-status --low-confidence +/egc-instinct-status +/egc-instinct-status --domain code-style +/egc-instinct-status --low-confidence ``` ## What to Do diff --git a/commands/jira.toml b/commands/egc-jira.toml similarity index 74% rename from commands/jira.toml rename to commands/egc-jira.toml index 6f510c7..cfb5e61 100644 --- a/commands/jira.toml +++ b/commands/egc-jira.toml @@ -7,10 +7,10 @@ Interact with Jira tickets directly from your workflow — fetch tickets, analyz ## Usage ``` -/jira get # Fetch and analyze a ticket -/jira comment # Add a progress comment -/jira transition # Change ticket status -/jira search # Search issues with JQL +/egc-jira get # Fetch and analyze a ticket +/egc-jira comment # Add a progress comment +/egc-jira transition # Change ticket status +/egc-jira search # Search issues with JQL ``` ## What This Command Does @@ -22,7 +22,7 @@ Interact with Jira tickets directly from your workflow — fetch tickets, analyz ## How It Works -### `/jira get ` +### `/egc-jira get ` 1. Fetch the ticket from Jira (via MCP `jira_get_issue` or REST API) 2. Extract all fields: summary, description, acceptance criteria, priority, labels, linked issues @@ -52,23 +52,23 @@ Dependencies: - [linked issues, APIs, services] Recommended Next Steps: -- /plan to create implementation plan -- /tdd to implement with tests first +- /egc-plan to create implementation plan +- /egc-tdd to implement with tests first ``` -### `/jira comment ` +### `/egc-jira comment ` 1. Summarize current session progress (what was built, tested, committed) 2. Format as a structured comment 3. Post to the Jira ticket -### `/jira transition ` +### `/egc-jira transition ` 1. Fetch available transitions for the ticket 2. Show options to user 3. Execute the selected transition -### `/jira search ` +### `/egc-jira search ` 1. Execute the JQL query against Jira 2. Return a summary table of matching issues @@ -92,11 +92,11 @@ If credentials are missing, stop and direct the user to set them up. ## Integration with Other Commands After analyzing a ticket: -- Use `/plan` to create an implementation plan from the requirements -- Use `/tdd` to implement with test-driven development -- Use `/code-review` after implementation -- Use `/jira comment` to post progress back to the ticket -- Use `/jira transition` to move the ticket when work is complete +- Use `/egc-plan` to create an implementation plan from the requirements +- Use `/egc-tdd` to implement with test-driven development +- Use `/egc-code-review` after implementation +- Use `/egc-jira comment` to post progress back to the ticket +- Use `/egc-jira transition` to move the ticket when work is complete ## Related diff --git a/commands/kotlin-build.toml b/commands/egc-kotlin-build.toml similarity index 95% rename from commands/kotlin-build.toml rename to commands/egc-kotlin-build.toml index 9bed05c..325f7c1 100644 --- a/commands/kotlin-build.toml +++ b/commands/egc-kotlin-build.toml @@ -18,7 +18,7 @@ This command invokes the **kotlin-build-resolver** agent to incrementally fix Ko ## When to Use -Use `/kotlin-build` when: +Use `/egc-kotlin-build` when: - `./gradlew build` fails with errors - Kotlin compiler reports errors - `./gradlew detekt` reports violations @@ -45,7 +45,7 @@ Use `/kotlin-build` when: ## Example Session ````text -User: /kotlin-build +User: /egc-kotlin-build Agent: # Kotlin Build Resolution @@ -166,9 +166,9 @@ The agent will stop and report if: ## Related Commands -- `/kotlin-test` - Run tests after build succeeds -- `/kotlin-review` - Review code quality -- `/verify` - Full verification loop +- `/egc-kotlin-test` - Run tests after build succeeds +- `/egc-kotlin-review` - Review code quality +- `/egc-verify` - Full verification loop ## Related diff --git a/commands/kotlin-review.toml b/commands/egc-kotlin-review.toml similarity index 92% rename from commands/kotlin-review.toml rename to commands/egc-kotlin-review.toml index 4833d5f..83d4fa7 100644 --- a/commands/kotlin-review.toml +++ b/commands/egc-kotlin-review.toml @@ -19,7 +19,7 @@ This command invokes the **kotlin-reviewer** agent for comprehensive Kotlin-spec ## When to Use -Use `/kotlin-review` when: +Use `/egc-kotlin-review` when: - After writing or modifying Kotlin code - Before committing Kotlin changes - Reviewing pull requests with Kotlin code @@ -70,7 +70,7 @@ Use `/kotlin-review` when: ## Example Usage ````text -User: /kotlin-review +User: /egc-kotlin-review Agent: # Kotlin Code Review Report @@ -131,10 +131,10 @@ Recommendation: ❌ Block merge until CRITICAL issue is fixed ## Integration with Other Commands -- Use `/kotlin-test` first to ensure tests pass -- Use `/kotlin-build` if build errors occur -- Use `/kotlin-review` before committing -- Use `/code-review` for non-Kotlin-specific concerns +- Use `/egc-kotlin-test` first to ensure tests pass +- Use `/egc-kotlin-build` if build errors occur +- Use `/egc-kotlin-review` before committing +- Use `/egc-code-review` for non-Kotlin-specific concerns ## Related diff --git a/commands/kotlin-test.toml b/commands/egc-kotlin-test.toml similarity index 96% rename from commands/kotlin-test.toml rename to commands/egc-kotlin-test.toml index a0959f9..d4a32ab 100644 --- a/commands/kotlin-test.toml +++ b/commands/egc-kotlin-test.toml @@ -19,7 +19,7 @@ This command enforces test-driven development methodology for Kotlin code using ## When to Use -Use `/kotlin-test` when: +Use `/egc-kotlin-test` when: - Implementing new Kotlin functions or classes - Adding test coverage to existing Kotlin code - Fixing bugs (write failing test first) @@ -38,7 +38,7 @@ REPEAT -> Next test case ## Example Session ````text -User: /kotlin-test I need a function to validate user registration requests +User: /egc-kotlin-test I need a function to validate user registration requests Agent: # TDD Session: Registration Validator @@ -304,9 +304,9 @@ open build/reports/kover/html/index.html ## Related Commands -- `/kotlin-build` - Fix build errors -- `/kotlin-review` - Review code after implementation -- `/verify` - Run full verification loop +- `/egc-kotlin-build` - Fix build errors +- `/egc-kotlin-review` - Review code after implementation +- `/egc-verify` - Run full verification loop ## Related diff --git a/commands/learn-eval.toml b/commands/egc-learn-eval.toml similarity index 95% rename from commands/learn-eval.toml rename to commands/egc-learn-eval.toml index ce3f87b..2de87b0 100644 --- a/commands/learn-eval.toml +++ b/commands/egc-learn-eval.toml @@ -1,12 +1,12 @@ -description = '/learn-eval - Extract, Evaluate, then Save' +description = '/egc-learn-eval - Extract, Evaluate, then Save' prompt = ''' --- description: "Extract reusable patterns from the session, self-evaluate quality before saving, and determine the right save location (Global vs Project)." --- -# /learn-eval - Extract, Evaluate, then Save +# /egc-learn-eval - Extract, Evaluate, then Save -Extends `/learn` with a quality gate, save-location decision, and knowledge-placement awareness before writing any skill file. +Extends `/egc-learn` with a quality gate, save-location decision, and knowledge-placement awareness before writing any skill file. ## What to Extract diff --git a/commands/learn.toml b/commands/egc-learn.toml similarity index 92% rename from commands/learn.toml rename to commands/egc-learn.toml index 27d3a80..6b21cbb 100644 --- a/commands/learn.toml +++ b/commands/egc-learn.toml @@ -1,12 +1,12 @@ description = "Extract reusable patterns from the current session" prompt = ''' -# /learn - Extract Reusable Patterns +# /egc-learn - Extract Reusable Patterns Analyze the current session and extract any patterns worth saving as skills. ## Trigger -Run `/learn` at any point during a session when you've solved a non-trivial problem. +Run `/egc-learn` at any point during a session when you've solved a non-trivial problem. ## What to Extract diff --git a/commands/loop-start.toml b/commands/egc-loop-start.toml similarity index 95% rename from commands/loop-start.toml rename to commands/egc-loop-start.toml index cb5e446..ac79e25 100644 --- a/commands/loop-start.toml +++ b/commands/egc-loop-start.toml @@ -6,7 +6,7 @@ Start a managed autonomous loop pattern with safety defaults. ## Usage -`/loop-start [pattern] [--mode safe|fast]` +`/egc-loop-start [pattern] [--mode safe|fast]` - `pattern`: `sequential`, `continuous-pr`, `rfc-dag`, `infinite` - `--mode`: diff --git a/commands/loop-status.toml b/commands/egc-loop-status.toml similarity index 94% rename from commands/loop-status.toml rename to commands/egc-loop-status.toml index 4d731fe..de9a9f3 100644 --- a/commands/loop-status.toml +++ b/commands/egc-loop-status.toml @@ -6,7 +6,7 @@ Inspect active loop state, progress, and failure signals. ## Usage -`/loop-status [--watch]` +`/egc-loop-status [--watch]` ## What to Report diff --git a/commands/model-route.toml b/commands/egc-model-route.toml similarity index 90% rename from commands/model-route.toml rename to commands/egc-model-route.toml index b890c7d..941dd7b 100644 --- a/commands/model-route.toml +++ b/commands/egc-model-route.toml @@ -6,7 +6,7 @@ Recommend the best model tier for the current task by complexity and budget. ## Usage -`/model-route [task-description] [--budget low|med|high]` +`/egc-model-route [task-description] [--budget low|med|high]` ## Routing Heuristic diff --git a/commands/multi-backend.toml b/commands/egc-multi-backend.toml similarity index 98% rename from commands/multi-backend.toml rename to commands/egc-multi-backend.toml index bf0c8ff..c97b205 100644 --- a/commands/multi-backend.toml +++ b/commands/egc-multi-backend.toml @@ -120,7 +120,7 @@ Output solutions (at least 2), wait for user selection. - Context: Analysis results from Phase 2 - OUTPUT: File structure, function/class design, dependency relationships -Gemini CLI synthesizes plan, save to `.gemini/plan/task-name.md` after user approval. +Gemini CLI synthesizes plan, save to `.gemini/egc-plan/task-name.md` after user approval. ### Phase 4: Implementation diff --git a/commands/multi-execute.toml b/commands/egc-multi-execute.toml similarity index 98% rename from commands/multi-execute.toml rename to commands/egc-multi-execute.toml index 1b3cec7..6c202a1 100644 --- a/commands/multi-execute.toml +++ b/commands/egc-multi-execute.toml @@ -113,7 +113,7 @@ TaskOutput({ task_id: "", block: true, timeout: 600000 }) `[Mode: Prepare]` 1. **Identify Input Type**: - - Plan file path (e.g., `.gemini/plan/xxx.md`) + - Plan file path (e.g., `.gemini/egc-plan/xxx.md`) - Direct task description 2. **Read Plan Content**: @@ -221,7 +221,7 @@ mcp__ace-tool__search_context({ - Refactor "dirty prototype" to **highly readable, maintainable, enterprise-grade code** - Remove redundant code - Ensure compliance with project's existing code standards - - **Do not generate comments/docs unless necessary**, code should be self-explanatory + - **Do not generate comments/egc-docs unless necessary**, code should be self-explanatory 4. **Minimal Scope**: - Changes limited to requirement scope only @@ -302,7 +302,7 @@ After audit passes, report to user: ```bash # Execute plan file -/ccg:execute .gemini/plan/feature-name.md +/ccg:execute .gemini/egc-plan/feature-name.md # Execute task directly (for plans already discussed in context) /ccg:execute implement user authentication based on previous plan diff --git a/commands/multi-frontend.toml b/commands/egc-multi-frontend.toml similarity index 98% rename from commands/multi-frontend.toml rename to commands/egc-multi-frontend.toml index 538d7ce..5a92354 100644 --- a/commands/multi-frontend.toml +++ b/commands/egc-multi-frontend.toml @@ -120,7 +120,7 @@ Output solutions (at least 2), wait for user selection. - Context: Analysis results from Phase 2 - OUTPUT: Component structure, UI flow, styling approach -Gemini CLI synthesizes plan, save to `.gemini/plan/task-name.md` after user approval. +Gemini CLI synthesizes plan, save to `.gemini/egc-plan/task-name.md` after user approval. ### Phase 4: Implementation diff --git a/commands/multi-plan.toml b/commands/egc-multi-plan.toml similarity index 93% rename from commands/multi-plan.toml rename to commands/egc-multi-plan.toml index 888242b..9d167e4 100644 --- a/commands/multi-plan.toml +++ b/commands/egc-multi-plan.toml @@ -14,7 +14,7 @@ $ARGUMENTS - **Mandatory Parallel**: Codex/Gemini calls MUST use `run_in_background: true` (including single model calls, to avoid blocking main thread) - **Code Sovereignty**: External models have **zero filesystem write access**, all modifications by Gemini CLI - **Stop-Loss Mechanism**: Do not proceed to next phase until current phase output is validated -- **Planning Only**: This command allows reading context and writing to `.gemini/plan/*` plan files, but **NEVER modify production code** +- **Planning Only**: This command allows reading context and writing to `.gemini/egc-plan/*` plan files, but **NEVER modify production code** --- @@ -202,18 +202,18 @@ Synthesize both analyses, generate **Step-by-step Implementation Plan**: **`/ccg:plan` responsibilities end here, MUST execute the following actions**: 1. Present complete implementation plan to user (including pseudo-code) -2. Save plan to `.gemini/plan/.md` (extract feature name from requirement, e.g., `user-auth`, `payment-module`) +2. Save plan to `.gemini/egc-plan/.md` (extract feature name from requirement, e.g., `user-auth`, `payment-module`) 3. Output prompt in **bold text** (MUST use actual saved file path): --- - **Plan generated and saved to `.gemini/plan/actual-feature-name.md`** + **Plan generated and saved to `.gemini/egc-plan/actual-feature-name.md`** **Please review the plan above. You can:** - **Modify plan**: Tell me what needs adjustment, I'll update the plan - **Execute plan**: Copy the following command to a new session ``` - /ccg:execute .gemini/plan/actual-feature-name.md + /ccg:execute .gemini/egc-plan/actual-feature-name.md ``` --- @@ -233,8 +233,8 @@ Synthesize both analyses, generate **Step-by-step Implementation Plan**: After planning completes, save plan to: -- **First planning**: `.gemini/plan/.md` -- **Iteration versions**: `.gemini/plan/-v2.md`, `.gemini/plan/-v3.md`... +- **First planning**: `.gemini/egc-plan/.md` +- **Iteration versions**: `.gemini/egc-plan/-v2.md`, `.gemini/egc-plan/-v3.md`... Plan file write should complete before presenting plan to user. @@ -245,7 +245,7 @@ Plan file write should complete before presenting plan to user. If user requests plan modifications: 1. Adjust plan content based on user feedback -2. Update `.gemini/plan/.md` file +2. Update `.gemini/egc-plan/.md` file 3. Re-present modified plan 4. Prompt user to review or execute again @@ -256,7 +256,7 @@ If user requests plan modifications: After user approves, **manually** execute: ```bash -/ccg:execute .gemini/plan/.md +/ccg:execute .gemini/egc-plan/.md ``` --- diff --git a/commands/multi-workflow.toml b/commands/egc-multi-workflow.toml similarity index 97% rename from commands/multi-workflow.toml rename to commands/egc-multi-workflow.toml index 2c9b4fe..dc06cba 100644 --- a/commands/multi-workflow.toml +++ b/commands/egc-multi-workflow.toml @@ -108,7 +108,7 @@ TaskOutput({ task_id: "", block: true, timeout: 600000 }) Use external tmux/worktree orchestration when the work must be split across parallel workers that need isolated git state, independent terminals, or separate build/test execution. Use in-process subagents for lightweight analysis, planning, or review where the main session remains the only writer. ```bash -node scripts/orchestrate-worktrees.js .gemini/plan/workflow-e2e-test.json --execute +node scripts/orchestrate-worktrees.js .gemini/egc-plan/workflow-e2e-test.json --execute ``` --- @@ -153,7 +153,7 @@ Wait for results with `TaskOutput`. **Follow the `IMPORTANT` instructions in `Multi-Model Call Specification` above** -**Gemini CLI Synthesis**: Adopt Codex backend plan + Gemini frontend plan, save to `.gemini/plan/task-name.md` after user approval. +**Gemini CLI Synthesis**: Adopt Codex backend plan + Gemini frontend plan, save to `.gemini/egc-plan/task-name.md` after user approval. ### Phase 4: Implementation diff --git a/commands/orchestrate.toml b/commands/egc-orchestrate.toml similarity index 94% rename from commands/orchestrate.toml rename to commands/egc-orchestrate.toml index 0fded2e..8bd8749 100644 --- a/commands/orchestrate.toml +++ b/commands/egc-orchestrate.toml @@ -10,7 +10,7 @@ Sequential agent workflow for complex tasks. ## Usage -`/orchestrate [workflow-type] [task-description]` +`/egc-orchestrate [workflow-type] [task-description]` ## Workflow Types @@ -73,7 +73,7 @@ Between agents, create handoff document: ## Example: Feature Workflow ``` -/orchestrate feature "Add user authentication" +/egc-orchestrate feature "Add user authentication" ``` Executes: @@ -164,7 +164,7 @@ When workers need to see dirty or untracked local files from the main checkout, "seedPaths": [ "scripts/orchestrate-worktrees.js", "scripts/lib/tmux-worktree-orchestrator.js", - ".gemini/plan/workflow-e2e-test.json" + ".gemini/egc-plan/workflow-e2e-test.json" ], "workers": [ { "name": "docs", "task": "Update orchestration docs." } @@ -175,7 +175,7 @@ When workers need to see dirty or untracked local files from the main checkout, To export a control-plane snapshot for a live tmux/worktree session, run: ```bash -node scripts/orchestration-status.js .gemini/plan/workflow-visual-proof.json +node scripts/orchestration-status.js .gemini/egc-plan/workflow-visual-proof.json ``` The snapshot includes session activity, tmux pane metadata, worker states, objectives, seeded overlays, and recent handoff summaries in JSON form. @@ -221,7 +221,7 @@ $ARGUMENTS: ## Custom Workflow Example ``` -/orchestrate custom "architect,tdd-guide,code-reviewer" "Redesign caching layer" +/egc-orchestrate custom "architect,tdd-guide,code-reviewer" "Redesign caching layer" ``` ## Tips diff --git a/commands/egc-plan.toml b/commands/egc-plan.toml index 71396ed..641f0a5 100644 --- a/commands/egc-plan.toml +++ b/commands/egc-plan.toml @@ -101,9 +101,9 @@ If you want changes, respond with: ## Integration with Other Commands After planning: -- Use `/tdd` to implement with test-driven development +- Use `/egc-tdd` to implement with test-driven development - Use `/build-and-fix` if build errors occur -- Use `/code-review` to review completed implementation +- Use `/egc-code-review` to review completed implementation ## Related Agents diff --git a/commands/pm2.toml b/commands/egc-pm2.toml similarity index 100% rename from commands/pm2.toml rename to commands/egc-pm2.toml diff --git a/commands/projects.toml b/commands/egc-projects.toml similarity index 93% rename from commands/projects.toml rename to commands/egc-projects.toml index e718a9a..3605cbc 100644 --- a/commands/projects.toml +++ b/commands/egc-projects.toml @@ -27,12 +27,12 @@ python3 ~/.gemini/skills/continuous-learning-v2/scripts/instinct-cli.py projects ## Usage ```bash -/projects +/egc-projects ``` ## What to Do -1. Read `~/.gemini/homunculus/projects.json` +1. Read `~/.gemini/homunculus/egc-projects.json` 2. For each project, display: - Project name, id, root, remote - Personal and inherited instinct counts diff --git a/commands/promote.toml b/commands/egc-promote.toml similarity index 76% rename from commands/promote.toml rename to commands/egc-promote.toml index 87de26e..20b2f15 100644 --- a/commands/promote.toml +++ b/commands/egc-promote.toml @@ -27,10 +27,10 @@ python3 ~/.gemini/skills/continuous-learning-v2/scripts/instinct-cli.py promote ## Usage ```bash -/promote # Auto-detect promotion candidates -/promote --dry-run # Preview auto-promotion candidates -/promote --force # Promote all qualified candidates without prompt -/promote grep-before-edit # Promote one specific instinct from current project +/egc-promote # Auto-detect promotion candidates +/egc-promote --dry-run # Preview auto-promotion candidates +/egc-promote --force # Promote all qualified candidates without prompt +/egc-promote grep-before-edit # Promote one specific instinct from current project ``` ## What to Do diff --git a/commands/prompt-optimize.toml b/commands/egc-prompt-optimize.toml similarity index 89% rename from commands/prompt-optimize.toml rename to commands/egc-prompt-optimize.toml index 52c2970..6e72e49 100644 --- a/commands/prompt-optimize.toml +++ b/commands/egc-prompt-optimize.toml @@ -1,10 +1,10 @@ -description = '/prompt-optimize' +description = '/egc-prompt-optimize' prompt = ''' --- description: Analyze a draft prompt and output an optimized, ECC-enriched version ready to paste and run. Does NOT execute the task — outputs advisory analysis only. --- -# /prompt-optimize +# /egc-prompt-optimize Analyze and optimize the following prompt for maximum ECC leverage. @@ -30,7 +30,7 @@ Apply the **prompt-optimizer** skill to the user's input below. Follow the 6-pha ## CRITICAL Do NOT execute the user's task. Output ONLY the analysis and optimized prompt. -If the user asks for direct execution, explain that `/prompt-optimize` only produces advisory output and tell them to start a normal task request instead. +If the user asks for direct execution, explain that `/egc-prompt-optimize` only produces advisory output and tell them to start a normal task request instead. Note: `blueprint` is a **skill**, not a slash command. Write "Use the blueprint skill" instead of presenting it as a `/...` command. diff --git a/commands/prp-commit.toml b/commands/egc-prp-commit.toml similarity index 82% rename from commands/prp-commit.toml rename to commands/egc-prp-commit.toml index 9a60eb4..24b2a35 100644 --- a/commands/prp-commit.toml +++ b/commands/egc-prp-commit.toml @@ -91,8 +91,8 @@ Files: {count} file(s) changed Next steps: - git push → push to remote - - /prp-pr → create a pull request - - /code-review → review before pushing + - /egc-prp-pr → create a pull request + - /egc-code-review → review before pushing ``` --- @@ -101,11 +101,11 @@ Next steps: | You say | What happens | |---|---| -| `/prp-commit` | Stages all, auto-generates message | -| `/prp-commit staged` | Commits only what's already staged | -| `/prp-commit *.ts` | Stages all TypeScript files, commits | -| `/prp-commit except tests` | Stages everything except test files | -| `/prp-commit the database migration` | Finds DB migration files from status, stages them | -| `/prp-commit only new files` | Stages untracked files only | +| `/egc-prp-commit` | Stages all, auto-generates message | +| `/egc-prp-commit staged` | Commits only what's already staged | +| `/egc-prp-commit *.ts` | Stages all TypeScript files, commits | +| `/egc-prp-commit except tests` | Stages everything except test files | +| `/egc-prp-commit the database migration` | Finds DB migration files from status, stages them | +| `/egc-prp-commit only new files` | Stages untracked files only | ''' diff --git a/commands/prp-implement.toml b/commands/egc-prp-implement.toml similarity index 94% rename from commands/prp-implement.toml rename to commands/egc-prp-implement.toml index 6ea008c..1d3bb41 100644 --- a/commands/prp-implement.toml +++ b/commands/egc-prp-implement.toml @@ -58,7 +58,7 @@ Extract these sections from the plan: If the file doesn't exist or isn't a valid plan: ``` Error: Plan file not found or invalid. -Run /prp-plan to create a plan first. +Run /egc-prp-plan to create a plan first. ``` **CHECKPOINT**: Plan loaded. All sections identified. Tasks extracted. @@ -264,8 +264,8 @@ Write report to `.gemini/PRPs/reports/{plan-name}-report.md`: | `path/to/test` | N tests | [area covered] | ## Next Steps -- [ ] Code review via `/code-review` -- [ ] Create PR via `/prp-pr` +- [ ] Code review via `/egc-code-review` +- [ ] Create PR via `/egc-prp-pr` ``` ### Update PRD (if applicable) @@ -323,7 +323,7 @@ Report to user: | Phase 2 | [next] | | ... | ... | -> Next step: Run `/prp-pr` to create a pull request, or `/code-review` to review changes first. +> Next step: Run `/egc-prp-pr` to create a pull request, or `/egc-code-review` to review changes first. ``` --- @@ -376,9 +376,9 @@ Report to user: ## Next Steps -- Run `/code-review` to review changes before committing -- Run `/prp-commit` to commit with a descriptive message -- Run `/prp-pr` to create a pull request -- Run `/prp-plan ` if the PRD has more phases +- Run `/egc-code-review` to review changes before committing +- Run `/egc-prp-commit` to commit with a descriptive message +- Run `/egc-prp-pr` to create a pull request +- Run `/egc-prp-plan ` if the PRD has more phases ''' diff --git a/commands/prp-plan.toml b/commands/egc-prp-plan.toml similarity index 97% rename from commands/prp-plan.toml rename to commands/egc-prp-plan.toml index 0ce6e5c..54b793b 100644 --- a/commands/prp-plan.toml +++ b/commands/egc-prp-plan.toml @@ -448,7 +448,7 @@ If this plan was generated from a PRD phase: - **Risks**: [top risk or "none identified"] - **Confidence Score**: [1-10] — likelihood of single-pass implementation -> Next step: Run `/prp-implement .gemini/PRPs/plans/{name}.plan.md` to execute this plan. +> Next step: Run `/egc-prp-implement .gemini/PRPs/plans/{name}.plan.md` to execute this plan. ``` --- @@ -493,8 +493,8 @@ A developer unfamiliar with this codebase should be able to implement the featur ## Next Steps -- Run `/prp-implement ` to execute this plan -- Run `/plan` for quick conversational planning without artifacts -- Run `/prp-prd` to create a PRD first if scope is unclear +- Run `/egc-prp-implement ` to execute this plan +- Run `/egc-plan` for quick conversational planning without artifacts +- Run `/egc-prp-prd` to create a PRD first if scope is unclear ''' diff --git a/commands/prp-pr.toml b/commands/egc-prp-pr.toml similarity index 97% rename from commands/prp-pr.toml rename to commands/egc-prp-pr.toml index 6b7c7ba..541ebf2 100644 --- a/commands/prp-pr.toml +++ b/commands/egc-prp-pr.toml @@ -26,7 +26,7 @@ git log origin/..HEAD --oneline | Check | Condition | Action if Failed | |---|---|---| | Not on base branch | Current branch ≠ base | Stop: "Switch to a feature branch first." | -| Clean working directory | No uncommitted changes | Warn: "You have uncommitted changes. Commit or stash first. Use `/prp-commit` to commit." | +| Clean working directory | No uncommitted changes | Warn: "You have uncommitted changes. Commit or stash first. Use `/egc-prp-commit` to commit." | | Has commits ahead | `git log origin/..HEAD` not empty | Stop: "No commits ahead of ``. Nothing to PR." | | No existing PR | `gh pr list --head --json number` is empty | Stop: "PR already exists: #. Use `gh pr view --web` to open it." | @@ -166,7 +166,7 @@ Artifacts referenced: Next steps: - gh pr view --web → open in browser - - /code-review → review the PR + - /egc-code-review → review the PR - gh pr merge → merge when ready ``` diff --git a/commands/prp-prd.toml b/commands/egc-prp-prd.toml similarity index 97% rename from commands/prp-prd.toml rename to commands/egc-prp-prd.toml index 28e40d2..f232a98 100644 --- a/commands/prp-prd.toml +++ b/commands/egc-prp-prd.toml @@ -386,7 +386,7 @@ After generating, report: ### To Start Implementation -Run: `/prp-plan .gemini/PRPs/prds/{name}.prd.md` +Run: `/egc-prp-plan .gemini/PRPs/prds/{name}.prd.md` This will automatically select the next pending phase and create an implementation plan. ``` @@ -430,9 +430,9 @@ This will automatically select the next pending phase and create an implementati ## Integration with ECC After PRD generation: -- Use `/prp-plan` to create implementation plans from PRD phases -- Use `/plan` for simpler planning without PRD structure -- Use `/save-session` to preserve PRD context across sessions +- Use `/egc-prp-plan` to create implementation plans from PRD phases +- Use `/egc-plan` for simpler planning without PRD structure +- Use `/egc-save-session` to preserve PRD context across sessions ## Success Criteria diff --git a/commands/prune.toml b/commands/egc-prune.toml similarity index 77% rename from commands/prune.toml rename to commands/egc-prune.toml index 452e864..9fced4a 100644 --- a/commands/prune.toml +++ b/commands/egc-prune.toml @@ -27,9 +27,9 @@ python3 ~/.gemini/skills/continuous-learning-v2/scripts/instinct-cli.py prune ## Usage ``` -/prune # Delete instincts older than 30 days -/prune --max-age 60 # Custom age threshold (days) -/prune --dry-run # Preview without deleting +/egc-prune # Delete instincts older than 30 days +/egc-prune --max-age 60 # Custom age threshold (days) +/egc-prune --dry-run # Preview without deleting ``` ''' diff --git a/commands/python-review.toml b/commands/egc-python-review.toml similarity index 96% rename from commands/python-review.toml rename to commands/egc-python-review.toml index 1d7ec44..b920a1f 100644 --- a/commands/python-review.toml +++ b/commands/egc-python-review.toml @@ -15,7 +15,7 @@ This command invokes the **python-reviewer** agent for comprehensive Python-spec ## When to Use -Use `/python-review` when: +Use `/egc-python-review` when: - After writing or modifying Python code - Before committing Python changes - Reviewing pull requests with Python code @@ -75,7 +75,7 @@ pytest --cov=app --cov-report=term-missing ## Example Usage ```text -User: /python-review +User: /egc-python-review Agent: # Python Code Review Report @@ -170,9 +170,9 @@ Run: `black app/routes/user.py app/services/auth.py` ## Integration with Other Commands - Use `/python-test` first to ensure tests pass -- Use `/code-review` for non-Python specific concerns -- Use `/python-review` before committing -- Use `/build-fix` if static analysis tools fail +- Use `/egc-code-review` for non-Python specific concerns +- Use `/egc-python-review` before committing +- Use `/egc-build-fix` if static analysis tools fail ## Framework-Specific Reviews diff --git a/commands/quality-gate.toml b/commands/egc-quality-gate.toml similarity index 92% rename from commands/quality-gate.toml rename to commands/egc-quality-gate.toml index b4520c7..8d9637b 100644 --- a/commands/quality-gate.toml +++ b/commands/egc-quality-gate.toml @@ -6,7 +6,7 @@ Run the ECC quality pipeline on demand for a file or project scope. ## Usage -`/quality-gate [path|.] [--fix] [--strict]` +`/egc-quality-gate [path|.] [--fix] [--strict]` - default target: current directory (`.`) - `--fix`: allow auto-format/fix where configured diff --git a/commands/refactor-clean.toml b/commands/egc-refactor-clean.toml similarity index 100% rename from commands/refactor-clean.toml rename to commands/egc-refactor-clean.toml diff --git a/commands/resume-session.toml b/commands/egc-resume-session.toml similarity index 81% rename from commands/resume-session.toml rename to commands/egc-resume-session.toml index bd4622d..05197bf 100644 --- a/commands/resume-session.toml +++ b/commands/egc-resume-session.toml @@ -1,13 +1,13 @@ description = 'Resume Session Command' prompt = ''' --- -description: Load the most recent session file from ~/.gemini/sessions/ and resume work with full context from where the last session ended. +description: Load the most recent session file from ~/.gemini/egc-sessions/ and resume work with full context from where the last session ended. --- # Resume Session Command Load the last saved session state and orient fully before doing any work. -This command is the counterpart to `/save-session`. +This command is the counterpart to `/egc-save-session`. ## When to Use @@ -19,10 +19,10 @@ This command is the counterpart to `/save-session`. ## Usage ``` -/resume-session # loads most recent file in ~/.gemini/sessions/ -/resume-session 2024-01-15 # loads most recent session for that date -/resume-session ~/.gemini/sessions/2024-01-15-session.tmp # loads a specific legacy-format file -/resume-session ~/.gemini/sessions/2024-01-15-abc123de-session.tmp # loads a current short-id session file +/egc-resume-session # loads most recent file in ~/.gemini/egc-sessions/ +/egc-resume-session 2024-01-15 # loads most recent session for that date +/egc-resume-session ~/.gemini/egc-sessions/2024-01-15-session.tmp # loads a specific legacy-format file +/egc-resume-session ~/.gemini/egc-sessions/2024-01-15-abc123de-session.tmp # loads a current short-id session file ``` ## Process @@ -31,18 +31,18 @@ This command is the counterpart to `/save-session`. If no argument provided: -1. Check `~/.gemini/sessions/` +1. Check `~/.gemini/egc-sessions/` 2. Pick the most recently modified `*-session.tmp` file 3. If the folder does not exist or has no matching files, tell the user: ``` - No session files found in ~/.gemini/sessions/ - Run /save-session at the end of a session to create one. + No session files found in ~/.gemini/egc-sessions/ + Run /egc-save-session at the end of a session to create one. ``` Then stop. If an argument is provided: -- If it looks like a date (`YYYY-MM-DD`), search `~/.gemini/sessions/` for files matching +- If it looks like a date (`YYYY-MM-DD`), search `~/.gemini/egc-sessions/` for files matching `YYYY-MM-DD-session.tmp` (legacy format) or `YYYY-MM-DD--session.tmp` (current format) and load the most recently modified variant for that date - If it looks like a file path, read that file directly @@ -109,14 +109,14 @@ Note the gap — "⚠️ This session is from N days ago (threshold: 7 days). Th Read it and follow the same briefing process — the format is the same regardless of source. **Session file is empty or malformed:** -Report: "Session file found but appears empty or unreadable. You may need to create a new one with /save-session." +Report: "Session file found but appears empty or unreadable. You may need to create a new one with /egc-save-session." --- ## Example Output ``` -SESSION LOADED: /Users/you/.gemini/sessions/2024-01-15-abc123de-session.tmp +SESSION LOADED: /Users/you/.gemini/egc-sessions/2024-01-15-abc123de-session.tmp ════════════════════════════════════════════════ PROJECT: my-app — JWT Authentication @@ -154,6 +154,6 @@ Ready to continue. What would you like to do? - Never modify the session file when loading it — it's a read-only historical record - The briefing format is fixed — do not skip sections even if they are empty - "What Not To Retry" must always be shown, even if it just says "None" — it's too important to miss -- After resuming, the user may want to run `/save-session` again at the end of the new session to create a new dated file +- After resuming, the user may want to run `/egc-save-session` again at the end of the new session to create a new dated file ''' diff --git a/commands/review-pr.toml b/commands/egc-review-pr.toml similarity index 84% rename from commands/review-pr.toml rename to commands/egc-review-pr.toml index 40670dc..f904638 100644 --- a/commands/review-pr.toml +++ b/commands/egc-review-pr.toml @@ -4,7 +4,7 @@ Run a comprehensive multi-perspective review of a pull request. ## Usage -`/review-pr [PR-number-or-URL] [--focus=comments|tests|errors|types|code|simplify]` +`/egc-review-pr [PR-number-or-URL] [--focus=comments|tests|errors|types|code|simplify]` If no PR is specified, review the current branch's PR. If no focus is specified, run the full review stack. @@ -36,7 +36,7 @@ Only report issues with confidence >= 80: ## Related Commands -- `/code-review` — Review uncommitted changes -- `/quality-gate` — Quality gate checks +- `/egc-code-review` — Review uncommitted changes +- `/egc-quality-gate` — Quality gate checks ''' diff --git a/commands/rules-distill.toml b/commands/egc-rules-distill.toml similarity index 65% rename from commands/rules-distill.toml rename to commands/egc-rules-distill.toml index 62a3358..62340df 100644 --- a/commands/rules-distill.toml +++ b/commands/egc-rules-distill.toml @@ -1,10 +1,10 @@ -description = '/rules-distill — Distill Principles from Skills into Rules' +description = '/egc-rules-distill — Distill Principles from Skills into Rules' prompt = ''' --- description: "Scan skills to extract cross-cutting principles and distill them into rules" --- -# /rules-distill — Distill Principles from Skills into Rules +# /egc-rules-distill — Distill Principles from Skills into Rules Scan installed skills, extract cross-cutting principles, and distill them into rules. diff --git a/commands/rust-build.toml b/commands/egc-rust-build.toml similarity index 95% rename from commands/rust-build.toml rename to commands/egc-rust-build.toml index a07ef48..28a488d 100644 --- a/commands/rust-build.toml +++ b/commands/egc-rust-build.toml @@ -18,7 +18,7 @@ This command invokes the **rust-build-resolver** agent to incrementally fix Rust ## When to Use -Use `/rust-build` when: +Use `/egc-rust-build` when: - `cargo build` or `cargo check` fails with errors - `cargo clippy` reports warnings - Borrow checker or lifetime errors block compilation @@ -47,7 +47,7 @@ if command -v cargo-audit >/dev/null; then cargo audit; else echo "cargo-audit n ## Example Session ````text -User: /rust-build +User: /egc-rust-build Agent: # Rust Build Resolution @@ -179,9 +179,9 @@ The agent will stop and report if: ## Related Commands -- `/rust-test` - Run tests after build succeeds -- `/rust-review` - Review code quality -- `/verify` - Full verification loop +- `/egc-rust-test` - Run tests after build succeeds +- `/egc-rust-review` - Review code quality +- `/egc-verify` - Full verification loop ## Related diff --git a/commands/rust-review.toml b/commands/egc-rust-review.toml similarity index 93% rename from commands/rust-review.toml rename to commands/egc-rust-review.toml index 0aed2f1..237baae 100644 --- a/commands/rust-review.toml +++ b/commands/egc-rust-review.toml @@ -19,7 +19,7 @@ This command invokes the **rust-reviewer** agent for comprehensive Rust-specific ## When to Use -Use `/rust-review` when: +Use `/egc-rust-review` when: - After writing or modifying Rust code - Before committing Rust changes - Reviewing pull requests with Rust code @@ -73,7 +73,7 @@ if command -v cargo-audit >/dev/null; then cargo audit; else echo "cargo-audit n ## Example Usage ````text -User: /rust-review +User: /egc-rust-review Agent: # Rust Code Review Report @@ -133,10 +133,10 @@ Recommendation: Block merge until CRITICAL issue is fixed ## Integration with Other Commands -- Use `/rust-test` first to ensure tests pass -- Use `/rust-build` if build errors occur -- Use `/rust-review` before committing -- Use `/code-review` for non-Rust-specific concerns +- Use `/egc-rust-test` first to ensure tests pass +- Use `/egc-rust-build` if build errors occur +- Use `/egc-rust-review` before committing +- Use `/egc-code-review` for non-Rust-specific concerns ## Related diff --git a/commands/rust-test.toml b/commands/egc-rust-test.toml similarity index 96% rename from commands/rust-test.toml rename to commands/egc-rust-test.toml index 2ece6dc..759f514 100644 --- a/commands/rust-test.toml +++ b/commands/egc-rust-test.toml @@ -19,7 +19,7 @@ This command enforces test-driven development methodology for Rust code using `# ## When to Use -Use `/rust-test` when: +Use `/egc-rust-test` when: - Implementing new Rust functions, methods, or traits - Adding test coverage to existing Rust code - Fixing bugs (write failing test first) @@ -38,7 +38,7 @@ REPEAT -> Next test case ## Example Session ````text -User: /rust-test I need a function to validate user registration +User: /egc-rust-test I need a function to validate user registration Agent: # TDD Session: Registration Validator @@ -300,9 +300,9 @@ cargo test --no-fail-fast ## Related Commands -- `/rust-build` - Fix build errors -- `/rust-review` - Review code after implementation -- `/verify` - Run full verification loop +- `/egc-rust-build` - Fix build errors +- `/egc-rust-review` - Review code after implementation +- `/egc-verify` - Run full verification loop ## Related diff --git a/commands/santa-loop.toml b/commands/egc-santa-loop.toml similarity index 99% rename from commands/santa-loop.toml rename to commands/egc-santa-loop.toml index d8292d6..e0fe785 100644 --- a/commands/santa-loop.toml +++ b/commands/egc-santa-loop.toml @@ -11,7 +11,7 @@ Run two independent reviewers (Gemini Ultra + an external model) against the cur ## Usage ``` -/santa-loop [file-or-glob | description] +/egc-santa-loop [file-or-glob | description] ``` ## Workflow diff --git a/commands/save-session.toml b/commands/egc-save-session.toml similarity index 95% rename from commands/save-session.toml rename to commands/egc-save-session.toml index b3b9e03..de88efe 100644 --- a/commands/save-session.toml +++ b/commands/egc-save-session.toml @@ -1,7 +1,7 @@ description = 'Save Session Command' prompt = ''' --- -description: Save current session state to a dated file in ~/.gemini/sessions/ so work can be resumed in a future session with full context. +description: Save current session state to a dated file in ~/.gemini/egc-sessions/ so work can be resumed in a future session with full context. --- # Save Session Command @@ -31,12 +31,12 @@ Before writing the file, collect: Create the canonical sessions folder in the user's Gemini home directory: ```bash -mkdir -p ~/.gemini/sessions +mkdir -p ~/.gemini/egc-sessions ``` ### Step 3: Write the session file -Create `~/.gemini/sessions/YYYY-MM-DD--session.tmp`, using today's actual date and a short-id that satisfies the rules enforced by `SESSION_FILENAME_REGEX` in `session-manager.js`: +Create `~/.gemini/egc-sessions/YYYY-MM-DD--session.tmp`, using today's actual date and a short-id that satisfies the rules enforced by `SESSION_FILENAME_REGEX` in `session-manager.js`: - Allowed characters: lowercase `a-z`, digits `0-9`, hyphens `-` - Minimum length: 8 characters @@ -272,8 +272,8 @@ Then test with Postman — the response should include a `Set-Cookie` header. - Each session gets its own file — never append to a previous session's file - The "What Did NOT Work" section is the most critical — future sessions will blindly retry failed approaches without it - If the user asks to save mid-session (not just at the end), save what's known so far and mark in-progress items clearly -- The file is meant to be read by Gemini at the start of the next session via `/resume-session` -- Use the canonical global session store: `~/.gemini/sessions/` +- The file is meant to be read by Gemini at the start of the next session via `/egc-resume-session` +- Use the canonical global session store: `~/.gemini/egc-sessions/` - Prefer the short-id filename form (`YYYY-MM-DD--session.tmp`) for any new session file ''' diff --git a/commands/sessions.toml b/commands/egc-sessions.toml similarity index 87% rename from commands/sessions.toml rename to commands/egc-sessions.toml index 5d95166..3799431 100644 --- a/commands/sessions.toml +++ b/commands/egc-sessions.toml @@ -6,11 +6,11 @@ description: Manage Gemini Code session history, aliases, and session metadata. # Sessions Command -Manage Gemini Code session history - list, load, alias, and edit sessions stored in `~/.gemini/sessions/`. +Manage Gemini Code session history - list, load, alias, and edit sessions stored in `~/.gemini/egc-sessions/`. ## Usage -`/sessions [list|load|alias|info|help] [options]` +`/egc-sessions [list|load|alias|info|help] [options]` ## Actions @@ -18,14 +18,14 @@ Manage Gemini Code session history - list, load, alias, and edit sessions stored Display all sessions with metadata, filtering, and pagination. -Use `/sessions info` when you need operator-surface context for a swarm: branch, worktree path, and session recency. +Use `/egc-sessions info` when you need operator-surface context for a swarm: branch, worktree path, and session recency. ```bash -/sessions # List all sessions (default) -/sessions list # Same as above -/sessions list --limit 10 # Show 10 sessions -/sessions list --date 2026-02-01 # Filter by date -/sessions list --search abc # Search by session ID +/egc-sessions # List all sessions (default) +/egc-sessions list # Same as above +/egc-sessions list --limit 10 # Show 10 sessions +/egc-sessions list --date 2026-02-01 # Filter by date +/egc-sessions list --search abc # Search by session ID ``` **Script:** @@ -63,10 +63,10 @@ for (const s of result.sessions) { Load and display a session's content (by ID or alias). ```bash -/sessions load # Load session -/sessions load 2026-02-01 # By date (for no-id sessions) -/sessions load a1b2c3d4 # By short ID -/sessions load my-alias # By alias name +/egc-sessions load # Load session +/egc-sessions load 2026-02-01 # By date (for no-id sessions) +/egc-sessions load a1b2c3d4 # By short ID +/egc-sessions load my-alias # By alias name ``` **Script:** @@ -91,7 +91,7 @@ const size = sm.getSessionSize(session.sessionPath); const aliases = aa.getAliasesForSession(session.filename); console.log('Session: ' + session.filename); -console.log('Path: ~/.gemini/sessions/' + session.filename); +console.log('Path: ~/.gemini/egc-sessions/' + session.filename); console.log(''); console.log('Statistics:'); console.log(' Lines: ' + stats.lineCount); @@ -138,8 +138,8 @@ if (session.metadata.worktree) { Create a memorable alias for a session. ```bash -/sessions alias # Create alias -/sessions alias 2026-02-01 today-work # Create alias named "today-work" +/egc-sessions alias # Create alias +/egc-sessions alias 2026-02-01 today-work # Create alias named "today-work" ``` **Script:** @@ -152,7 +152,7 @@ const sessionId = process.argv[1]; const aliasName = process.argv[2]; if (!sessionId || !aliasName) { - console.log('Usage: /sessions alias '); + console.log('Usage: /egc-sessions alias '); process.exit(1); } @@ -178,8 +178,8 @@ if (result.success) { Delete an existing alias. ```bash -/sessions alias --remove # Remove alias -/sessions unalias # Same as above +/egc-sessions alias --remove # Remove alias +/egc-sessions unalias # Same as above ``` **Script:** @@ -189,7 +189,7 @@ const aa = require((()=>{var e=process.env.GEMINI_EXTENSION_ROOT;if(e&&e.trim()) const aliasName = process.argv[1]; if (!aliasName) { - console.log('Usage: /sessions alias --remove '); + console.log('Usage: /egc-sessions alias --remove '); process.exit(1); } @@ -208,7 +208,7 @@ if (result.success) { Show detailed information about a session. ```bash -/sessions info # Show session details +/egc-sessions info # Show session details ``` **Script:** @@ -258,7 +258,7 @@ if (aliases.length > 0) { Show all session aliases. ```bash -/sessions aliases # List all aliases +/egc-sessions aliases # List all aliases ``` **Script:** @@ -287,8 +287,8 @@ if (aliases.length === 0) { ## Operator Notes -- Session files persist `Project`, `Branch`, and `Worktree` in the header so `/sessions info` can disambiguate parallel tmux/worktree runs. -- For command-center style monitoring, combine `/sessions info`, `git diff --stat`, and the cost metrics emitted by `scripts/hooks/cost-tracker.js`. +- Session files persist `Project`, `Branch`, and `Worktree` in the header so `/egc-sessions info` can disambiguate parallel tmux/worktree runs. +- For command-center style monitoring, combine `/egc-sessions info`, `git diff --stat`, and the cost metrics emitted by `scripts/hooks/cost-tracker.js`. ## Arguments @@ -309,27 +309,27 @@ $ARGUMENTS: ```bash # List all sessions -/sessions list +/egc-sessions list # Create an alias for today's session -/sessions alias 2026-02-01 today +/egc-sessions alias 2026-02-01 today # Load session by alias -/sessions load today +/egc-sessions load today # Show session info -/sessions info today +/egc-sessions info today # Remove alias -/sessions alias --remove today +/egc-sessions alias --remove today # List all aliases -/sessions aliases +/egc-sessions aliases ``` ## Notes -- Sessions are stored as markdown files in `~/.gemini/sessions/` +- Sessions are stored as markdown files in `~/.gemini/egc-sessions/` - Aliases are stored in `~/.gemini/session-aliases.json` - Session IDs can be shortened (first 4-8 characters usually unique enough) - Use aliases for frequently referenced sessions diff --git a/commands/setup-pm.toml b/commands/egc-setup-pm.toml similarity index 100% rename from commands/setup-pm.toml rename to commands/egc-setup-pm.toml diff --git a/commands/skill-create.toml b/commands/egc-skill-create.toml similarity index 87% rename from commands/skill-create.toml rename to commands/egc-skill-create.toml index 6993b6a..360d4d8 100644 --- a/commands/skill-create.toml +++ b/commands/egc-skill-create.toml @@ -1,16 +1,16 @@ description = "Analyze local git history to extract coding patterns and generate SKILL.md files. Local version of the Skill Creator GitHub App." prompt = ''' -# /skill-create - Local Skill Generation +# /egc-skill-create - Local Skill Generation Analyze your repository's git history to extract coding patterns and generate SKILL.md files that teach Gemini your team's practices. ## Usage ```bash -/skill-create # Analyze current repo -/skill-create --commits 100 # Analyze last 100 commits -/skill-create --output ./skills # Custom output directory -/skill-create --instincts # Also generate instincts for continuous-learning-v2 +/egc-skill-create # Analyze current repo +/egc-skill-create --commits 100 # Analyze last 100 commits +/egc-skill-create --output ./skills # Custom output directory +/egc-skill-create --instincts # Also generate instincts for continuous-learning-v2 ``` ## What It Does @@ -100,7 +100,7 @@ Prefix commits with: feat:, fix:, chore:, docs:, test:, refactor: ## Example Output -Running `/skill-create` on a TypeScript project might produce: +Running `/egc-skill-create` on a TypeScript project might produce: ```markdown --- @@ -161,9 +161,9 @@ For advanced features (10k+ commits, team sharing, auto-PRs), use the [Skill Cre ## Related Commands -- `/instinct-import` - Import generated instincts -- `/instinct-status` - View learned instincts -- `/evolve` - Cluster instincts into skills/agents +- `/egc-instinct-import` - Import generated instincts +- `/egc-instinct-status` - View learned instincts +- `/egc-evolve` - Cluster instincts into skills/agents --- diff --git a/commands/skill-health.toml b/commands/egc-skill-health.toml similarity index 92% rename from commands/skill-health.toml rename to commands/egc-skill-health.toml index 12653fe..f7088cd 100644 --- a/commands/skill-health.toml +++ b/commands/egc-skill-health.toml @@ -36,16 +36,16 @@ node "$ECC_ROOT/scripts/skills-health.js" --dashboard --json ## Usage ``` -/skill-health # Full dashboard view -/skill-health --panel failures # Only failure clustering panel -/skill-health --json # Machine-readable JSON output +/egc-skill-health # Full dashboard view +/egc-skill-health --panel failures # Only failure clustering panel +/egc-skill-health --json # Machine-readable JSON output ``` ## What to Do 1. Run the skills-health.js script with --dashboard flag 2. Display the output to the user -3. If any skills are declining, highlight them and suggest running /evolve +3. If any skills are declining, highlight them and suggest running /egc-evolve 4. If there are pending amendments, suggest reviewing them ## Panels diff --git a/commands/tdd.toml b/commands/egc-tdd.toml similarity index 96% rename from commands/tdd.toml rename to commands/egc-tdd.toml index b18e4bf..f22a63a 100644 --- a/commands/tdd.toml +++ b/commands/egc-tdd.toml @@ -14,7 +14,7 @@ This command invokes the **tdd-guide** agent to enforce test-driven development ## When to Use -Use `/tdd` when: +Use `/egc-tdd` when: - Implementing new features - Adding new functions/components - Fixing bugs (write test that reproduces bug first) @@ -47,7 +47,7 @@ REPEAT: Next feature/scenario ## Example Usage ``` -User: /tdd I need a function to calculate market liquidity score +User: /egc-tdd I need a function to calculate market liquidity score Agent (tdd-guide): # TDD Session: Market Liquidity Score Calculator @@ -283,7 +283,7 @@ Coverage: 100% ✅ (Target: 80%) - External service calls - React components with hooks -**E2E Tests** (use `/e2e` command): +**E2E Tests** (use `/egc-e2e` command): - Critical user flows - Multi-step processes - Full stack integration @@ -309,11 +309,11 @@ Never skip the RED phase. Never write code before tests. ## Integration with Other Commands -- Use `/plan` first to understand what to build -- Use `/tdd` to implement with tests +- Use `/egc-plan` first to understand what to build +- Use `/egc-tdd` to implement with tests - Use `/build-and-fix` if build errors occur -- Use `/code-review` to review implementation -- Use `/test-coverage` to verify coverage +- Use `/egc-code-review` to review implementation +- Use `/egc-test-coverage` to verify coverage ## Related Agents diff --git a/commands/test-coverage.toml b/commands/egc-test-coverage.toml similarity index 100% rename from commands/test-coverage.toml rename to commands/egc-test-coverage.toml diff --git a/commands/update-codemaps.toml b/commands/egc-update-codemaps.toml similarity index 100% rename from commands/update-codemaps.toml rename to commands/egc-update-codemaps.toml diff --git a/commands/update-docs.toml b/commands/egc-update-docs.toml similarity index 100% rename from commands/update-docs.toml rename to commands/egc-update-docs.toml diff --git a/commands/verify.toml b/commands/egc-verify.toml similarity index 100% rename from commands/verify.toml rename to commands/egc-verify.toml diff --git a/docs/en/commands/README.md b/docs/en/commands/README.md index 003f65d..3b3793e 100644 --- a/docs/en/commands/README.md +++ b/docs/en/commands/README.md @@ -6,57 +6,57 @@ List of available commands provided by `everything-gemini-code`. | Command | Description | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------ | -| `/agent-sort` | Sort and organize agent configurations. | -| `/build-fix` | Analyze build errors and attempt to fix them automatically using the `build-error-resolver` agent. | -| `/checkpoint` | Stage all changes and commit them with an AI-generated message. | -| `/code-review` | Comprehensive code review of the current changes or specific files using the `code-reviewer` agent. | -| `/e2e` | Generate and run end-to-end tests with Playwright. | +| `/egc-agent-sort` | Sort and organize agent configurations. | +| `/egc-build-fix` | Analyze build errors and attempt to fix them automatically using the `build-error-resolver` agent. | +| `/egc-checkpoint` | Stage all changes and commit them with an AI-generated message. | +| `/egc-code-review` | Comprehensive code review of the current changes or specific files using the `code-reviewer` agent. | +| `/egc-e2e` | Generate and run end-to-end tests with Playwright. | | `/egc-plan` | Restate requirements, assess risks, and create step-by-step implementation plan. (alias: `/everything-gemini-code:plan`) | | `/egc-docs` | Look up current documentation for a library or topic via Context7. (alias: `/everything-gemini-code:docs`) | -| `/eval` | Manage eval-driven development workflow. | -| `/evolve` | Cluster related instincts into skills, commands, or agents. | -| `/feature-dev` | Guided feature development with codebase understanding. | -| `/flutter-build` | Fix Dart analyzer errors and Flutter build failures. | -| `/flutter-review` | Review Flutter/Dart code for idiomatic patterns. | -| `/flutter-test` | Run Flutter/Dart tests and fix failures. | -| `/gan-build` | GAN-style three-agent build loop. | -| `/gan-design` | GAN-style design harness for frontend quality. | -| `/go-build` | Fix Go build errors, go vet warnings, and linter issues incrementally. | -| `/go-review` | Comprehensive Go code review for idiomatic patterns, concurrency safety, error handling, and security. | -| `/go-test` | Enforce TDD workflow for Go. Write table-driven tests first, then implement. | -| `/hookify` | Create hooks to prevent unwanted behaviors. | -| `/hookify-configure` | Enable or disable hookify rules. | -| `/hookify-help` | Hookify system documentation. | -| `/hookify-list` | List configured hookify rules. | -| `/instinct-export` | Export learned instincts to a file for sharing. | -| `/instinct-import` | Import instincts from a file or another source. | -| `/instinct-status` | Show all currently learned instincts with confidence levels. | -| `/jira` | Jira ticket integration. | -| `/learn` | Extract reusable patterns from the current session. | -| `/multi-backend` | Backend-focused multi-agent workflow. | -| `/multi-execute` | Execute a multi-phase plan using multiple specialized agents. | -| `/multi-frontend` | Frontend-focused multi-agent workflow. | -| `/multi-plan` | Create a comprehensive implementation plan using multiple agents. | -| `/multi-workflow` | Multi-model collaborative development workflow. | -| `/orchestrate` | High-level orchestration for complex, multi-step tasks. | -| `/pm2` | Auto-analyze project and generate PM2 service commands. | -| `/prp-commit` | Natural language commit targeting. | -| `/prp-implement` | Execute implementation plans with validation. | -| `/prp-plan` | Create implementation plans with codebase analysis. | -| `/prp-pr` | Create GitHub PRs from current branch. | -| `/prp-prd` | Interactive PRD generator. | -| `/python-review` | Comprehensive Python code review for PEP 8, type hints, and security. | -| `/refactor-clean` | Identify and remove dead code, unused imports, and legacy artifacts. | -| `/review-pr` | Comprehensive multi-perspective PR review. | -| `/santa-loop` | Adversarial dual-review convergence loop. | -| `/sessions` | Manage and list active Gemini sessions. | -| `/setup-pm` | Configure your preferred package manager (npm/pnpm/yarn/bun). | -| `/skill-create` | Analyze local git history to extract coding patterns and generate `SKILL.md` files. | -| `/tdd` | Enforce test-driven development workflow. | -| `/test-coverage` | Analyze current test coverage and suggest tests to improve it. | -| `/update-codemaps` | Refresh the codebase maps to ensure the agent has the latest context. | -| `/update-docs` | Update documentation files based on recent code changes. | -| `/verify` | Run a full verification suite (lint, build, test). | +| `/egc-eval` | Manage eval-driven development workflow. | +| `/egc-evolve` | Cluster related instincts into skills, commands, or agents. | +| `/egc-feature-dev` | Guided feature development with codebase understanding. | +| `/egc-flutter-build` | Fix Dart analyzer errors and Flutter build failures. | +| `/egc-flutter-review` | Review Flutter/Dart code for idiomatic patterns. | +| `/egc-flutter-test` | Run Flutter/Dart tests and fix failures. | +| `/egc-gan-build` | GAN-style three-agent build loop. | +| `/egc-gan-design` | GAN-style design harness for frontend quality. | +| `/egc-go-build` | Fix Go build errors, go vet warnings, and linter issues incrementally. | +| `/egc-go-review` | Comprehensive Go code review for idiomatic patterns, concurrency safety, error handling, and security. | +| `/egc-go-test` | Enforce TDD workflow for Go. Write table-driven tests first, then implement. | +| `/egc-hookify` | Create hooks to prevent unwanted behaviors. | +| `/egc-hookify-configure` | Enable or disable hookify rules. | +| `/egc-hookify-help` | Hookify system documentation. | +| `/egc-hookify-list` | List configured hookify rules. | +| `/egc-instinct-export` | Export learned instincts to a file for sharing. | +| `/egc-instinct-import` | Import instincts from a file or another source. | +| `/egc-instinct-status` | Show all currently learned instincts with confidence levels. | +| `/egc-jira` | Jira ticket integration. | +| `/egc-learn` | Extract reusable patterns from the current session. | +| `/egc-multi-backend` | Backend-focused multi-agent workflow. | +| `/egc-multi-execute` | Execute a multi-phase plan using multiple specialized agents. | +| `/egc-multi-frontend` | Frontend-focused multi-agent workflow. | +| `/egc-multi-plan` | Create a comprehensive implementation plan using multiple agents. | +| `/egc-multi-workflow` | Multi-model collaborative development workflow. | +| `/egc-orchestrate` | High-level orchestration for complex, multi-step tasks. | +| `/egc-pm2` | Auto-analyze project and generate PM2 service commands. | +| `/egc-prp-commit` | Natural language commit targeting. | +| `/egc-prp-implement` | Execute implementation plans with validation. | +| `/egc-prp-plan` | Create implementation plans with codebase analysis. | +| `/egc-prp-pr` | Create GitHub PRs from current branch. | +| `/egc-prp-prd` | Interactive PRD generator. | +| `/egc-python-review` | Comprehensive Python code review for PEP 8, type hints, and security. | +| `/egc-refactor-clean` | Identify and remove dead code, unused imports, and legacy artifacts. | +| `/egc-review-pr` | Comprehensive multi-perspective PR review. | +| `/egc-santa-loop` | Adversarial dual-review convergence loop. | +| `/egc-sessions` | Manage and list active Gemini sessions. | +| `/egc-setup-pm` | Configure your preferred package manager (npm/pnpm/yarn/bun). | +| `/egc-skill-create` | Analyze local git history to extract coding patterns and generate `SKILL.md` files. | +| `/egc-tdd` | Enforce test-driven development workflow. | +| `/egc-test-coverage` | Analyze current test coverage and suggest tests to improve it. | +| `/egc-update-codemaps` | Refresh the codebase maps to ensure the agent has the latest context. | +| `/egc-update-docs` | Update documentation files based on recent code changes. | +| `/egc-verify` | Run a full verification suite (lint, build, test). | --- @@ -66,23 +66,23 @@ List of available commands provided by `everything-gemini-code`. Restate requirements, assess risks, and create step-by-step implementation plan. WAIT for user CONFIRM before touching any code. -### /tdd +### /egc-tdd Enforce test-driven development workflow. Scaffold interfaces, generate tests FIRST, then implement minimal code to pass. Ensure 80%+ coverage. -### /code-review +### /egc-code-review Comprehensive security and quality review of uncommitted changes. -### /build-fix +### /egc-build-fix Incrementally fix TypeScript and build errors. -### /refactor-clean +### /egc-refactor-clean Safely identify and remove dead code with test verification. -### /e2e +### /egc-e2e Generate and run end-to-end tests with Playwright. Creates test journeys, runs tests, captures screenshots/videos/traces, and uploads artifacts. @@ -90,31 +90,31 @@ Generate and run end-to-end tests with Playwright. Creates test journeys, runs t ## Multi-Agent Commands -### /multi-plan +### /egc-multi-plan Multi-model collaborative planning - Context retrieval + Dual-model analysis. -### /multi-execute +### /egc-multi-execute Multi-model collaborative execution - Get prototype from plan, refactor and implement, audit and deliver. -### /multi-backend +### /egc-multi-backend Backend-focused workflow (Research, Ideation, Plan, Execute, Optimize, Review). -### /multi-frontend +### /egc-multi-frontend Frontend-focused workflow (Research, Ideation, Plan, Execute, Optimize, Review). -### /multi-workflow +### /egc-multi-workflow Multi-model collaborative development workflow with intelligent routing: Frontend to Gemini, Backend to Codex. -### /orchestrate +### /egc-orchestrate Sequential agent workflow for complex tasks. -### /pm2 +### /egc-pm2 Auto-analyze project and generate PM2 service commands. @@ -122,35 +122,35 @@ Auto-analyze project and generate PM2 service commands. ## Language-Specific Commands -### /go-build +### /egc-go-build Fix Go build errors, go vet warnings, and linter issues incrementally. Invokes the go-build-resolver agent. -### /go-review +### /egc-go-review Comprehensive Go code review for idiomatic patterns, concurrency safety, error handling, and security. Invokes the go-reviewer agent. -### /go-test +### /egc-go-test Enforce TDD workflow for Go. Write table-driven tests first, then implement. Verify 80%+ coverage. -### /python-review +### /egc-python-review Comprehensive Python code review for PEP 8 compliance, type hints, security, and Pythonic idioms. Invokes the python-reviewer agent. -### /kotlin-build, /kotlin-review, /kotlin-test +### /egc-kotlin-build, /egc-kotlin-review, /egc-kotlin-test Kotlin build error resolution, code review, and TDD workflow. -### /cpp-build, /cpp-review, /cpp-test +### /egc-cpp-build, /egc-cpp-review, /egc-cpp-test C++ build error resolution, code review, and TDD workflow. -### /rust-build, /rust-review, /rust-test +### /egc-rust-build, /egc-rust-review, /egc-rust-test Rust build error resolution, code review, and TDD workflow. -### /gradle-build +### /egc-gradle-build Fix Gradle/Android build errors and dependency issues. @@ -158,27 +158,27 @@ Fix Gradle/Android build errors and dependency issues. ## Learning & Evolution Commands -### /learn +### /egc-learn Analyze the current session and extract any patterns worth saving as skills. -### /skill-create +### /egc-skill-create Analyze local git history to extract coding patterns and generate SKILL.md files. -### /evolve +### /egc-evolve Cluster related instincts into skills, commands, or agents. -### /instinct-import, /instinct-export, /instinct-status +### /egc-instinct-import, /egc-instinct-export, /egc-instinct-status Import, export, and view learned instincts. -### /learn-eval +### /egc-learn-eval Extract reusable patterns with self-evaluation. -### /promote, /prune, /projects +### /egc-promote, /egc-prune, /egc-projects Promote instincts to global scope, prune low-confidence instincts, list known projects. @@ -186,19 +186,19 @@ Promote instincts to global scope, prune low-confidence instincts, list known pr ## Utility Commands -### /setup-pm +### /egc-setup-pm Configure your preferred package manager (npm/pnpm/yarn/bun). -### /update-docs, /update-codemaps +### /egc-update-docs, /egc-update-codemaps Sync documentation and refresh codebase architecture maps. -### /verify, /checkpoint, /eval +### /egc-verify, /egc-checkpoint, /egc-eval Verification suite, workflow checkpoints, and eval-driven development. -### /sessions, /save-session, /resume-session +### /egc-sessions, /egc-save-session, /egc-resume-session Session management - list, save, load, and alias sessions. @@ -206,11 +206,11 @@ Session management - list, save, load, and alias sessions. Look up current documentation for a library or topic via Context7. -### /context-budget +### /egc-context-budget Monitor and manage context window usage. -### /model-route +### /egc-model-route Route tasks to the optimal model based on complexity. @@ -218,11 +218,11 @@ Route tasks to the optimal model based on complexity. ## Feature Development -### /feature-dev +### /egc-feature-dev Guided feature development workflow with codebase exploration, architecture design, and quality review. -### /review-pr +### /egc-review-pr Multi-perspective PR review using specialized agents (code-reviewer, comment-analyzer, pr-test-analyzer, etc.). @@ -230,11 +230,11 @@ Multi-perspective PR review using specialized agents (code-reviewer, comment-ana ## GAN Harness -### /gan-build +### /egc-gan-build Three-agent adversarial build loop: planner, generator, evaluator iterate until quality threshold is met. -### /gan-design +### /egc-gan-design Design-focused GAN loop emphasizing visual excellence and creative breakthroughs. @@ -242,7 +242,7 @@ Design-focused GAN loop emphasizing visual excellence and creative breakthroughs ## Hookify -### /hookify, /hookify-configure, /hookify-list, /hookify-help +### /egc-hookify, /egc-hookify-configure, /egc-hookify-list, /egc-hookify-help Create, configure, list, and document behavior-prevention hooks. @@ -250,7 +250,7 @@ Create, configure, list, and document behavior-prevention hooks. ## PRP (Plan-Review-Push) -### /prp-prd, /prp-plan, /prp-implement, /prp-commit, /prp-pr +### /egc-prp-prd, /egc-prp-plan, /egc-prp-implement, /egc-prp-commit, /egc-prp-pr Full development pipeline: PRD → plan → implement → commit → PR. @@ -258,6 +258,6 @@ Full development pipeline: PRD → plan → implement → commit → PR. ## Flutter -### /flutter-build, /flutter-review, /flutter-test +### /egc-flutter-build, /egc-flutter-review, /egc-flutter-test Flutter/Dart build error resolution, code review, and testing. diff --git a/docs/en/contributing/COMMAND-AGENT-MAP.md b/docs/en/contributing/COMMAND-AGENT-MAP.md index ea79554..a92ef7f 100644 --- a/docs/en/contributing/COMMAND-AGENT-MAP.md +++ b/docs/en/contributing/COMMAND-AGENT-MAP.md @@ -4,32 +4,32 @@ Quick reference for which agents are invoked by each command. | Command | Agent Used | Description | |---------|------------|-------------| -| `/plan` | planner | Feature implementation planning | -| `/tdd` | tdd-guide | Test-driven development | -| `/code-review` | code-reviewer | Code quality review | -| `/build-fix` | build-error-resolver | Fix build errors | -| `/e2e` | e2e-runner | E2E test generation | -| `/refactor-clean` | refactor-cleaner | Dead code removal | -| `/update-docs` | doc-updater | Documentation sync | -| `/verify` | — | Runs verification loop skill | -| `/eval` | — | Evaluation against criteria | -| `/go-build` | go-build-resolver | Go build error resolution | -| `/go-review` | go-reviewer | Go code review | -| `/go-test` | — | Go TDD workflow | -| `/python-review` | python-reviewer | Python code review | -| `/kotlin-build` | kotlin-build-resolver | Kotlin build errors | -| `/kotlin-review` | kotlin-reviewer | Kotlin code review | -| `/rust-build` | rust-build-resolver | Rust build errors | -| `/rust-review` | rust-reviewer | Rust code review | -| `/cpp-build` | cpp-build-resolver | C++ build errors | -| `/cpp-review` | cpp-reviewer | C++ code review | -| `/orchestrate` | — | Multi-agent coordination | -| `/multi-plan` | planner | Multi-agent task decomposition | -| `/sessions` | — | Session history management | -| `/skill-create` | — | Generate skills from git history | -| `/learn` | — | Extract patterns from session | -| `/evolve` | — | Cluster instincts into skills | -| `/checkpoint` | — | Save verification state | +| `/egc-plan` | planner | Feature implementation planning | +| `/egc-tdd` | tdd-guide | Test-driven development | +| `/egc-code-review` | code-reviewer | Code quality review | +| `/egc-build-fix` | build-error-resolver | Fix build errors | +| `/egc-e2e` | e2e-runner | E2E test generation | +| `/egc-refactor-clean` | refactor-cleaner | Dead code removal | +| `/egc-update-docs` | doc-updater | Documentation sync | +| `/egc-verify` | — | Runs verification loop skill | +| `/egc-eval` | — | Evaluation against criteria | +| `/egc-go-build` | go-build-resolver | Go build error resolution | +| `/egc-go-review` | go-reviewer | Go code review | +| `/egc-go-test` | — | Go TDD workflow | +| `/egc-python-review` | python-reviewer | Python code review | +| `/egc-kotlin-build` | kotlin-build-resolver | Kotlin build errors | +| `/egc-kotlin-review` | kotlin-reviewer | Kotlin code review | +| `/egc-rust-build` | rust-build-resolver | Rust build errors | +| `/egc-rust-review` | rust-reviewer | Rust code review | +| `/egc-cpp-build` | cpp-build-resolver | C++ build errors | +| `/egc-cpp-review` | cpp-reviewer | C++ code review | +| `/egc-orchestrate` | — | Multi-agent coordination | +| `/egc-multi-plan` | planner | Multi-agent task decomposition | +| `/egc-sessions` | — | Session history management | +| `/egc-skill-create` | — | Generate skills from git history | +| `/egc-learn` | — | Extract patterns from session | +| `/egc-evolve` | — | Cluster instincts into skills | +| `/egc-checkpoint` | — | Save verification state | --- diff --git a/docs/en/contributing/SKILL-PLACEMENT-POLICY.md b/docs/en/contributing/SKILL-PLACEMENT-POLICY.md index 0a848b4..5372e2e 100644 --- a/docs/en/contributing/SKILL-PLACEMENT-POLICY.md +++ b/docs/en/contributing/SKILL-PLACEMENT-POLICY.md @@ -25,7 +25,7 @@ Location: `skills//` with `SKILL.md` at root. Location: `~/.gemini/skills/learned//`. -Created by continuous-learning (evaluate-session hook, `/learn` command). +Created by continuous-learning (evaluate-session hook, `/egc-learn` command). - Not in repo. Not shipped. - Must have `.provenance.json` sibling to `SKILL.md`. @@ -44,7 +44,7 @@ User-installed skills from external sources (URL, file copy, etc.). Location: `~/.gemini/skills/evolved/`. -Generated by the `/evolve` command from clustered instincts. +Generated by the `/egc-evolve` command from clustered instincts. - Not in repo. Not shipped. - Provenance inherited from source instincts; no separate `.provenance.json` required. diff --git a/docs/en/contributing/VERIFICATION_GUIDE.md b/docs/en/contributing/VERIFICATION_GUIDE.md index 335d92d..df9cc64 100644 --- a/docs/en/contributing/VERIFICATION_GUIDE.md +++ b/docs/en/contributing/VERIFICATION_GUIDE.md @@ -36,10 +36,10 @@ You should see output similar to: ### Step 3: Verify Command Shims -Check if the short commands (e.g., `/tdd`) are created and point to the extension: +Check if the short commands (e.g., `/egc-tdd`) are created and point to the extension: ```bash -cat ~/.gemini/commands/tdd.toml | grep "@everything-gemini-code" +cat ~/.gemini/commands/egc-tdd.toml | grep "@everything-gemini-code" ``` **Expected Output:** @@ -52,10 +52,10 @@ If you see this, the shim is correctly configured. ## 2. Functionality Verification -### Test the `/tdd` Command +### Test the `/egc-tdd` Command 1. Start a Gemini session: `gemini` -2. Type `/tdd` and press Enter. +2. Type `/egc-tdd` and press Enter. 3. The prompt should load the **TDD Guide** agent from the extension. 4. Verify the agent name in the chat (it might show as "tdd-guide" or "everything-gemini-code.tdd-guide"). @@ -67,12 +67,12 @@ If you see this, the shim is correctly configured. ## Troubleshooting -If `/tdd` command is missing or not working: +If `/egc-tdd` command is missing or not working: 1. **Force Shim Regeneration:** Delete the existing shim and restart session: ```bash - rm ~/.gemini/commands/tdd.toml + rm ~/.gemini/commands/egc-tdd.toml gemini run "echo 'Regenerating...'" ``` 2. **Check Logs:** diff --git a/docs/en/contributing/token-optimization.md b/docs/en/contributing/token-optimization.md index 3adb1c3..e43497e 100644 --- a/docs/en/contributing/token-optimization.md +++ b/docs/en/contributing/token-optimization.md @@ -43,8 +43,8 @@ Each active MCP server consumes context tokens. Best practices: ### Session Management - Start fresh sessions for unrelated tasks -- Use `/checkpoint` to save state before context-intensive operations -- Use `/sessions` to review and resume past sessions +- Use `/egc-checkpoint` to save state before context-intensive operations +- Use `/egc-sessions` to review and resume past sessions ## Skill Loading Optimization @@ -74,15 +74,15 @@ export ECC_DISABLED_HOOKS="hook-id-1,hook-id-2" | Situation | Action | |-----------|--------| | Large codebase review | Use targeted agents (`@go-reviewer` not full review) | -| Repeated build fixes | Use language-specific resolver (`/go-build` vs generic) | -| Documentation updates | Use `/update-docs` instead of manual prompting | +| Repeated build fixes | Use language-specific resolver (`/egc-go-build` vs generic) | +| Documentation updates | Use `/egc-update-docs` instead of manual prompting | | Architecture decisions | Use `@architect` with clear scope boundaries | ## Continuous Learning for Token Efficiency -The `/learn` command extracts patterns from your sessions into reusable skills, reducing the need to re-explain context in future sessions: +The `/egc-learn` command extracts patterns from your sessions into reusable skills, reducing the need to re-explain context in future sessions: ```bash -/learn # Extract patterns from current session -/evolve # Cluster instincts into efficient skills +/egc-learn # Extract patterns from current session +/egc-evolve # Cluster instincts into efficient skills ``` diff --git a/docs/en/scripts/README.md b/docs/en/scripts/README.md index f8da9f9..4e35c76 100644 --- a/docs/en/scripts/README.md +++ b/docs/en/scripts/README.md @@ -15,7 +15,7 @@ This directory contains utility scripts for maintaining the Everything Gemini Co | Script | Description | |--------|-------------| -| `harness-audit.js` | Audits the repository against core Gemini CLI harness rules. Checks for the presence of required context optimization documents, eval coverage, required hooks, and security guards.

**Usage:** `node scripts/harness-audit.js --scope repo` | +| `harness-audit.js` | Audits the repository against core Gemini CLI harness rules. Checks for the presence of required context optimization documents, eval coverage, required hooks, and security guards.

**Usage:** `node scripts/egc-harness-audit.js --scope repo` | | `release.sh` | Synchronizes version numbers in `package.json`, `gemini-extension.json`, and `.gemini-plugin/plugin.json`, creates a git commit, and generates a version tag.

**Usage:** `./scripts/release.sh ` | ### Documentation Generation diff --git a/docs/ko-KR/README.md b/docs/ko-KR/README.md index 44815d5..bf5547f 100644 --- a/docs/ko-KR/README.md +++ b/docs/ko-KR/README.md @@ -57,13 +57,13 @@ Antigravity 사용자는 스크립트를 사용하세요: ```bash # 기능 구현 계획 -/plan "사용자 인증 추가" +/egc-plan "사용자 인증 추가" # TDD 워크플로우 시작 -/tdd "사용자 서비스 생성" +/egc-tdd "사용자 서비스 생성" # 코드 리뷰 실행 -/code-review +/egc-code-review # 에이전트 직접 호출 @architect "마이크로서비스 아키텍처 설계" @@ -141,14 +141,14 @@ everything-gemini-code/ │ └── 그 외 100개+ 스킬... │ ├── commands/ # Gemini CLI 커맨드 (.toml, 60개) -│ ├── plan.toml # /plan - 구현 계획 -│ ├── tdd.toml # /tdd - 테스트 주도 개발 -│ ├── code-review.toml # /code-review - 코드 리뷰 -│ ├── build-fix.toml # /build-fix - 빌드 에러 수정 -│ ├── e2e.toml # /e2e - E2E 테스트 생성 -│ ├── refactor-clean.toml # /refactor-clean - 코드 정리 +│ ├── plan.toml # /egc-plan - 구현 계획 +│ ├── tdd.toml # /egc-tdd - 테스트 주도 개발 +│ ├── code-review.toml # /egc-code-review - 코드 리뷰 +│ ├── build-fix.toml # /egc-build-fix - 빌드 에러 수정 +│ ├── e2e.toml # /egc-e2e - E2E 테스트 생성 +│ ├── refactor-clean.toml # /egc-refactor-clean - 코드 정리 │ ├── security-scan.toml # /security-scan - 보안 스캔 (AgentShield) -│ ├── update-docs.toml # /update-docs - 문서 업데이트 +│ ├── update-docs.toml # /egc-update-docs - 문서 업데이트 │ └── 그 외 50개+ 커맨드... │ ├── workflows/ # Antigravity 워크플로우 (.md) @@ -258,17 +258,17 @@ Incrementally fix build errors: | 하고 싶은 것 | 사용할 커맨드 | 사용되는 에이전트 | |-------------|-------------|--------------------| -| 새 기능 계획하기 | `/plan "인증 추가"` | planner | +| 새 기능 계획하기 | `/egc-plan "인증 추가"` | planner | | 시스템 아키텍처 설계 | `@architect "설계해줘"` | architect | -| 테스트를 먼저 작성하며 코딩 | `/tdd` | tdd-guide | -| 방금 작성한 코드 리뷰 | `/code-review` | code-reviewer | -| 빌드 실패 수정 | `/build-fix` | build-error-resolver | -| E2E 테스트 실행 | `/e2e` | e2e-runner | +| 테스트를 먼저 작성하며 코딩 | `/egc-tdd` | tdd-guide | +| 방금 작성한 코드 리뷰 | `/egc-code-review` | code-reviewer | +| 빌드 실패 수정 | `/egc-build-fix` | build-error-resolver | +| E2E 테스트 실행 | `/egc-e2e` | e2e-runner | | 보안 취약점 찾기 | `@security-reviewer "감사해줘"` | security-reviewer | -| 사용하지 않는 코드 제거 | `/refactor-clean` | refactor-cleaner | -| 문서 업데이트 | `/update-docs` | doc-updater | -| Go 코드 리뷰 | `/go-review` | go-reviewer | -| Python 코드 리뷰 | `/python-review` | python-reviewer | +| 사용하지 않는 코드 제거 | `/egc-refactor-clean` | refactor-cleaner | +| 문서 업데이트 | `/egc-update-docs` | doc-updater | +| Go 코드 리뷰 | `/egc-go-review` | go-reviewer | +| Python 코드 리뷰 | `/egc-python-review` | python-reviewer | | TypeScript 코드 리뷰 | `@typescript-reviewer` | typescript-reviewer | | 데이터베이스 쿼리 감사 | `@database-reviewer` | database-reviewer | @@ -276,24 +276,24 @@ Incrementally fix build errors: **새로운 기능 시작:** ``` -/plan "OAuth를 사용한 사용자 인증 추가" +/egc-plan "OAuth를 사용한 사용자 인증 추가" → planner가 구현 청사진 작성 -/tdd → tdd-guide가 테스트 먼저 작성 강제 -/code-review → code-reviewer가 코드 검토 +/egc-tdd → tdd-guide가 테스트 먼저 작성 강제 +/egc-code-review → code-reviewer가 코드 검토 ``` **버그 수정:** ``` -/tdd → tdd-guide: 버그를 재현하는 실패 테스트 작성 +/egc-tdd → tdd-guide: 버그를 재현하는 실패 테스트 작성 → 수정 구현, 테스트 통과 확인 -/code-review → code-reviewer: 회귀 검사 +/egc-code-review → code-reviewer: 회귀 검사 ``` **프로덕션 준비:** ``` @security-reviewer "보안 감사" → OWASP Top 10 감사 -/e2e → e2e-runner: 핵심 사용자 흐름 테스트 -/test-coverage → 80% 이상 커버리지 확인 +/egc-e2e → e2e-runner: 핵심 사용자 흐름 테스트 +/egc-test-coverage → 80% 이상 커버리지 확인 ``` --- diff --git a/docs/ko-KR/commands/README.md b/docs/ko-KR/commands/README.md index 400e418..f7e483e 100644 --- a/docs/ko-KR/commands/README.md +++ b/docs/ko-KR/commands/README.md @@ -6,57 +6,57 @@ | 명령어 | 설명 | | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------- | -| `/agent-sort` | 에이전트 설정을 정렬하고 관리합니다. | -| `/build-fix` | 빌드 오류를 분석하고 `build-error-resolver` 에이전트로 자동 수정을 시도합니다. | -| `/checkpoint` | 모든 변경 사항을 스테이징하고 AI 생성 메시지로 커밋합니다. | -| `/code-review` | `code-reviewer` 에이전트를 사용하여 현재 변경 사항에 대한 종합 코드 리뷰를 수행합니다. | -| `/e2e` | Playwright로 E2E 테스트를 생성하고 실행합니다. | +| `/egc-agent-sort` | 에이전트 설정을 정렬하고 관리합니다. | +| `/egc-build-fix` | 빌드 오류를 분석하고 `build-error-resolver` 에이전트로 자동 수정을 시도합니다. | +| `/egc-checkpoint` | 모든 변경 사항을 스테이징하고 AI 생성 메시지로 커밋합니다. | +| `/egc-code-review` | `code-reviewer` 에이전트를 사용하여 현재 변경 사항에 대한 종합 코드 리뷰를 수행합니다. | +| `/egc-e2e` | Playwright로 E2E 테스트를 생성하고 실행합니다. | | `/egc-plan` | 요구 사항을 재검토하고 단계별 구현 계획을 수립합니다. (별칭: `/everything-gemini-code:plan`) | | `/egc-docs` | Context7을 통해 라이브러리 또는 주제의 최신 문서를 조회합니다. (별칭: `/everything-gemini-code:docs`) | -| `/eval` | Eval 기반 개발 워크플로우를 관리합니다. | -| `/evolve` | 관련 인스팅트를 스킬, 커맨드 또는 에이전트로 클러스터링합니다. | -| `/feature-dev` | 코드베이스 이해 기반 가이드 기능 개발. | -| `/flutter-build` | Dart 분석기 오류 및 Flutter 빌드 실패 수정. | -| `/flutter-review` | Flutter/Dart 코드 관용 패턴 리뷰. | -| `/flutter-test` | Flutter/Dart 테스트 실행 및 실패 수정. | -| `/gan-build` | GAN 스타일 3-에이전트 빌드 루프. | -| `/gan-design` | 프론트엔드 품질을 위한 GAN 스타일 디자인 하네스. | -| `/go-build` | Go 빌드 오류, go vet 경고 및 린터 문제를 점진적으로 수정합니다. | -| `/hookify` | 원하지 않는 동작을 방지하는 훅 생성. | -| `/hookify-configure` | hookify 규칙 활성화/비활성화. | -| `/hookify-help` | hookify 시스템 문서. | -| `/hookify-list` | 설정된 hookify 규칙 목록. | -| `/jira` | Jira 티켓 통합. | -| `/go-review` | Go 코드 리뷰 — 관용 패턴, 동시성 안전성, 에러 처리, 보안 점검. | -| `/go-test` | Go TDD 워크플로우. 테이블 기반 테스트 먼저 작성 후 구현. | -| `/instinct-export` | 학습된 인스팅트를 파일로 내보냅니다. | -| `/instinct-import` | 파일 또는 외부 소스에서 인스팅트를 가져옵니다. | -| `/instinct-status` | 현재 학습된 모든 인스팅트와 신뢰도를 표시합니다. | -| `/learn` | 현재 세션에서 재사용 가능한 패턴을 추출합니다. | -| `/multi-backend` | 백엔드 중심 멀티 에이전트 워크플로우. | -| `/multi-execute` | 여러 전문 에이전트를 사용하여 멀티 페이즈 계획을 실행합니다. | -| `/multi-frontend` | 프론트엔드 중심 멀티 에이전트 워크플로우. | -| `/multi-plan` | 여러 에이전트를 사용하여 종합적인 구현 계획을 수립합니다. | -| `/multi-workflow` | 멀티 모델 협업 개발 워크플로우. | -| `/orchestrate` | 복잡한 멀티 스텝 작업을 위한 상위 오케스트레이션. | -| `/pm2` | 프로젝트를 분석하고 PM2 서비스 명령을 자동 생성합니다. | -| `/prp-commit` | 자연어 기반 커밋 타겟팅. | -| `/prp-implement` | 검증을 포함한 구현 계획 실행. | -| `/prp-plan` | 코드베이스 분석 기반 구현 계획 생성. | -| `/prp-pr` | 현재 브랜치에서 GitHub PR 생성. | -| `/prp-prd` | 대화형 PRD 생성기. | -| `/python-review` | PEP 8, 타입 힌트, 보안에 대한 종합 Python 코드 리뷰. | -| `/refactor-clean` | 불필요한 코드, 미사용 임포트 및 레거시 아티팩트를 식별하고 제거합니다. | -| `/review-pr` | 종합 멀티 관점 PR 리뷰. | -| `/santa-loop` | 적대적 이중 리뷰 수렴 루프. | -| `/sessions` | 활성 Gemini 세션을 관리하고 나열합니다. | -| `/setup-pm` | 선호하는 패키지 매니저(npm/pnpm/yarn/bun)를 설정합니다. | -| `/skill-create` | 로컬 git 히스토리를 분석하여 코딩 패턴을 추출하고 `SKILL.md` 파일을 생성합니다. | -| `/tdd` | 테스트 주도 개발 워크플로우를 적용합니다. | -| `/test-coverage` | 현재 테스트 커버리지를 분석하고 개선 방안을 제안합니다. | -| `/update-codemaps` | 코드베이스 맵을 새로 고쳐 최신 컨텍스트를 반영합니다. | -| `/update-docs` | 최근 코드 변경에 따라 문서를 업데이트합니다. | -| `/verify` | 전체 검증 스위트(린트, 빌드, 테스트)를 실행합니다. | +| `/egc-eval` | Eval 기반 개발 워크플로우를 관리합니다. | +| `/egc-evolve` | 관련 인스팅트를 스킬, 커맨드 또는 에이전트로 클러스터링합니다. | +| `/egc-feature-dev` | 코드베이스 이해 기반 가이드 기능 개발. | +| `/egc-flutter-build` | Dart 분석기 오류 및 Flutter 빌드 실패 수정. | +| `/egc-flutter-review` | Flutter/Dart 코드 관용 패턴 리뷰. | +| `/egc-flutter-test` | Flutter/Dart 테스트 실행 및 실패 수정. | +| `/egc-gan-build` | GAN 스타일 3-에이전트 빌드 루프. | +| `/egc-gan-design` | 프론트엔드 품질을 위한 GAN 스타일 디자인 하네스. | +| `/egc-go-build` | Go 빌드 오류, go vet 경고 및 린터 문제를 점진적으로 수정합니다. | +| `/egc-hookify` | 원하지 않는 동작을 방지하는 훅 생성. | +| `/egc-hookify-configure` | hookify 규칙 활성화/비활성화. | +| `/egc-hookify-help` | hookify 시스템 문서. | +| `/egc-hookify-list` | 설정된 hookify 규칙 목록. | +| `/egc-jira` | Jira 티켓 통합. | +| `/egc-go-review` | Go 코드 리뷰 — 관용 패턴, 동시성 안전성, 에러 처리, 보안 점검. | +| `/egc-go-test` | Go TDD 워크플로우. 테이블 기반 테스트 먼저 작성 후 구현. | +| `/egc-instinct-export` | 학습된 인스팅트를 파일로 내보냅니다. | +| `/egc-instinct-import` | 파일 또는 외부 소스에서 인스팅트를 가져옵니다. | +| `/egc-instinct-status` | 현재 학습된 모든 인스팅트와 신뢰도를 표시합니다. | +| `/egc-learn` | 현재 세션에서 재사용 가능한 패턴을 추출합니다. | +| `/egc-multi-backend` | 백엔드 중심 멀티 에이전트 워크플로우. | +| `/egc-multi-execute` | 여러 전문 에이전트를 사용하여 멀티 페이즈 계획을 실행합니다. | +| `/egc-multi-frontend` | 프론트엔드 중심 멀티 에이전트 워크플로우. | +| `/egc-multi-plan` | 여러 에이전트를 사용하여 종합적인 구현 계획을 수립합니다. | +| `/egc-multi-workflow` | 멀티 모델 협업 개발 워크플로우. | +| `/egc-orchestrate` | 복잡한 멀티 스텝 작업을 위한 상위 오케스트레이션. | +| `/egc-pm2` | 프로젝트를 분석하고 PM2 서비스 명령을 자동 생성합니다. | +| `/egc-prp-commit` | 자연어 기반 커밋 타겟팅. | +| `/egc-prp-implement` | 검증을 포함한 구현 계획 실행. | +| `/egc-prp-plan` | 코드베이스 분석 기반 구현 계획 생성. | +| `/egc-prp-pr` | 현재 브랜치에서 GitHub PR 생성. | +| `/egc-prp-prd` | 대화형 PRD 생성기. | +| `/egc-python-review` | PEP 8, 타입 힌트, 보안에 대한 종합 Python 코드 리뷰. | +| `/egc-refactor-clean` | 불필요한 코드, 미사용 임포트 및 레거시 아티팩트를 식별하고 제거합니다. | +| `/egc-review-pr` | 종합 멀티 관점 PR 리뷰. | +| `/egc-santa-loop` | 적대적 이중 리뷰 수렴 루프. | +| `/egc-sessions` | 활성 Gemini 세션을 관리하고 나열합니다. | +| `/egc-setup-pm` | 선호하는 패키지 매니저(npm/pnpm/yarn/bun)를 설정합니다. | +| `/egc-skill-create` | 로컬 git 히스토리를 분석하여 코딩 패턴을 추출하고 `SKILL.md` 파일을 생성합니다. | +| `/egc-tdd` | 테스트 주도 개발 워크플로우를 적용합니다. | +| `/egc-test-coverage` | 현재 테스트 커버리지를 분석하고 개선 방안을 제안합니다. | +| `/egc-update-codemaps` | 코드베이스 맵을 새로 고쳐 최신 컨텍스트를 반영합니다. | +| `/egc-update-docs` | 최근 코드 변경에 따라 문서를 업데이트합니다. | +| `/egc-verify` | 전체 검증 스위트(린트, 빌드, 테스트)를 실행합니다. | --- @@ -66,23 +66,23 @@ 요구 사항을 재검토하고, 위험을 평가하며, 단계별 구현 계획을 수립합니다. 코드 작성 전 사용자 확인을 기다립니다. -### /tdd +### /egc-tdd 테스트 주도 개발 워크플로우. 인터페이스 스캐폴딩, 테스트 먼저 생성, 최소 코드 구현. 80%+ 커버리지 보장. -### /code-review +### /egc-code-review 커밋되지 않은 변경 사항에 대한 종합 보안 및 품질 리뷰. -### /build-fix +### /egc-build-fix TypeScript 및 빌드 오류를 점진적으로 수정합니다. -### /refactor-clean +### /egc-refactor-clean 테스트 검증을 통해 불필요한 코드를 안전하게 식별하고 제거합니다. -### /e2e +### /egc-e2e Playwright로 E2E 테스트를 생성하고 실행합니다. 테스트 여정 생성, 스크린샷/비디오/트레이스 캡처. @@ -90,31 +90,31 @@ Playwright로 E2E 테스트를 생성하고 실행합니다. 테스트 여정 ## 멀티 에이전트 커맨드 -### /multi-plan +### /egc-multi-plan 멀티 모델 협업 계획 — 컨텍스트 검색 + 이중 모델 분석. -### /multi-execute +### /egc-multi-execute 멀티 모델 협업 실행 — 프로토타입, 리팩토링 및 구현, 감사 및 전달. -### /multi-backend +### /egc-multi-backend 백엔드 중심 워크플로우 (조사, 아이디어, 계획, 실행, 최적화, 리뷰). -### /multi-frontend +### /egc-multi-frontend 프론트엔드 중심 워크플로우 (조사, 아이디어, 계획, 실행, 최적화, 리뷰). -### /multi-workflow +### /egc-multi-workflow 멀티 모델 협업 개발 워크플로우. 프론트엔드는 Gemini, 백엔드는 Codex로 지능적 라우팅. -### /orchestrate +### /egc-orchestrate 복잡한 작업을 위한 순차적 에이전트 워크플로우. -### /pm2 +### /egc-pm2 프로젝트를 분석하고 PM2 서비스 명령을 자동 생성합니다. @@ -122,27 +122,27 @@ Playwright로 E2E 테스트를 생성하고 실행합니다. 테스트 여정 ## 언어별 커맨드 -### /go-build, /go-review, /go-test +### /egc-go-build, /egc-go-review, /egc-go-test Go 빌드 오류 수정, 코드 리뷰, TDD 워크플로우. -### /python-review +### /egc-python-review PEP 8, 타입 힌트, 보안에 대한 종합 Python 코드 리뷰. -### /kotlin-build, /kotlin-review, /kotlin-test +### /egc-kotlin-build, /egc-kotlin-review, /egc-kotlin-test Kotlin 빌드 오류 수정, 코드 리뷰, TDD 워크플로우. -### /cpp-build, /cpp-review, /cpp-test +### /egc-cpp-build, /egc-cpp-review, /egc-cpp-test C++ 빌드 오류 수정, 코드 리뷰, TDD 워크플로우. -### /rust-build, /rust-review, /rust-test +### /egc-rust-build, /egc-rust-review, /egc-rust-test Rust 빌드 오류 수정, 코드 리뷰, TDD 워크플로우. -### /gradle-build +### /egc-gradle-build Gradle/Android 빌드 오류 및 의존성 문제 수정. @@ -150,27 +150,27 @@ Gradle/Android 빌드 오류 및 의존성 문제 수정. ## 학습 및 진화 커맨드 -### /learn +### /egc-learn 현재 세션을 분석하여 스킬로 저장할 만한 패턴을 추출합니다. -### /skill-create +### /egc-skill-create 로컬 git 히스토리를 분석하여 코딩 패턴을 추출하고 SKILL.md 파일을 생성합니다. -### /evolve +### /egc-evolve 관련 인스팅트를 스킬, 커맨드 또는 에이전트로 클러스터링합니다. -### /instinct-import, /instinct-export, /instinct-status +### /egc-instinct-import, /egc-instinct-export, /egc-instinct-status 인스팅트 가져오기, 내보내기, 조회. -### /learn-eval +### /egc-learn-eval 자체 평가를 통한 재사용 가능한 패턴 추출. -### /promote, /prune, /projects +### /egc-promote, /egc-prune, /egc-projects 인스팅트 글로벌 승격, 저신뢰도 인스팅트 정리, 알려진 프로젝트 목록. @@ -178,19 +178,19 @@ Gradle/Android 빌드 오류 및 의존성 문제 수정. ## 유틸리티 커맨드 -### /setup-pm +### /egc-setup-pm 선호하는 패키지 매니저(npm/pnpm/yarn/bun)를 설정합니다. -### /update-docs, /update-codemaps +### /egc-update-docs, /egc-update-codemaps 문서 동기화 및 코드베이스 아키텍처 맵 새로 고침. -### /verify, /checkpoint, /eval +### /egc-verify, /egc-checkpoint, /egc-eval 검증 스위트, 워크플로우 체크포인트, eval 기반 개발. -### /sessions, /save-session, /resume-session +### /egc-sessions, /egc-save-session, /egc-resume-session 세션 관리 — 나열, 저장, 불러오기, 별칭 설정. @@ -198,11 +198,11 @@ Gradle/Android 빌드 오류 및 의존성 문제 수정. Context7을 통해 라이브러리 또는 주제의 최신 문서를 조회합니다. -### /context-budget +### /egc-context-budget 컨텍스트 윈도우 사용량을 모니터링하고 관리합니다. -### /model-route +### /egc-model-route 작업 복잡도에 따라 최적 모델로 라우팅합니다. @@ -210,11 +210,11 @@ Context7을 통해 라이브러리 또는 주제의 최신 문서를 조회합 ## 기능 개발 -### /feature-dev +### /egc-feature-dev 코드베이스 탐색, 아키텍처 설계, 품질 리뷰를 포함한 가이드 기능 개발 워크플로우. -### /review-pr +### /egc-review-pr 전문 에이전트(code-reviewer, comment-analyzer, pr-test-analyzer 등)를 사용한 멀티 관점 PR 리뷰. @@ -222,11 +222,11 @@ Context7을 통해 라이브러리 또는 주제의 최신 문서를 조회합 ## GAN 하네스 -### /gan-build +### /egc-gan-build 3-에이전트 적대적 빌드 루프: 플래너, 제너레이터, 이밸류에이터가 품질 임계값까지 반복. -### /gan-design +### /egc-gan-design 시각적 우수성과 창의적 돌파를 강조하는 디자인 중심 GAN 루프. @@ -234,7 +234,7 @@ Context7을 통해 라이브러리 또는 주제의 최신 문서를 조회합 ## Hookify -### /hookify, /hookify-configure, /hookify-list, /hookify-help +### /egc-hookify, /egc-hookify-configure, /egc-hookify-list, /egc-hookify-help 동작 방지 훅 생성, 설정, 목록 조회, 문서. @@ -242,7 +242,7 @@ Context7을 통해 라이브러리 또는 주제의 최신 문서를 조회합 ## PRP (Plan-Review-Push) -### /prp-prd, /prp-plan, /prp-implement, /prp-commit, /prp-pr +### /egc-prp-prd, /egc-prp-plan, /egc-prp-implement, /egc-prp-commit, /egc-prp-pr 전체 개발 파이프라인: PRD → 계획 → 구현 → 커밋 → PR. @@ -250,6 +250,6 @@ Context7을 통해 라이브러리 또는 주제의 최신 문서를 조회합 ## Flutter -### /flutter-build, /flutter-review, /flutter-test +### /egc-flutter-build, /egc-flutter-review, /egc-flutter-test Flutter/Dart 빌드 오류 수정, 코드 리뷰, 테스팅. diff --git a/docs/ko-KR/contributing/COMMAND-AGENT-MAP.md b/docs/ko-KR/contributing/COMMAND-AGENT-MAP.md index 776297f..180e1b9 100644 --- a/docs/ko-KR/contributing/COMMAND-AGENT-MAP.md +++ b/docs/ko-KR/contributing/COMMAND-AGENT-MAP.md @@ -7,31 +7,31 @@ | 커맨드 | 사용 에이전트 | 설명 | |--------|-------------|------| | `/egc-plan` | planner | 기능 구현 계획 수립 | -| `/tdd` | tdd-guide | 테스트 주도 개발 | -| `/code-review` | code-reviewer | 코드 품질 리뷰 | -| `/build-fix` | build-error-resolver | 빌드 오류 수정 | -| `/e2e` | e2e-runner | E2E 테스트 생성 | -| `/refactor-clean` | refactor-cleaner | 불필요한 코드 제거 | -| `/update-docs` | doc-updater | 문서 동기화 | -| `/verify` | — | 검증 루프 스킬 실행 | -| `/eval` | — | 기준 대비 평가 | -| `/go-build` | go-build-resolver | Go 빌드 오류 수정 | -| `/go-review` | go-reviewer | Go 코드 리뷰 | -| `/go-test` | — | Go TDD 워크플로우 | -| `/python-review` | python-reviewer | Python 코드 리뷰 | -| `/kotlin-build` | kotlin-build-resolver | Kotlin 빌드 오류 | -| `/kotlin-review` | kotlin-reviewer | Kotlin 코드 리뷰 | -| `/rust-build` | rust-build-resolver | Rust 빌드 오류 | -| `/rust-review` | rust-reviewer | Rust 코드 리뷰 | -| `/cpp-build` | cpp-build-resolver | C++ 빌드 오류 | -| `/cpp-review` | cpp-reviewer | C++ 코드 리뷰 | -| `/orchestrate` | — | 멀티 에이전트 조율 | -| `/multi-plan` | planner | 멀티 에이전트 작업 분해 | -| `/sessions` | — | 세션 히스토리 관리 | -| `/skill-create` | — | git 히스토리에서 스킬 생성 | -| `/learn` | — | 세션에서 패턴 추출 | -| `/evolve` | — | 인스팅트를 스킬로 클러스터링 | -| `/checkpoint` | — | 검증 상태 저장 | +| `/egc-tdd` | tdd-guide | 테스트 주도 개발 | +| `/egc-code-review` | code-reviewer | 코드 품질 리뷰 | +| `/egc-build-fix` | build-error-resolver | 빌드 오류 수정 | +| `/egc-e2e` | e2e-runner | E2E 테스트 생성 | +| `/egc-refactor-clean` | refactor-cleaner | 불필요한 코드 제거 | +| `/egc-update-docs` | doc-updater | 문서 동기화 | +| `/egc-verify` | — | 검증 루프 스킬 실행 | +| `/egc-eval` | — | 기준 대비 평가 | +| `/egc-go-build` | go-build-resolver | Go 빌드 오류 수정 | +| `/egc-go-review` | go-reviewer | Go 코드 리뷰 | +| `/egc-go-test` | — | Go TDD 워크플로우 | +| `/egc-python-review` | python-reviewer | Python 코드 리뷰 | +| `/egc-kotlin-build` | kotlin-build-resolver | Kotlin 빌드 오류 | +| `/egc-kotlin-review` | kotlin-reviewer | Kotlin 코드 리뷰 | +| `/egc-rust-build` | rust-build-resolver | Rust 빌드 오류 | +| `/egc-rust-review` | rust-reviewer | Rust 코드 리뷰 | +| `/egc-cpp-build` | cpp-build-resolver | C++ 빌드 오류 | +| `/egc-cpp-review` | cpp-reviewer | C++ 코드 리뷰 | +| `/egc-orchestrate` | — | 멀티 에이전트 조율 | +| `/egc-multi-plan` | planner | 멀티 에이전트 작업 분해 | +| `/egc-sessions` | — | 세션 히스토리 관리 | +| `/egc-skill-create` | — | git 히스토리에서 스킬 생성 | +| `/egc-learn` | — | 세션에서 패턴 추출 | +| `/egc-evolve` | — | 인스팅트를 스킬로 클러스터링 | +| `/egc-checkpoint` | — | 검증 상태 저장 | --- diff --git a/docs/ko-KR/contributing/SKILL-PLACEMENT-POLICY.md b/docs/ko-KR/contributing/SKILL-PLACEMENT-POLICY.md index db7a207..a90c719 100644 --- a/docs/ko-KR/contributing/SKILL-PLACEMENT-POLICY.md +++ b/docs/ko-KR/contributing/SKILL-PLACEMENT-POLICY.md @@ -27,7 +27,7 @@ 위치: `~/.gemini/skills/learned//` -지속적 학습(evaluate-session 훅, `/learn` 커맨드)에 의해 생성됨. +지속적 학습(evaluate-session 훅, `/egc-learn` 커맨드)에 의해 생성됨. - 저장소에 없음. 배포 안 됨 - `SKILL.md` 옆에 `.provenance.json` 파일 필수 @@ -46,7 +46,7 @@ 위치: `~/.gemini/skills/evolved/` -`/evolve` 커맨드에 의해 클러스터링된 인스팅트에서 생성됨. +`/egc-evolve` 커맨드에 의해 클러스터링된 인스팅트에서 생성됨. - 저장소에 없음. 배포 안 됨 - 출처는 소스 인스팅트에서 상속됨. 별도 `.provenance.json` 불필요 diff --git a/docs/ko-KR/contributing/VERIFICATION_GUIDE.md b/docs/ko-KR/contributing/VERIFICATION_GUIDE.md index 8baf2a1..0a03d5b 100644 --- a/docs/ko-KR/contributing/VERIFICATION_GUIDE.md +++ b/docs/ko-KR/contributing/VERIFICATION_GUIDE.md @@ -34,17 +34,17 @@ gemini run "echo '세션 초기화 중...'" ```bash # Gemini CLI 내에서 -/tdd +/egc-tdd ``` TDD 가이드 에이전트가 로드되어야 합니다. ## 2. 기능 검증 -### `/tdd` 커맨드 테스트 +### `/egc-tdd` 커맨드 테스트 1. Gemini 세션 시작: `gemini` -2. `/tdd` 입력 후 Enter +2. `/egc-tdd` 입력 후 Enter 3. **TDD Guide** 에이전트가 확장에서 로드되어야 합니다 ### 훅 테스트 @@ -55,7 +55,7 @@ TDD 가이드 에이전트가 로드되어야 합니다. ## 문제 해결 -`/tdd` 커맨드가 없거나 작동하지 않는 경우: +`/egc-tdd` 커맨드가 없거나 작동하지 않는 경우: 1. **로그 확인:** 출력에서 `[SessionStart]` 오류를 확인하세요. diff --git a/docs/ko-KR/contributing/token-optimization.md b/docs/ko-KR/contributing/token-optimization.md index ac49fbc..725af1a 100644 --- a/docs/ko-KR/contributing/token-optimization.md +++ b/docs/ko-KR/contributing/token-optimization.md @@ -45,8 +45,8 @@ export GEMINI_MODEL=gemini-2.5-pro ### 세션 관리 - 관련 없는 작업은 새 세션에서 시작 -- 컨텍스트 집약적 작업 전에 `/checkpoint`으로 상태 저장 -- `/sessions`으��� 과거 세션을 확인하고 재개 +- 컨텍스트 집약적 작업 전에 `/egc-checkpoint`으로 상태 저장 +- `/egc-sessions`으��� 과거 세션을 확인하고 재개 ## 스킬 로딩 최적화 @@ -76,15 +76,15 @@ export ECC_DISABLED_HOOKS="hook-id-1,hook-id-2" | 상황 | 조치 | |------|------| | 대규모 코드베이스 리뷰 | 대상 에이전트 사용 (전체 리뷰 대신 `@go-reviewer`) | -| 반복적인 빌드 수정 | 언어별 리졸버 사용 (일반 대신 `/go-build`) | -| 문서 업데이트 | 수동 프롬프트 대신 `/update-docs` 사용 | +| 반복적인 빌드 수정 | 언어별 리졸버 사용 (일반 대신 `/egc-go-build`) | +| 문서 업데이트 | 수동 프롬프트 대신 `/egc-update-docs` 사용 | | 아키텍처 결정 | 명확한 범위 경계와 함께 `@architect` 사용 | ## 토큰 효율을 위한 지속적 학습 -`/learn` 커맨드는 세션에서 패턴을 추출하여 재사용 가능한 스킬로 저장합니다. 향후 세션에서 컨텍스트를 다시 설명할 필요가 줄어듭니다: +`/egc-learn` 커맨드는 세션에서 패턴을 추출하여 재사용 가능한 스킬로 저장합니다. 향후 세션에서 컨텍스트를 다시 설명할 필요가 줄어듭니다: ```bash -/learn # 현재 세션에서 패턴 추출 -/evolve # 인스팅트를 효율적인 스킬로 클러스터링 +/egc-learn # 현재 세션에서 패턴 추출 +/egc-evolve # 인스팅트를 효율적인 스킬로 클러스터링 ``` diff --git a/docs/ko-KR/scripts/README.md b/docs/ko-KR/scripts/README.md index dc8f79a..e2efeed 100644 --- a/docs/ko-KR/scripts/README.md +++ b/docs/ko-KR/scripts/README.md @@ -15,7 +15,7 @@ | 스크립트 | 설명 | |----------|------| -| `harness-audit.js` | 핵심 Gemini CLI 규칙에 대한 저장소 상태를 검사(Audit)합니다. 토큰/컨텍스트 최적화 가이드 제공 여부, 훅 구성 파일, Eval 커버리지, 보안 가드레일 등을 평가합니다.

**사용법:** `node scripts/harness-audit.js --scope repo` | +| `harness-audit.js` | 핵심 Gemini CLI 규칙에 대한 저장소 상태를 검사(Audit)합니다. 토큰/컨텍스트 최적화 가이드 제공 여부, 훅 구성 파일, Eval 커버리지, 보안 가드레일 등을 평가합니다.

**사용법:** `node scripts/egc-harness-audit.js --scope repo` | | `release.sh` | `package.json`, `gemini-extension.json`, `.gemini-plugin/plugin.json` 세 파일의 버전을 동기화하고, 커밋 및 버전 태그(`v*`)를 생성합니다.

**사용법:** `./scripts/release.sh ` | ### 문서 자동 생성 diff --git a/docs/zh-CN/README.md b/docs/zh-CN/README.md index aa94319..3fedcb4 100644 --- a/docs/zh-CN/README.md +++ b/docs/zh-CN/README.md @@ -69,13 +69,13 @@ gemini extensions uninstall https://github.com/Jamkris/everything-gemini-code ```bash # 规划功能实现 -/plan "添加 JWT 用户认证" +/egc-plan "添加 JWT 用户认证" # 开始 TDD 工作流 -/tdd "创建用户服务" +/egc-tdd "创建用户服务" # 运行代码审查 -/code-review +/egc-code-review ``` ### 智能体 (Agents) @@ -109,7 +109,7 @@ everything-gemini-code/ ├── gemini-extension.json # 扩展清单 ├── agents/ # 专用子智能体 (@planner, @architect 等) ├── skills/ # 工作流定义 (TDD, Patterns 等) -├── commands/ # 斜杠命令 (/plan, /tdd 等) +├── commands/ # 斜杠命令 (/egc-plan, /egc-tdd 等) ├── templates/ # GEMINI.md 规则模板 (Global, TS, Python, Go) ├── hooks/ # 自动化触发器 (hooks.json) └── mcp-configs/ # MCP 服务器配置 diff --git a/docs/zh-CN/commands/README.md b/docs/zh-CN/commands/README.md index c3f03b1..8c8007e 100644 --- a/docs/zh-CN/commands/README.md +++ b/docs/zh-CN/commands/README.md @@ -6,35 +6,35 @@ | 命令 | 描述 | | ------------------ | ------------------------------------------------------------------------------------------------------------ | -| `/build-fix` | 分析构建错误并使用 `build-error-resolver` 代理自动修复。 | -| `/checkpoint` | 暂存所有更改并使用 AI 生成的消息提交。 | -| `/code-review` | 使用 `code-reviewer` 代理对当前更改进行全面代码审查。 | -| `/e2e` | 使用 Playwright 生成并运行端到端测试。 | +| `/egc-build-fix` | 分析构建错误并使用 `build-error-resolver` 代理自动修复。 | +| `/egc-checkpoint` | 暂存所有更改并使用 AI 生成的消息提交。 | +| `/egc-code-review` | 使用 `code-reviewer` 代理对当前更改进行全面代码审查。 | +| `/egc-e2e` | 使用 Playwright 生成并运行端到端测试。 | | `/egc-plan` | 重述需求、评估风险并制定分步实施计划。(别名: `/everything-gemini-code:plan`) | | `/egc-docs` | 通过 Context7 查找库或主题的最新文档。(别名: `/everything-gemini-code:docs`) | -| `/eval` | 管理 eval 驱动的开发工作流。 | -| `/evolve` | 将相关直觉聚类为技能、命令或代理。 | -| `/go-build` | 逐步修复 Go 构建错误、go vet 警告和 linter 问题。 | -| `/go-review` | 全面的 Go 代码审查 — 惯用模式、并发安全、错误处理、安全性。 | -| `/go-test` | Go TDD 工作流。先编写表驱动测试，再实现代码。 | -| `/instinct-export` | 将学习的直觉导出到文件。 | -| `/instinct-import` | 从文件或其他来源导入直觉。 | -| `/instinct-status` | 显示所有已学习直觉及其置信度。 | -| `/learn` | 从当前会话中提取可重用模式。 | -| `/multi-backend` | 后端专注的多代理工作流。 | -| `/multi-execute` | 使用多个专业代理执行多阶段计划。 | -| `/multi-frontend` | 前端专注的多代理工作流。 | -| `/multi-plan` | 使用多个代理创建全面的实施计划。 | -| `/multi-workflow` | 多模型协作开发工作流。 | -| `/orchestrate` | 复杂多步骤任务的高级编排。 | -| `/pm2` | 自动分析项目并生成 PM2 服务命令。 | -| `/python-review` | PEP 8、类型提示和安全性的全面 Python 代码审查。 | -| `/refactor-clean` | 识别并删除死代码、未使用的导入和遗留工件。 | -| `/sessions` | 管理和列出活动的 Gemini 会话。 | -| `/setup-pm` | 配置首选包管理器（npm/pnpm/yarn/bun）。 | -| `/skill-create` | 分析本地 git 历史以提取编码模式并生成 `SKILL.md` 文件。 | -| `/tdd` | 实施测试驱动开发工作流。 | -| `/test-coverage` | 分析当前测试覆盖率并建议改进方法。 | -| `/update-codemaps` | 刷新代码库映射以确保代理拥有最新上下文。 | -| `/update-docs` | 根据最近的代码更改更新文档。 | -| `/verify` | 运行完整验证套件（lint、构建、测试）。 | +| `/egc-eval` | 管理 eval 驱动的开发工作流。 | +| `/egc-evolve` | 将相关直觉聚类为技能、命令或代理。 | +| `/egc-go-build` | 逐步修复 Go 构建错误、go vet 警告和 linter 问题。 | +| `/egc-go-review` | 全面的 Go 代码审查 — 惯用模式、并发安全、错误处理、安全性。 | +| `/egc-go-test` | Go TDD 工作流。先编写表驱动测试，再实现代码。 | +| `/egc-instinct-export` | 将学习的直觉导出到文件。 | +| `/egc-instinct-import` | 从文件或其他来源导入直觉。 | +| `/egc-instinct-status` | 显示所有已学习直觉及其置信度。 | +| `/egc-learn` | 从当前会话中提取可重用模式。 | +| `/egc-multi-backend` | 后端专注的多代理工作流。 | +| `/egc-multi-execute` | 使用多个专业代理执行多阶段计划。 | +| `/egc-multi-frontend` | 前端专注的多代理工作流。 | +| `/egc-multi-plan` | 使用多个代理创建全面的实施计划。 | +| `/egc-multi-workflow` | 多模型协作开发工作流。 | +| `/egc-orchestrate` | 复杂多步骤任务的高级编排。 | +| `/egc-pm2` | 自动分析项目并生成 PM2 服务命令。 | +| `/egc-python-review` | PEP 8、类型提示和安全性的全面 Python 代码审查。 | +| `/egc-refactor-clean` | 识别并删除死代码、未使用的导入和遗留工件。 | +| `/egc-sessions` | 管理和列出活动的 Gemini 会话。 | +| `/egc-setup-pm` | 配置首选包管理器（npm/pnpm/yarn/bun）。 | +| `/egc-skill-create` | 分析本地 git 历史以提取编码模式并生成 `SKILL.md` 文件。 | +| `/egc-tdd` | 实施测试驱动开发工作流。 | +| `/egc-test-coverage` | 分析当前测试覆盖率并建议改进方法。 | +| `/egc-update-codemaps` | 刷新代码库映射以确保代理拥有最新上下文。 | +| `/egc-update-docs` | 根据最近的代码更改更新文档。 | +| `/egc-verify` | 运行完整验证套件（lint、构建、测试）。 | diff --git a/examples/GEMINI.md b/examples/GEMINI.md index c0cb5aa..5735fd5 100644 --- a/examples/GEMINI.md +++ b/examples/GEMINI.md @@ -87,10 +87,10 @@ DEBUG=false ## Available Commands -- `/tdd` - Test-driven development workflow -- `/plan` - Create implementation plan -- `/code-review` - Review code quality -- `/build-fix` - Fix build errors +- `/egc-tdd` - Test-driven development workflow +- `/egc-plan` - Create implementation plan +- `/egc-code-review` - Review code quality +- `/egc-build-fix` - Fix build errors ## Git Workflow diff --git a/examples/statusline.json b/examples/statusline.json index 5e31d0c..3655d3e 100644 --- a/examples/statusline.json +++ b/examples/statusline.json @@ -13,7 +13,7 @@ "C": "Cyan - username, todos", "T": "Gray - model name" }, - "output_example": "affoon:~/projects/myapp main* ctx:73% sonnet-4.5 14:30 todos:3", + "output_example": "affoon:~/egc-projects/myapp main* ctx:73% sonnet-4.5 14:30 todos:3", "usage": "Copy the statusLine object to your ~/.gemini/settings.json" } } diff --git a/mcp-configs/README.md b/mcp-configs/README.md index f5d2d70..9301fad 100644 --- a/mcp-configs/README.md +++ b/mcp-configs/README.md @@ -2,5 +2,5 @@ See the full documentation: -- [English](../docs/en/mcp-configs/README.md) -- [한국어](../docs/ko-KR/mcp-configs/README.md) +- [English](../egc-docs/en/mcp-configs/README.md) +- [한국어](../egc-docs/ko-KR/mcp-configs/README.md) diff --git a/mcp-configs/mcp-servers.json b/mcp-configs/mcp-servers.json index 28193c6..73311f3 100644 --- a/mcp-configs/mcp-servers.json +++ b/mcp-configs/mcp-servers.json @@ -81,7 +81,7 @@ "args": [ "-y", "@modelcontextprotocol/server-filesystem", - "/path/to/your/projects" + "/path/to/your/egc-projects" ], "description": "Filesystem operations (set your path)" } diff --git a/scripts/generate-docs.js b/scripts/generate-docs.js index 0b7240d..0317ac3 100644 --- a/scripts/generate-docs.js +++ b/scripts/generate-docs.js @@ -2,7 +2,7 @@ const fs = require('fs'); const path = require('path'); const COMMANDS_DIR = path.join(__dirname, '../../gemini/commands'); -const DOCS_DIR = path.join(__dirname, '../docs/commands'); +const DOCS_DIR = path.join(__dirname, '../egc-docs/commands'); if (!fs.existsSync(DOCS_DIR)) { fs.mkdirSync(DOCS_DIR, { recursive: true }); diff --git a/scripts/harness-audit.js b/scripts/harness-audit.js index e2450d4..087cbfb 100755 --- a/scripts/harness-audit.js +++ b/scripts/harness-audit.js @@ -188,10 +188,10 @@ function getChecks() { category: 'Context Efficiency', points: 2, scopes: ['repo', 'commands'], - path: 'commands/model-route.toml', + path: 'commands/egc-model-route.toml', description: 'Model routing command exists', - pass: fileExists('commands/model-route.toml'), - fix: 'Add model-route command guidance in commands/model-route.toml.', + pass: fileExists('commands/egc-model-route.toml'), + fix: 'Add model-route command guidance in commands/egc-model-route.toml.', }, { id: 'context-token-doc', @@ -278,10 +278,10 @@ function getChecks() { category: 'Eval Coverage', points: 4, scopes: ['repo', 'commands'], - path: 'commands/eval.toml', + path: 'commands/egc-eval.toml', description: 'Eval and verification commands exist', - pass: fileExists('commands/eval.toml') && fileExists('commands/verify.toml') && fileExists('commands/checkpoint.toml'), - fix: 'Add eval/checkpoint/verify commands to standardize verification loops.', + pass: fileExists('commands/egc-eval.toml') && fileExists('commands/egc-verify.toml') && fileExists('commands/egc-checkpoint.toml'), + fix: 'Add eval/egc-checkpoint/egc-verify commands to standardize verification loops.', }, { id: 'eval-tests-presence', @@ -442,7 +442,7 @@ function printText(report) { function showHelp(exitCode = 0) { console.log(` -Usage: node scripts/harness-audit.js [scope] [--scope ] [--format ] +Usage: node scripts/egc-harness-audit.js [scope] [--scope ] [--format ] Deterministic Gemini harness audit based on explicit file/rule checks. `); diff --git a/scripts/hooks/session-start.js b/scripts/hooks/session-start.js index 6573250..d8cff5d 100644 --- a/scripts/hooks/session-start.js +++ b/scripts/hooks/session-start.js @@ -51,7 +51,7 @@ runHook('SessionStart', async () => { } } } else { - // Manual install: create shims so short aliases like /tdd work + // Manual install: create shims so short aliases like /egc-tdd work const globalCmdDir = path.join(geminiDir, 'commands'); const extDir = path.resolve(__dirname, '..', '..'); const extCmdDir = path.join(extDir, 'commands'); diff --git a/scripts/lib/session-manager.js b/scripts/lib/session-manager.js index 36f765c..9441242 100644 --- a/scripts/lib/session-manager.js +++ b/scripts/lib/session-manager.js @@ -2,7 +2,7 @@ * Session Manager Library for Gemini CLI * Provides core session CRUD operations for listing, loading, and managing sessions * - * Sessions are stored as markdown files in ~/.gemini/sessions/ with format: + * Sessions are stored as markdown files in ~/.gemini/egc-sessions/ with format: * - YYYY-MM-DD-session.tmp (old format) * - YYYY-MM-DD--session.tmp (new format) */ diff --git a/scripts/setup-package-manager.js b/scripts/setup-package-manager.js index 582c99b..ef19060 100644 --- a/scripts/setup-package-manager.js +++ b/scripts/setup-package-manager.js @@ -3,7 +3,7 @@ * Package Manager Setup Script * * Interactive script to configure preferred package manager. - * Can be run directly or via the /setup-pm command. + * Can be run directly or via the /egc-setup-pm command. * * Usage: * node scripts/setup-package-manager.js [pm-name] diff --git a/scripts/skill-create-output.js b/scripts/skill-create-output.js index 4b229a6..aae77f6 100644 --- a/scripts/skill-create-output.js +++ b/scripts/skill-create-output.js @@ -2,7 +2,7 @@ /** * Skill Creator - Pretty Output Formatter * - * Creates beautiful terminal output for the /skill-create command + * Creates beautiful terminal output for the /egc-skill-create command * similar to @mvanhorn's /last30days skill */ @@ -158,9 +158,9 @@ ${chalk.bold('Files Tracked:')} ${chalk.green(data.files)} nextSteps() { console.log(box('📋 Next Steps', ` ${chalk.yellow('1.')} Review the generated SKILL.md -${chalk.yellow('2.')} Import instincts: ${chalk.cyan('/instinct-import ')} -${chalk.yellow('3.')} View learned patterns: ${chalk.cyan('/instinct-status')} -${chalk.yellow('4.')} Evolve into skills: ${chalk.cyan('/evolve')} +${chalk.yellow('2.')} Import instincts: ${chalk.cyan('/egc-instinct-import ')} +${chalk.yellow('3.')} View learned patterns: ${chalk.cyan('/egc-instinct-status')} +${chalk.yellow('4.')} Evolve into skills: ${chalk.cyan('/egc-evolve')} `)); console.log('\n'); } diff --git a/skills/autonomous-agent-harness/SKILL.md b/skills/autonomous-agent-harness/SKILL.md index 5e62419..de6df8b 100644 --- a/skills/autonomous-agent-harness/SKILL.md +++ b/skills/autonomous-agent-harness/SKILL.md @@ -51,7 +51,7 @@ Turn Gemini CLI into a persistent, self-directing agent system using only native Use Gemini CLI's built-in memory system enhanced with MCP memory server for structured data. -**Built-in memory** (`~/.gemini/projects/*/memory/`): +**Built-in memory** (`~/.gemini/egc-projects/*/memory/`): - User preferences, feedback, project context - Stored as markdown files with frontmatter - Automatically loaded at session start @@ -68,7 +68,7 @@ Use Gemini CLI's built-in memory system enhanced with MCP memory server for stru Use TodoWrite for in-session task tracking # Medium-term: project memory files -Write to ~/.gemini/projects/*/memory/ for cross-session recall +Write to ~/.gemini/egc-projects/*/memory/ for cross-session recall # Long-term: MCP knowledge graph Use mcp__memory__create_entities for permanent structured data @@ -147,7 +147,7 @@ Manage a persistent queue of tasks that survive session boundaries. ``` # Task persistence via memory -Write task queue to ~/.gemini/projects/*/memory/task-queue.md +Write task queue to ~/.gemini/egc-projects/*/memory/task-queue.md # Task format --- diff --git a/skills/autonomous-loops/SKILL.md b/skills/autonomous-loops/SKILL.md index 4c77f78..c0002a8 100644 --- a/skills/autonomous-loops/SKILL.md +++ b/skills/autonomous-loops/SKILL.md @@ -112,15 +112,15 @@ gemini -p --allowedTools "Read,Write,Edit,Bash" "Implement the fixes from securi ```bash # Start the default session -node scripts/claw.js +node scripts/egc-claw.js # Named session with skill context -CLAW_SESSION=my-project CLAW_SKILLS=tdd-workflow,security-review node scripts/claw.js +CLAW_SESSION=my-project CLAW_SKILLS=tdd-workflow,security-review node scripts/egc-claw.js ``` ### How It Works -1. Loads conversation history from `~/.gemini/claw/{session}.md` +1. Loads conversation history from `~/.gemini/egc-claw/{session}.md` 2. Each user message is sent to `gemini -p` with full history as context 3. Responses are appended to the session file (Markdown-as-database) 4. Sessions persist across restarts @@ -135,7 +135,7 @@ CLAW_SESSION=my-project CLAW_SKILLS=tdd-workflow,security-review node scripts/cl | Context accumulation | Grows per turn | Fresh each step | | CI/CD integration | Poor | Excellent | -See the `/claw` command documentation for full details. +See the `/egc-claw` command documentation for full details. --- @@ -568,7 +568,7 @@ These patterns compose well: 2. **Continuous Gemini + De-Sloppify** — Add `--review-prompt` with a de-sloppify directive to each iteration. -3. **Any loop + Verification** — Use ECC's `/verify` command or `verification-loop` skill as a gate before commits. +3. **Any loop + Verification** — Use ECC's `/egc-verify` command or `verification-loop` skill as a gate before commits. 4. **Ralphinho's tiered approach in simpler loops** — Even in a sequential pipeline, you can route simple tasks to Haiku and complex tasks to Opus: ```bash @@ -606,5 +606,5 @@ These patterns compose well: | Ralphinho | enitrat | credit: @enitrat | | Infinite Agentic Loop | disler | credit: @disler | | Continuous Gemini | AnandChowdhary | credit: @AnandChowdhary | -| NanoClaw | ECC | `/claw` command in this repo | +| NanoClaw | ECC | `/egc-claw` command in this repo | | Verification Loop | ECC | `skills/verification-loop/` in this repo | diff --git a/skills/context-budget/SKILL.md b/skills/context-budget/SKILL.md index b933097..4d7c066 100644 --- a/skills/context-budget/SKILL.md +++ b/skills/context-budget/SKILL.md @@ -14,7 +14,7 @@ Analyze token overhead across every loaded component in a Gemini CLI session and - You've recently added many skills, agents, or MCP servers - You want to know how much context headroom you actually have - Planning to add more components and need to know if there's room -- Running `/context-budget` command (this skill backs it) +- Running `/egc-context-budget` command (this skill backs it) ## How It Works @@ -106,7 +106,7 @@ In verbose mode, additionally output per-file token counts, line-by-line breakdo **Basic audit** ``` -User: /context-budget +User: /egc-context-budget Skill: Scans setup → 16 agents (12,400 tokens), 28 skills (6,200), 87 MCP tools (43,500), 2 GEMINI.md (1,200) Flags: 3 heavy agents, 14 MCP servers (3 CLI-replaceable) Top saving: remove 3 MCP servers → -27,500 tokens (47% overhead reduction) @@ -114,7 +114,7 @@ Skill: Scans setup → 16 agents (12,400 tokens), 28 skills (6,200), 87 MCP tool **Verbose mode** ``` -User: /context-budget --verbose +User: /egc-context-budget --verbose Skill: Full report + per-file breakdown showing planner.md (213 lines, 1,840 tokens), MCP tool list with per-tool sizes, duplicated rule lines side by side ``` diff --git a/skills/continuous-agent-loop/SKILL.md b/skills/continuous-agent-loop/SKILL.md index 3e7bd93..38ee7fc 100644 --- a/skills/continuous-agent-loop/SKILL.md +++ b/skills/continuous-agent-loop/SKILL.md @@ -26,7 +26,7 @@ Start Recommended production stack: 1. RFC decomposition (`ralphinho-rfc-pipeline`) -2. quality gates (`plankton-code-quality` + `/quality-gate`) +2. quality gates (`plankton-code-quality` + `/egc-quality-gate`) 3. eval loop (`eval-harness`) 4. session persistence (`nanoclaw-repl`) @@ -40,6 +40,6 @@ Recommended production stack: ## Recovery - freeze loop -- run `/harness-audit` +- run `/egc-harness-audit` - reduce scope to failing unit - replay with explicit acceptance criteria diff --git a/skills/continuous-learning-v2/SKILL.md b/skills/continuous-learning-v2/SKILL.md index 9d89f14..7fc5f5f 100644 --- a/skills/continuous-learning-v2/SKILL.md +++ b/skills/continuous-learning-v2/SKILL.md @@ -78,7 +78,7 @@ Session Activity │ • use-zod-validation.md (0.6) │ └─────────────────────────────────────────┘ │ - │ /evolve clusters + │ /egc-evolve clusters ▼ ┌─────────────────────────────────────────┐ │ evolved/ │ @@ -152,20 +152,20 @@ touch ~/.gemini/homunculus/observations.jsonl ### 3. Use the Instinct Commands ```bash -/instinct-status # Show learned instincts with confidence scores -/evolve # Cluster related instincts into skills/commands -/instinct-export # Export instincts for sharing -/instinct-import # Import instincts from others +/egc-instinct-status # Show learned instincts with confidence scores +/egc-evolve # Cluster related instincts into skills/commands +/egc-instinct-export # Export instincts for sharing +/egc-instinct-import # Import instincts from others ``` ## Commands | Command | Description | |---------|-------------| -| `/instinct-status` | Show all learned instincts with confidence | -| `/evolve` | Cluster related instincts into skills/commands | -| `/instinct-export` | Export instincts for sharing | -| `/instinct-import ` | Import instincts from others | +| `/egc-instinct-status` | Show all learned instincts with confidence | +| `/egc-evolve` | Cluster related instincts into skills/commands | +| `/egc-instinct-export` | Export instincts for sharing | +| `/egc-instinct-import ` | Import instincts from others | ## Configuration diff --git a/skills/continuous-learning/SKILL.md b/skills/continuous-learning/SKILL.md index fe53e5c..dbccecd 100644 --- a/skills/continuous-learning/SKILL.md +++ b/skills/continuous-learning/SKILL.md @@ -77,7 +77,7 @@ Add to your `~/.gemini/settings.json`: ## Related - [The Longform Guide](https://x.com/Jamkris/status/2014040193557471352) - Section on continuous learning -- `/learn` command - Manual pattern extraction mid-session +- `/egc-learn` command - Manual pattern extraction mid-session --- diff --git a/skills/council/SKILL.md b/skills/council/SKILL.md index ce4e6b2..ed14c04 100644 --- a/skills/council/SKILL.md +++ b/skills/council/SKILL.md @@ -157,7 +157,7 @@ Do **not** write ad-hoc notes to `~/.gemini/notes` or other shadow paths from th If the council materially changes the recommendation: - use `knowledge-ops` to store the lesson in the right durable location -- or use `/save-session` if the outcome belongs in session memory +- or use `/egc-save-session` if the outcome belongs in session memory - or update the relevant GitHub / Linear issue directly if the decision changes active execution truth Only persist a decision when it changes something real. diff --git a/skills/dart-flutter-patterns/SKILL.md b/skills/dart-flutter-patterns/SKILL.md index d6c97b7..e1c7582 100644 --- a/skills/dart-flutter-patterns/SKILL.md +++ b/skills/dart-flutter-patterns/SKILL.md @@ -554,7 +554,7 @@ testWidgets('CartBadge shows item count', (tester) async { ## References - [Effective Dart: Design](https://dart.dev/effective-dart/design) -- [Flutter Performance Best Practices](https://docs.flutter.dev/perf/best-practices) +- [Flutter Performance Best Practices](https://egc-docs.flutter.dev/perf/best-practices) - [Riverpod Documentation](https://riverpod.dev/) - [BLoC Library](https://bloclibrary.dev/) - [GoRouter](https://pub.dev/packages/go_router) diff --git a/skills/design-system/SKILL.md b/skills/design-system/SKILL.md index 43cf48f..b24590a 100644 --- a/skills/design-system/SKILL.md +++ b/skills/design-system/SKILL.md @@ -72,7 +72,7 @@ Identifies generic AI-generated design patterns: **Audit existing UI:** ``` -/design-system audit --url http://localhost:3000 --pages / /pricing /docs +/design-system audit --url http://localhost:3000 --pages / /pricing /egc-docs ``` **Check for AI slop:** diff --git a/skills/dmux-workflows/SKILL.md b/skills/dmux-workflows/SKILL.md index 9a28313..086cd84 100644 --- a/skills/dmux-workflows/SKILL.md +++ b/skills/dmux-workflows/SKILL.md @@ -174,7 +174,7 @@ Use `seedPaths` when workers need access to dirty or untracked local files that "seedPaths": [ "scripts/orchestrate-worktrees.js", "scripts/lib/tmux-worktree-orchestrator.js", - ".gemini/plan/workflow-e2e-test.json" + ".gemini/egc-plan/workflow-e2e-test.json" ], "launcherCommand": "bash {repo_root}/scripts/orchestrate-codex-worker.sh {task_file} {handoff_file} {status_file}", "workers": [ diff --git a/skills/e2e-testing/SKILL.md b/skills/e2e-testing/SKILL.md index 0563199..6db827f 100644 --- a/skills/e2e-testing/SKILL.md +++ b/skills/e2e-testing/SKILL.md @@ -103,7 +103,7 @@ test.describe('Item Search', () => { 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, @@ -225,7 +225,7 @@ use: { ## CI/CD Integration ```yaml -# .github/workflows/e2e.yml +# .github/workflows/egc-e2e.yml name: E2E Tests on: [push, pull_request] @@ -265,7 +265,7 @@ jobs: ## Failed Tests ### test-name -**File:** `tests/e2e/feature.spec.ts:45` +**File:** `tests/egc-e2e/feature.spec.ts:45` **Error:** Expected element to be visible **Screenshot:** artifacts/failed.png **Recommended Fix:** [description] diff --git a/skills/eval-harness/SKILL.md b/skills/eval-harness/SKILL.md index 9073b59..45623cb 100644 --- a/skills/eval-harness/SKILL.md +++ b/skills/eval-harness/SKILL.md @@ -157,19 +157,19 @@ Status: READY FOR REVIEW ### Pre-Implementation ``` -/eval define feature-name +/egc-eval define feature-name ``` Creates eval definition file at `.gemini/evals/feature-name.md` ### During Implementation ``` -/eval check feature-name +/egc-eval check feature-name ``` Runs current evals and reports status ### Post-Implementation ``` -/eval report feature-name +/egc-eval report feature-name ``` Generates full eval report @@ -216,7 +216,7 @@ Regression Evals: [Write code] ### Phase 3: Evaluate -Run: /eval check add-authentication +Run: /egc-eval check add-authentication ### Phase 4: Report EVAL REPORT: add-authentication diff --git a/skills/flutter-dart-code-review/SKILL.md b/skills/flutter-dart-code-review/SKILL.md index 2f9529d..eb7abc9 100644 --- a/skills/flutter-dart-code-review/SKILL.md +++ b/skills/flutter-dart-code-review/SKILL.md @@ -426,10 +426,10 @@ The table below maps universal principles to their implementation in popular sol - [Effective Dart: Style](https://dart.dev/effective-dart/style) - [Effective Dart: Usage](https://dart.dev/effective-dart/usage) - [Effective Dart: Design](https://dart.dev/effective-dart/design) -- [Flutter Performance Best Practices](https://docs.flutter.dev/perf/best-practices) -- [Flutter Testing Overview](https://docs.flutter.dev/testing/overview) -- [Flutter Accessibility](https://docs.flutter.dev/ui/accessibility-and-internationalization/accessibility) -- [Flutter Internationalization](https://docs.flutter.dev/ui/accessibility-and-internationalization/internationalization) -- [Flutter Navigation and Routing](https://docs.flutter.dev/ui/navigation) -- [Flutter Error Handling](https://docs.flutter.dev/testing/errors) -- [Flutter State Management Options](https://docs.flutter.dev/data-and-backend/state-mgmt/options) +- [Flutter Performance Best Practices](https://egc-docs.flutter.dev/perf/best-practices) +- [Flutter Testing Overview](https://egc-docs.flutter.dev/testing/overview) +- [Flutter Accessibility](https://egc-docs.flutter.dev/ui/accessibility-and-internationalization/accessibility) +- [Flutter Internationalization](https://egc-docs.flutter.dev/ui/accessibility-and-internationalization/internationalization) +- [Flutter Navigation and Routing](https://egc-docs.flutter.dev/ui/navigation) +- [Flutter Error Handling](https://egc-docs.flutter.dev/testing/errors) +- [Flutter State Management Options](https://egc-docs.flutter.dev/data-and-backend/state-mgmt/options) diff --git a/skills/hookify-rules/SKILL.md b/skills/hookify-rules/SKILL.md index 7a482c2..f6b0a46 100644 --- a/skills/hookify-rules/SKILL.md +++ b/skills/hookify-rules/SKILL.md @@ -7,7 +7,7 @@ description: This skill should be used when the user asks to create a hookify ru ## Overview -Hookify rules are markdown files with YAML frontmatter that define patterns to watch for and messages to show when those patterns match. Rules are stored in `.gemini/hookify.{rule-name}.local.md` files. +Hookify rules are markdown files with YAML frontmatter that define patterns to watch for and messages to show when those patterns match. Rules are stored in `.gemini/egc-hookify.{rule-name}.local.md` files. ## Rule File Format @@ -104,15 +104,15 @@ python3 -c "import re; print(re.search(r'your_pattern', 'test text'))" ## File Organization - **Location**: `.gemini/` directory in project root -- **Naming**: `.gemini/hookify.{descriptive-name}.local.md` +- **Naming**: `.gemini/egc-hookify.{descriptive-name}.local.md` - **Gitignore**: Add `.gemini/*.local.md` to `.gitignore` ## Commands -- `/hookify [description]` - Create new rules (auto-analyzes conversation if no args) -- `/hookify-list` - View all rules in table format -- `/hookify-configure` - Toggle rules on/off interactively -- `/hookify-help` - Full documentation +- `/egc-hookify [description]` - Create new rules (auto-analyzes conversation if no args) +- `/egc-hookify-list` - View all rules in table format +- `/egc-hookify-configure` - Toggle rules on/off interactively +- `/egc-hookify-help` - Full documentation ## Quick Reference diff --git a/skills/knowledge-ops/SKILL.md b/skills/knowledge-ops/SKILL.md index acbf115..8ab3b15 100644 --- a/skills/knowledge-ops/SKILL.md +++ b/skills/knowledge-ops/SKILL.md @@ -26,12 +26,12 @@ Prefer the live workspace model: ## Knowledge Architecture ### Layer 1: Active execution truth -- **Sources:** GitHub issues, PRs, discussions, release notes, Linear issues/projects/docs +- **Sources:** GitHub issues, PRs, discussions, release notes, Linear issues/egc-projects/egc-docs - **Use for:** the current operational state of the work - **Rule:** if something affects an active engineering plan, roadmap, rollout, or release, prefer putting it here first ### Layer 2: Gemini CLI Memory (Quick Access) -- **Path:** `~/.gemini/projects/*/memory/` +- **Path:** `~/.gemini/egc-projects/*/memory/` - **Format:** Markdown files with frontmatter - **Types:** user preferences, feedback, project context, reference - **Use for:** quick-access context that persists across conversations @@ -121,7 +121,7 @@ Pull knowledge from multiple sources into one place: Use TodoWrite for in-session task tracking # Medium-term: project memory files -Write to ~/.gemini/projects/*/memory/ for cross-session recall +Write to ~/.gemini/egc-projects/*/memory/ for cross-session recall # Long-term: GitHub / Linear / KB Put active execution truth in GitHub + Linear diff --git a/skills/kotlin-patterns/SKILL.md b/skills/kotlin-patterns/SKILL.md index 5e75d27..3e589b9 100644 --- a/skills/kotlin-patterns/SKILL.md +++ b/skills/kotlin-patterns/SKILL.md @@ -531,7 +531,7 @@ val first20 = fibonacci.take(20).toList() ### build.gradle.kts Configuration ```kotlin -// Check for latest versions: https://kotlinlang.org/docs/releases.html +// Check for latest versions: https://kotlinlang.org/egc-docs/releases.html plugins { kotlin("jvm") version "2.3.10" kotlin("plugin.serialization") version "2.3.10" diff --git a/skills/laravel-patterns/SKILL.md b/skills/laravel-patterns/SKILL.md index ec59113..0475e40 100644 --- a/skills/laravel-patterns/SKILL.md +++ b/skills/laravel-patterns/SKILL.md @@ -114,7 +114,7 @@ Use scoped bindings to prevent cross-tenant access. ```php Route::scopeBindings()->group(function () { - Route::get('/accounts/{account}/projects/{project}', [ProjectController::class, 'show']); + Route::get('/accounts/{account}/egc-projects/{project}', [ProjectController::class, 'show']); }); ``` diff --git a/skills/laravel-security/SKILL.md b/skills/laravel-security/SKILL.md index ee4ec32..c920d49 100644 --- a/skills/laravel-security/SKILL.md +++ b/skills/laravel-security/SKILL.md @@ -84,7 +84,7 @@ Use policy middleware for route-level enforcement: ```php use Illuminate\Support\Facades\Route; -Route::put('/projects/{project}', [ProjectController::class, 'update']) +Route::put('/egc-projects/{project}', [ProjectController::class, 'update']) ->middleware(['auth:sanctum', 'can:update,project']); ``` diff --git a/skills/laravel-tdd/SKILL.md b/skills/laravel-tdd/SKILL.md index e80fa4d..033cb8a 100644 --- a/skills/laravel-tdd/SKILL.md +++ b/skills/laravel-tdd/SKILL.md @@ -65,7 +65,7 @@ final class ProjectControllerTest extends TestCase { $user = User::factory()->create(); - $response = $this->actingAs($user)->postJson('/api/projects', [ + $response = $this->actingAs($user)->postJson('/api/egc-projects', [ 'name' => 'New Project', ]); @@ -92,7 +92,7 @@ final class ProjectIndexTest extends TestCase $user = User::factory()->create(); Project::factory()->count(3)->for($user)->create(); - $response = $this->actingAs($user)->getJson('/api/projects'); + $response = $this->actingAs($user)->getJson('/api/egc-projects'); $response->assertOk(); $response->assertJsonStructure(['success', 'data', 'error', 'meta']); @@ -114,7 +114,7 @@ uses(RefreshDatabase::class); test('owner can create project', function () { $user = User::factory()->create(); - $response = actingAs($user)->postJson('/api/projects', [ + $response = actingAs($user)->postJson('/api/egc-projects', [ 'name' => 'New Project', ]); @@ -138,7 +138,7 @@ test('projects index returns paginated results', function () { $user = User::factory()->create(); Project::factory()->count(3)->for($user)->create(); - $response = actingAs($user)->getJson('/api/projects'); + $response = actingAs($user)->getJson('/api/egc-projects'); $response->assertOk(); $response->assertJsonStructure(['success', 'data', 'error', 'meta']); @@ -216,7 +216,7 @@ use Laravel\Sanctum\Sanctum; Sanctum::actingAs($user); -$response = $this->getJson('/api/projects'); +$response = $this->getJson('/api/egc-projects'); $response->assertOk(); ``` diff --git a/skills/nanoclaw-repl/SKILL.md b/skills/nanoclaw-repl/SKILL.md index 94f0c27..72bf192 100644 --- a/skills/nanoclaw-repl/SKILL.md +++ b/skills/nanoclaw-repl/SKILL.md @@ -6,7 +6,7 @@ origin: ECC # NanoClaw REPL -Use this skill when running or extending `scripts/claw.js`. +Use this skill when running or extending `scripts/egc-claw.js`. ## Capabilities diff --git a/skills/prompt-optimizer/SKILL.md b/skills/prompt-optimizer/SKILL.md index 5765c19..69fbc00 100644 --- a/skills/prompt-optimizer/SKILL.md +++ b/skills/prompt-optimizer/SKILL.md @@ -32,7 +32,7 @@ and output a complete optimized prompt the user can paste and run. - User pastes a draft prompt and asks for feedback or enhancement - User says "I don't know how to prompt for this" - User says "how should I use ECC for..." -- User explicitly invokes `/prompt-optimize` +- User explicitly invokes `/egc-prompt-optimize` ### Do Not Use When @@ -105,8 +105,8 @@ from the prompt description alone and mark the estimate as uncertain. |-------|-----------|---------------| | TRIVIAL | Single file, < 50 lines | Direct execution | | LOW | Single component or module | Single command or skill | -| MEDIUM | Multiple components, same domain | Command chain + /verify | -| HIGH | Cross-domain, 5+ files | /plan first, then phased execution | +| MEDIUM | Multiple components, same domain | Command chain + /egc-verify | +| HIGH | Cross-domain, 5+ files | /egc-plan first, then phased execution | | EPIC | Multi-session, multi-PR, architectural shift | Use blueprint skill for multi-session plan | ### Phase 3: ECC Component Matching @@ -117,15 +117,15 @@ Map intent + scope + tech stack (from Phase 0) to specific ECC components. | Intent | Commands | Skills | Agents | |--------|----------|--------|--------| -| New Feature | /plan, /tdd, /code-review, /verify | tdd-workflow, verification-loop | planner, tdd-guide, code-reviewer | -| Bug Fix | /tdd, /build-fix, /verify | tdd-workflow | tdd-guide, build-error-resolver | -| Refactor | /refactor-clean, /code-review, /verify | verification-loop | refactor-cleaner, code-reviewer | -| Research | /plan | search-first, iterative-retrieval | — | -| Testing | /tdd, /e2e, /test-coverage | tdd-workflow, e2e-testing | tdd-guide, e2e-runner | -| Review | /code-review | security-review | code-reviewer, security-reviewer | -| Documentation | /update-docs, /update-codemaps | — | doc-updater | -| Infrastructure | /plan, /verify | docker-patterns, deployment-patterns, database-migrations | architect | -| Design (MEDIUM-HIGH) | /plan | — | planner, architect | +| New Feature | /egc-plan, /egc-tdd, /egc-code-review, /egc-verify | tdd-workflow, verification-loop | planner, tdd-guide, code-reviewer | +| Bug Fix | /egc-tdd, /egc-build-fix, /egc-verify | tdd-workflow | tdd-guide, build-error-resolver | +| Refactor | /egc-refactor-clean, /egc-code-review, /egc-verify | verification-loop | refactor-cleaner, code-reviewer | +| Research | /egc-plan | search-first, iterative-retrieval | — | +| Testing | /egc-tdd, /egc-e2e, /egc-test-coverage | tdd-workflow, e2e-testing | tdd-guide, e2e-runner | +| Review | /egc-code-review | security-review | code-reviewer, security-reviewer | +| Documentation | /egc-update-docs, /egc-update-codemaps | — | doc-updater | +| Infrastructure | /egc-plan, /egc-verify | docker-patterns, deployment-patterns, database-migrations | architect | +| Design (MEDIUM-HIGH) | /egc-plan | — | planner, architect | | Design (EPIC) | — | blueprint (invoke as skill) | planner, architect | #### By Tech Stack @@ -172,7 +172,7 @@ Determine where this prompt sits in the development lifecycle: Research → Plan → Implement (TDD) → Review → Verify → Commit ``` -For MEDIUM+ tasks, always start with /plan. For EPIC tasks, use blueprint skill. +For MEDIUM+ tasks, always start with /egc-plan. For EPIC tasks, use blueprint skill. **Model recommendation** (include in output): @@ -186,10 +186,10 @@ For MEDIUM+ tasks, always start with /plan. For EPIC tasks, use blueprint skill. **Multi-prompt splitting** (for HIGH/EPIC scope): For tasks that exceed a single session, split into sequential prompts: -- Prompt 1: Research + Plan (use search-first skill, then /plan) -- Prompt 2-N: Implement one phase per prompt (each ends with /verify) -- Final Prompt: Integration test + /code-review across all phases -- Use /save-session and /resume-session to preserve context between sessions +- Prompt 1: Research + Plan (use search-first skill, then /egc-plan) +- Prompt 2-N: Implement one phase per prompt (each ends with /egc-verify) +- Final Prompt: Integration test + /egc-code-review across all phases +- Use /egc-save-session and /egc-resume-session to preserve context between sessions --- @@ -215,7 +215,7 @@ If Phase 0 auto-detected the answer, state it instead of asking. | Type | Component | Purpose | |------|-----------|---------| -| Command | /plan | Plan architecture before coding | +| Command | /egc-plan | Plan architecture before coding | | Skill | tdd-workflow | TDD methodology guidance | | Agent | code-reviewer | Post-implementation review | | Model | Sonnet 4.6 | Recommended for this scope | @@ -240,14 +240,14 @@ A compact version for experienced ECC users. Vary by intent type: | Intent | Quick Pattern | |--------|--------------| -| New Feature | `/plan [feature]. /tdd to implement. /code-review. /verify.` | -| Bug Fix | `/tdd — write failing test for [bug]. Fix to green. /verify.` | -| Refactor | `/refactor-clean [scope]. /code-review. /verify.` | -| Research | `Use search-first skill for [topic]. /plan based on findings.` | -| Testing | `/tdd [module]. /e2e for critical flows. /test-coverage.` | -| Review | `/code-review. Then use security-reviewer agent.` | -| Docs | `/update-docs. /update-codemaps.` | -| EPIC | `Use blueprint skill for "[objective]". Execute phases with /verify gates.` | +| New Feature | `/egc-plan [feature]. /egc-tdd to implement. /egc-code-review. /egc-verify.` | +| Bug Fix | `/egc-tdd — write failing test for [bug]. Fix to green. /egc-verify.` | +| Refactor | `/egc-refactor-clean [scope]. /egc-code-review. /egc-verify.` | +| Research | `Use search-first skill for [topic]. /egc-plan based on findings.` | +| Testing | `/egc-tdd [module]. /egc-e2e for critical flows. /egc-test-coverage.` | +| Review | `/egc-code-review. Then use security-reviewer agent.` | +| Docs | `/egc-update-docs. /egc-update-codemaps.` | +| EPIC | `Use blueprint skill for "[objective]". Execute phases with /egc-verify gates.` | ### Section 5: Enhancement Rationale @@ -291,11 +291,11 @@ A compact version for experienced ECC users. Vary by intent type: - 包含：邮箱/密码登录表单、表单验证、错误提示、加载状态、响应式布局 工作流： -1. /plan 先规划组件结构和认证流程，参考现有页面的模式 -2. /tdd 测试先行：编写登录表单的单元测试和认证流程的集成测试 +1. /egc-plan 先规划组件结构和认证流程，参考现有页面的模式 +2. /egc-tdd 测试先行：编写登录表单的单元测试和认证流程的集成测试 3. 实现登录页面和认证逻辑 -4. /code-review 审查实现 -5. /verify 验证所有测试通过且页面正常渲染 +4. /egc-code-review 审查实现 +5. /egc-verify 验证所有测试通过且页面正常渲染 安全要求： - 密码不明文传输 @@ -339,11 +339,11 @@ Requirements: - Follow existing API patterns in the codebase Workflow: -1. /plan the endpoint structure, middleware chain, and validation logic -2. /tdd — write table-driven tests for success, validation failure, auth failure, not-found +1. /egc-plan the endpoint structure, middleware chain, and validation logic +2. /egc-tdd — write table-driven tests for success, validation failure, auth failure, not-found 3. Implement following existing handler patterns -4. /go-review -5. /verify — run full test suite, confirm no regressions +4. /egc-go-review +5. /egc-verify — run full test suite, confirm no regressions Do not: - Modify existing endpoints @@ -376,8 +376,8 @@ The blueprint should produce phases like: - Phase 4: Verify with integration tests, then extract next service - Phase N: Decommission monolith -Each phase = 1 PR, with /verify gates between phases. -Use /save-session between phases. Use /resume-session to continue. +Each phase = 1 PR, with /egc-verify gates between phases. +Use /egc-save-session between phases. Use /egc-resume-session to continue. Use git worktrees for parallel service extraction when dependencies allow. Recommended: Opus 4.6 for blueprint planning, Sonnet 4.6 for phase execution. diff --git a/skills/pytorch-patterns/SKILL.md b/skills/pytorch-patterns/SKILL.md index c022933..04b0c26 100644 --- a/skills/pytorch-patterns/SKILL.md +++ b/skills/pytorch-patterns/SKILL.md @@ -336,7 +336,7 @@ model = torch.compile(model, mode="reduce-overhead") | Idiom | Description | |-------|-------------| -| `model.train()` / `model.eval()` | Always set mode before train/eval | +| `model.train()` / `model.eval()` | Always set mode before train/egc-eval | | `torch.no_grad()` | Disable gradients for inference | | `optimizer.zero_grad(set_to_none=True)` | More efficient gradient clearing | | `.to(device)` | Device-agnostic tensor/model placement | diff --git a/skills/remotion-video-creation/rules/tailwind.md b/skills/remotion-video-creation/rules/tailwind.md index a9e64c9..71e6d0b 100644 --- a/skills/remotion-video-creation/rules/tailwind.md +++ b/skills/remotion-video-creation/rules/tailwind.md @@ -8,4 +8,4 @@ You can and should use TailwindCSS in Remotion, if TailwindCSS is installed in t Don't use `transition-*` or `animate-*` classes - always animate using the `useCurrentFrame()` hook. -Tailwind must be installed and enabled first in a Remotion project - fetch using WebFetch for instructions. +Tailwind must be installed and enabled first in a Remotion project - fetch using WebFetch for instructions. diff --git a/skills/remotion-video-creation/rules/transcribe-captions.md b/skills/remotion-video-creation/rules/transcribe-captions.md index 60a6f24..ae7b7ec 100644 --- a/skills/remotion-video-creation/rules/transcribe-captions.md +++ b/skills/remotion-video-creation/rules/transcribe-captions.md @@ -10,10 +10,10 @@ metadata: Remotion provides several built-in options for transcribing audio to generate captions: - `@remotion/install-whisper-cpp` - Transcribe locally on a server using Whisper.cpp. Fast and free, but requires server infrastructure. - + - `@remotion/whisper-web` - Transcribe in the browser using WebAssembly. No server needed and free, but slower due to WASM overhead. - + - `@remotion/openai-whisper` - Use OpenAI Whisper API for cloud-based transcription. Fast and no server needed, but requires payment. - + diff --git a/skills/rules-distill/SKILL.md b/skills/rules-distill/SKILL.md index 4fbd647..5244777 100644 --- a/skills/rules-distill/SKILL.md +++ b/skills/rules-distill/SKILL.md @@ -25,13 +25,13 @@ The rules distillation process follows three phases: #### 1a. Collect skill inventory ```bash -bash ~/.gemini/skills/rules-distill/scripts/scan-skills.sh +bash ~/.gemini/skills/egc-rules-distill/scripts/scan-skills.sh ``` #### 1b. Collect rules index ```bash -bash ~/.gemini/skills/rules-distill/scripts/scan-rules.sh +bash ~/.gemini/skills/egc-rules-distill/scripts/scan-rules.sh ``` #### 1c. Present to user @@ -207,7 +207,7 @@ Store results in the skill directory (`results.json`): ### End-to-end run ``` -$ /rules-distill +$ /egc-rules-distill Rules Distillation — Phase 1: Inventory ──────────────────────────────────────── diff --git a/skills/security-review/SKILL.md b/skills/security-review/SKILL.md index b3ade08..d4db4d3 100644 --- a/skills/security-review/SKILL.md +++ b/skills/security-review/SKILL.md @@ -485,8 +485,8 @@ Before ANY production deployment: ## Resources - [OWASP Top 10](https://owasp.org/www-project-top-ten/) -- [Next.js Security](https://nextjs.org/docs/security) -- [Supabase Security](https://supabase.com/docs/guides/auth) +- [Next.js Security](https://nextjs.org/egc-docs/security) +- [Supabase Security](https://supabase.com/egc-docs/guides/auth) - [Web Security Academy](https://portswigger.net/web-security) --- diff --git a/skills/security-review/cloud-infrastructure-security.md b/skills/security-review/cloud-infrastructure-security.md index 3c6f457..34d6c4a 100644 --- a/skills/security-review/cloud-infrastructure-security.md +++ b/skills/security-review/cloud-infrastructure-security.md @@ -356,6 +356,6 @@ resource "aws_db_instance" "good" { - [CIS AWS Foundations Benchmark](https://www.cisecurity.org/benchmark/amazon_web_services) - [Cloudflare Security Documentation](https://developers.cloudflare.com/security/) - [OWASP Cloud Security](https://owasp.org/www-project-cloud-security/) -- [Terraform Security Best Practices](https://www.terraform.io/docs/cloud/guides/recommended-practices/) +- [Terraform Security Best Practices](https://www.terraform.io/egc-docs/cloud/guides/recommended-practices/) **Remember**: Cloud misconfigurations are the leading cause of data breaches. A single exposed S3 bucket or overly permissive IAM policy can compromise your entire infrastructure. Always follow the principle of least privilege and defense in depth. diff --git a/skills/token-budget-advisor/SKILL.md b/skills/token-budget-advisor/SKILL.md index 7552173..48b3f48 100644 --- a/skills/token-budget-advisor/SKILL.md +++ b/skills/token-budget-advisor/SKILL.md @@ -35,7 +35,7 @@ Intercept the response flow to offer the user a choice about response depth **be Use the repository's canonical context-budget heuristics to estimate the prompt's token count mentally. -Use the same calibration guidance as [context-budget](../context-budget/SKILL.md): +Use the same calibration guidance as [context-budget](../egc-context-budget/SKILL.md): - prose: `words × 1.3` - code-heavy or mixed/code blocks: `chars / 4` diff --git a/skills/verification-loop/SKILL.md b/skills/verification-loop/SKILL.md index adeccbe..3899df8 100644 --- a/skills/verification-loop/SKILL.md +++ b/skills/verification-loop/SKILL.md @@ -116,7 +116,7 @@ Set a mental checkpoint: - After finishing a component - Before moving to next task -Run: /verify +Run: /egc-verify ``` ## Integration with Hooks diff --git a/skills/video-editing/SKILL.md b/skills/video-editing/SKILL.md index cb00a7a..aec574b 100644 --- a/skills/video-editing/SKILL.md +++ b/skills/video-editing/SKILL.md @@ -164,7 +164,7 @@ export const VlogComposition: React.FC = () => { npx remotion render src/index.ts VlogComposition output.mp4 ``` -See the [Remotion docs](https://www.remotion.dev/docs) for detailed patterns and API reference. +See the [Remotion docs](https://www.remotion.dev/egc-docs) for detailed patterns and API reference. ## Layer 5: Generated Assets (ElevenLabs / fal.ai) diff --git a/skills/videodb/reference/capture-reference.md b/skills/videodb/reference/capture-reference.md index 3576b53..3f21adf 100644 --- a/skills/videodb/reference/capture-reference.md +++ b/skills/videodb/reference/capture-reference.md @@ -107,7 +107,7 @@ Use [scripts/ws_listener.py](../scripts/ws_listener.py) to connect and dump even } ``` -> For latest details, see [VideoDB Realtime Context docs](https://docs.videodb.io/pages/ingest/capture-sdks/realtime-context.md). +> For latest details, see [VideoDB Realtime Context docs](https://egc-docs.videodb.io/pages/ingest/capture-sdks/realtime-context.md). --- diff --git a/skills/videodb/reference/rtstream-reference.md b/skills/videodb/reference/rtstream-reference.md index b86c472..c29e4b2 100644 --- a/skills/videodb/reference/rtstream-reference.md +++ b/skills/videodb/reference/rtstream-reference.md @@ -3,7 +3,7 @@ Code-level details for RTStream operations. For workflow guide, see [rtstream.md](rtstream.md). For usage guidance and workflow selection, start with [../SKILL.md](../SKILL.md). -Based on [docs.videodb.io](https://docs.videodb.io/pages/ingest/live-streams/realtime-apis.md). +Based on [docs.videodb.io](https://egc-docs.videodb.io/pages/ingest/live-streams/realtime-apis.md). --- diff --git a/workflows/agent-sort.md b/workflows/agent-sort.md index 3949371..195fd12 100644 --- a/workflows/agent-sort.md +++ b/workflows/agent-sort.md @@ -4,7 +4,7 @@ description: Legacy slash-entry shim for the agent-sort skill. Prefer the skill # 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/workflows/checkpoint.md b/workflows/checkpoint.md index cc076db..347c14b 100644 --- a/workflows/checkpoint.md +++ b/workflows/checkpoint.md @@ -8,13 +8,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`: @@ -60,15 +60,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/workflows/e2e.md b/workflows/e2e.md index 553dbd2..7dd6ccc 100644 --- a/workflows/e2e.md +++ b/workflows/e2e.md @@ -16,7 +16,7 @@ This command invokes the **e2e-runner** agent to generate, maintain, and execute ## When to Use -Use `/e2e` when: +Use `/egc-e2e` when: - Testing critical user journeys (login, trading, payments) - Verifying multi-step flows work end-to-end - Testing UI interactions and navigation @@ -37,7 +37,7 @@ The e2e-runner agent will: ## Example Usage ``` -User: /e2e Test the market search and view flow +User: /egc-e2e Test the market search and view flow Agent (e2e-runner): # E2E Test Generation: Market Search and View Flow @@ -57,7 +57,7 @@ Agent (e2e-runner): ## Generated Test Code ```typescript -// tests/e2e/markets/search-and-view.spec.ts +// tests/egc-e2e/markets/search-and-view.spec.ts import { test, expect } from '@playwright/test' import { MarketsPage } from '../../pages/MarketsPage' import { MarketDetailsPage } from '../../pages/MarketDetailsPage' @@ -160,7 +160,7 @@ test.describe('Market Search and View Flow', () => { ```bash # Run the generated test -npx playwright test tests/e2e/markets/search-and-view.spec.ts +npx playwright test tests/egc-e2e/markets/search-and-view.spec.ts Running 3 tests using 3 workers @@ -235,7 +235,7 @@ open artifacts/search-results.png If a test fails intermittently: ``` -⚠️ FLAKY TEST DETECTED: tests/e2e/markets/trade.spec.ts +⚠️ FLAKY TEST DETECTED: tests/egc-e2e/markets/trade.spec.ts Test passed 7/10 runs (70% pass rate) @@ -266,7 +266,7 @@ Configure in `playwright.config.ts` to adjust browsers. Add to your CI pipeline: ```yaml -# .github/workflows/e2e.yml +# .github/workflows/egc-e2e.yml - name: Install Playwright run: npx playwright install --with-deps @@ -330,10 +330,10 @@ For PMX, prioritize these E2E tests: ## Integration with Other Commands -- Use `/plan` to identify critical journeys to test -- Use `/tdd` for unit tests (faster, more granular) -- Use `/e2e` for integration and user journey tests -- Use `/code-review` to verify test quality +- Use `/egc-plan` to identify critical journeys to test +- Use `/egc-tdd` for unit tests (faster, more granular) +- Use `/egc-e2e` for integration and user journey tests +- Use `/egc-code-review` to verify test quality ## Related Agents @@ -347,7 +347,7 @@ This command invokes the `e2e-runner` agent located at: npx playwright test # Run specific test file -npx playwright test tests/e2e/markets/search.spec.ts +npx playwright test tests/egc-e2e/markets/search.spec.ts # Run in headed mode (see browser) npx playwright test --headed diff --git a/workflows/egc-plan.md b/workflows/egc-plan.md index 792d3e6..adb5e9b 100644 --- a/workflows/egc-plan.md +++ b/workflows/egc-plan.md @@ -15,7 +15,7 @@ This command invokes the **planner** agent to create a comprehensive implementat ## When to Use -Use `/plan` when: +Use `/egc-plan` when: - Starting a new feature - Making significant architectural changes - Working on complex refactoring @@ -36,7 +36,7 @@ The planner agent will: ## Example Usage ``` -User: /plan I need to add real-time notifications when markets resolve +User: /egc-plan I need to add real-time notifications when markets resolve Agent (planner): # Implementation Plan: Real-Time Market Resolution Notifications @@ -103,9 +103,9 @@ If you want changes, respond with: ## Integration with Other Commands After planning: -- Use `/tdd` to implement with test-driven development +- Use `/egc-tdd` to implement with test-driven development - Use `/build-and-fix` if build errors occur -- Use `/code-review` to review completed implementation +- Use `/egc-code-review` to review completed implementation ## Related Agents diff --git a/workflows/eval.md b/workflows/eval.md index 0ef5b4f..8ff7cc1 100644 --- a/workflows/eval.md +++ b/workflows/eval.md @@ -8,11 +8,11 @@ Manage eval-driven development workflow. ## Usage -`/eval [define|check|report|list] [feature-name]` +`/egc-eval [define|check|report|list] [feature-name]` ## Define Evals -`/eval define feature-name` +`/egc-eval define feature-name` Create a new eval definition: @@ -39,7 +39,7 @@ Created: $(date) ## Check Evals -`/eval check feature-name` +`/egc-eval check feature-name` Run evals for a feature: @@ -64,7 +64,7 @@ Status: IN PROGRESS / READY ## Report Evals -`/eval report feature-name` +`/egc-eval report feature-name` Generate comprehensive eval report: @@ -102,7 +102,7 @@ RECOMMENDATION ## List Evals -`/eval list` +`/egc-eval list` Show all eval definitions: diff --git a/workflows/evolve.md b/workflows/evolve.md index 28db3c6..fc5dab4 100644 --- a/workflows/evolve.md +++ b/workflows/evolve.md @@ -28,10 +28,10 @@ Analyzes instincts and clusters related ones into higher-level structures: ## Usage ``` -/evolve # Analyze all instincts and suggest evolutions -/evolve --domain testing # Only evolve instincts in testing domain -/evolve --dry-run # Show what would be created without creating -/evolve --threshold 5 # Require 5+ related instincts to cluster +/egc-evolve # Analyze all instincts and suggest evolutions +/egc-evolve --domain testing # Only evolve instincts in testing domain +/egc-evolve --dry-run # Show what would be created without creating +/egc-evolve --threshold 5 # Require 5+ related instincts to cluster ``` ## Evolution Rules @@ -125,7 +125,7 @@ Files: - ~/.gemini/homunculus/evolved/agents/debugger.md --- -Run `/evolve --execute` to create these files. +Run `/egc-evolve --execute` to create these files. ``` ## Flags diff --git a/workflows/flutter-build.md b/workflows/flutter-build.md index add6b5c..cbe9657 100644 --- a/workflows/flutter-build.md +++ b/workflows/flutter-build.md @@ -16,7 +16,7 @@ This command invokes the **dart-build-resolver** agent to incrementally fix Dart ## When to Use -Use `/flutter-build` when: +Use `/egc-flutter-build` when: - `flutter analyze` reports errors - `flutter build` fails for any platform - `dart pub get` / `flutter pub get` fails with version conflicts @@ -43,7 +43,7 @@ flutter build web 2>&1 ## Example Session ````text -User: /flutter-build +User: /egc-flutter-build Agent: # Flutter Build Resolution @@ -154,9 +154,9 @@ The agent will stop and report if: ## Related Commands -- `/flutter-test` — Run tests after build succeeds -- `/flutter-review` — Review code quality -- `/verify` — Full verification loop +- `/egc-flutter-test` — Run tests after build succeeds +- `/egc-flutter-review` — Review code quality +- `/egc-verify` — Full verification loop ## Related diff --git a/workflows/flutter-review.md b/workflows/flutter-review.md index 39ad44b..bab2241 100644 --- a/workflows/flutter-review.md +++ b/workflows/flutter-review.md @@ -16,15 +16,15 @@ This command invokes the **flutter-reviewer** agent to review Flutter/Dart code ## Prerequisites -Before running `/flutter-review`, ensure: -1. **Build passes** — run `/flutter-build` first; a review on broken code is incomplete -2. **Tests pass** — run `/flutter-test` to confirm no regressions +Before running `/egc-flutter-review`, ensure: +1. **Build passes** — run `/egc-flutter-build` first; a review on broken code is incomplete +2. **Tests pass** — run `/egc-flutter-test` to confirm no regressions 3. **No merge conflicts** — resolve all conflicts so the diff reflects only intentional changes 4. **`flutter analyze` is clean** — fix analyzer warnings before review ## When to Use -Use `/flutter-review` when: +Use `/egc-flutter-review` when: - Before submitting a PR with Flutter/Dart changes (after build and tests pass) - After implementing a new feature to catch issues early - When reviewing someone else's Flutter code @@ -50,7 +50,7 @@ Use `/flutter-review` when: ## Example Session ````text -User: /flutter-review +User: /egc-flutter-review Agent: # Flutter Code Review @@ -105,9 +105,9 @@ Verdict: BLOCK — HIGH issues must be fixed before merge. ## Related Commands -- `/flutter-build` — Fix build errors first -- `/flutter-test` — Run tests before reviewing -- `/code-review` — General code review (language-agnostic) +- `/egc-flutter-build` — Fix build errors first +- `/egc-flutter-test` — Run tests before reviewing +- `/egc-code-review` — General code review (language-agnostic) ## Related diff --git a/workflows/flutter-test.md b/workflows/flutter-test.md index cc1f0e7..c2169f5 100644 --- a/workflows/flutter-test.md +++ b/workflows/flutter-test.md @@ -16,9 +16,9 @@ This command runs the Flutter test suite and reports results. When failures occu ## When to Use -Use `/flutter-test` when: +Use `/egc-flutter-test` when: - After implementing a feature to verify nothing broke -- After running `/flutter-build` to ensure tests pass +- After running `/egc-flutter-build` to ensure tests pass - To check test coverage on new code - When a specific test file is failing - Before submitting a PR @@ -48,7 +48,7 @@ flutter test --update-goldens 2>&1 ## Example Session ````text -User: /flutter-test +User: /egc-flutter-test Agent: # Flutter Test Run @@ -132,9 +132,9 @@ Test Status: PASS ✓ ## Related Commands -- `/flutter-build` — Fix build errors before running tests -- `/flutter-review` — Review code after tests pass -- `/tdd` — Test-driven development workflow +- `/egc-flutter-build` — Fix build errors before running tests +- `/egc-flutter-review` — Review code after tests pass +- `/egc-tdd` — Test-driven development workflow ## Related diff --git a/workflows/go-build.md b/workflows/go-build.md index bf32689..1b3ccf3 100644 --- a/workflows/go-build.md +++ b/workflows/go-build.md @@ -16,7 +16,7 @@ This command invokes the **go-build-resolver** agent to incrementally fix Go bui ## When to Use -Use `/go-build` when: +Use `/egc-go-build` when: - `go build ./...` fails with errors - `go vet ./...` reports issues - `golangci-lint run` shows warnings @@ -44,7 +44,7 @@ go mod tidy -v ## Example Session ```text -User: /go-build +User: /egc-go-build Agent: # Go Build Resolution @@ -173,9 +173,9 @@ The agent will stop and report if: ## Related Commands -- `/go-test` - Run tests after build succeeds -- `/go-review` - Review code quality -- `/verify` - Full verification loop +- `/egc-go-test` - Run tests after build succeeds +- `/egc-go-review` - Review code quality +- `/egc-verify` - Full verification loop ## Related diff --git a/workflows/go-review.md b/workflows/go-review.md index 9aedaf1..4d44aa7 100644 --- a/workflows/go-review.md +++ b/workflows/go-review.md @@ -17,7 +17,7 @@ This command invokes the **go-reviewer** agent for comprehensive Go-specific cod ## When to Use -Use `/go-review` when: +Use `/egc-go-review` when: - After writing or modifying Go code - Before committing Go changes - Reviewing pull requests with Go code @@ -69,7 +69,7 @@ govulncheck ./... ## Example Usage ```text -User: /go-review +User: /egc-go-review Agent: # Go Code Review Report @@ -137,10 +137,10 @@ Recommendation: ❌ Block merge until CRITICAL issue is fixed ## Integration with Other Commands -- Use `/go-test` first to ensure tests pass -- Use `/go-build` if build errors occur -- Use `/go-review` before committing -- Use `/code-review` for non-Go specific concerns +- Use `/egc-go-test` first to ensure tests pass +- Use `/egc-go-build` if build errors occur +- Use `/egc-go-review` before committing +- Use `/egc-code-review` for non-Go specific concerns ## Related diff --git a/workflows/go-test.md b/workflows/go-test.md index 94c8726..0aeafe9 100644 --- a/workflows/go-test.md +++ b/workflows/go-test.md @@ -17,7 +17,7 @@ This command enforces test-driven development methodology for Go code using idio ## When to Use -Use `/go-test` when: +Use `/egc-go-test` when: - Implementing new Go functions - Adding test coverage to existing code - Fixing bugs (write failing test first) @@ -36,7 +36,7 @@ REPEAT → Next test case ## Example Session ```text -User: /go-test I need a function to validate email addresses +User: /egc-go-test I need a function to validate email addresses Agent: # TDD Session: Email Validator @@ -258,9 +258,9 @@ go test -race -cover ./... ## Related Commands -- `/go-build` - Fix build errors -- `/go-review` - Review code after implementation -- `/verify` - Run full verification loop +- `/egc-go-build` - Fix build errors +- `/egc-go-review` - Review code after implementation +- `/egc-verify` - Run full verification loop ## Related diff --git a/workflows/hookify-configure.md b/workflows/hookify-configure.md index 578614f..ccae16d 100644 --- a/workflows/hookify-configure.md +++ b/workflows/hookify-configure.md @@ -6,7 +6,7 @@ Interactively enable or disable existing hookify rules. ## Steps -1. Find all `.gemini/hookify.*.local.md` files +1. Find all `.gemini/egc-hookify.*.local.md` files 2. Read the current state of each rule 3. Present the list with current enabled / disabled status 4. Ask which rules to toggle diff --git a/workflows/hookify-help.md b/workflows/hookify-help.md index 9914867..2b432c6 100644 --- a/workflows/hookify-help.md +++ b/workflows/hookify-help.md @@ -18,7 +18,7 @@ Hookify creates rule files that integrate with Gemini CLI's hook system to preve ### Rule File Format -Files are stored as `.gemini/hookify.{name}.local.md`: +Files are stored as `.gemini/egc-hookify.{name}.local.md`: ```yaml --- @@ -34,9 +34,9 @@ Supports multiple lines. ### Commands -- `/hookify [description]` creates new rules and auto-analyzes the conversation when no description is given -- `/hookify-list` lists configured rules -- `/hookify-configure` toggles rules on or off +- `/egc-hookify [description]` creates new rules and auto-analyzes the conversation when no description is given +- `/egc-hookify-list` lists configured rules +- `/egc-hookify-configure` toggles rules on or off ### Pattern Tips diff --git a/workflows/hookify-list.md b/workflows/hookify-list.md index e23a1bd..673a06b 100644 --- a/workflows/hookify-list.md +++ b/workflows/hookify-list.md @@ -6,7 +6,7 @@ Find and display all hookify rules in a formatted table. ## Steps -1. Find all `.gemini/hookify.*.local.md` files +1. Find all `.gemini/egc-hookify.*.local.md` files 2. Read each file's frontmatter: - `name` - `enabled` @@ -18,4 +18,4 @@ Find and display all hookify rules in a formatted table. | Rule | Enabled | Event | Pattern | File | |------|---------|-------|---------|------| -4. Show the rule count and remind the user that `/hookify-configure` can change state later. +4. Show the rule count and remind the user that `/egc-hookify-configure` can change state later. diff --git a/workflows/hookify.md b/workflows/hookify.md index 52e2a50..be93061 100644 --- a/workflows/hookify.md +++ b/workflows/hookify.md @@ -6,7 +6,7 @@ Create hook rules to prevent unwanted Gemini CLI behaviors by analyzing conversa ## Usage -`/hookify [description of behavior to prevent]` +`/egc-hookify [description of behavior to prevent]` If no arguments are provided, analyze the current conversation to find behaviors worth preventing. @@ -32,7 +32,7 @@ Show the user: ### Step 3: Generate Rule Files -For each approved rule, create a file at `.gemini/hookify.{name}.local.md`: +For each approved rule, create a file at `.gemini/egc-hookify.{name}.local.md`: ```yaml --- @@ -47,4 +47,4 @@ Message shown when rule triggers. ### Step 4: Confirm -Report created rules and how to manage them with `/hookify-list` and `/hookify-configure`. +Report created rules and how to manage them with `/egc-hookify-list` and `/egc-hookify-configure`. diff --git a/workflows/instinct-export.md b/workflows/instinct-export.md index 9b7eb01..04f4126 100644 --- a/workflows/instinct-export.md +++ b/workflows/instinct-export.md @@ -1,7 +1,7 @@ --- name: instinct-export description: Export instincts for sharing with teammates or other projects -command: /instinct-export +command: /egc-instinct-export --- # Instinct Export Command @@ -14,10 +14,10 @@ Exports instincts to a shareable format. Perfect for: ## Usage ``` -/instinct-export # Export all personal instincts -/instinct-export --domain testing # Export only testing instincts -/instinct-export --min-confidence 0.7 # Only export high-confidence instincts -/instinct-export --output team-instincts.yaml +/egc-instinct-export # Export all personal instincts +/egc-instinct-export --domain testing # Export only testing instincts +/egc-instinct-export --min-confidence 0.7 # Only export high-confidence instincts +/egc-instinct-export --output team-instincts.yaml ``` ## What to Do diff --git a/workflows/instinct-import.md b/workflows/instinct-import.md index 6189d66..2c790c2 100644 --- a/workflows/instinct-import.md +++ b/workflows/instinct-import.md @@ -29,9 +29,9 @@ Import instincts from: ## Usage ``` -/instinct-import team-instincts.yaml -/instinct-import https://github.com/org/repo/instincts.yaml -/instinct-import --from-skill-creator acme/webapp +/egc-instinct-import team-instincts.yaml +/egc-instinct-import https://github.com/org/repo/instincts.yaml +/egc-instinct-import --from-skill-creator acme/webapp ``` ## What to Do @@ -110,7 +110,7 @@ original_source: "session-observation" # or "repo-analysis" When importing from Skill Creator: ``` -/instinct-import --from-skill-creator acme/webapp +/egc-instinct-import --from-skill-creator acme/webapp ``` This fetches instincts generated from repo analysis: @@ -138,5 +138,5 @@ Skipped: 3 instincts (2 duplicates, 1 conflict) New instincts saved to: ~/.gemini/homunculus/instincts/inherited/ -Run /instinct-status to see all instincts. +Run /egc-instinct-status to see all instincts. ``` diff --git a/workflows/instinct-status.md b/workflows/instinct-status.md index 9427553..31f4994 100644 --- a/workflows/instinct-status.md +++ b/workflows/instinct-status.md @@ -25,9 +25,9 @@ python3 ~/.gemini/skills/continuous-learning-v2/scripts/instinct-cli.py status ## Usage ``` -/instinct-status -/instinct-status --domain code-style -/instinct-status --low-confidence +/egc-instinct-status +/egc-instinct-status --domain code-style +/egc-instinct-status --low-confidence ``` ## What to Do diff --git a/workflows/jira.md b/workflows/jira.md index 4830bf2..e6db185 100644 --- a/workflows/jira.md +++ b/workflows/jira.md @@ -9,10 +9,10 @@ Interact with Jira tickets directly from your workflow — fetch tickets, analyz ## Usage ``` -/jira get # Fetch and analyze a ticket -/jira comment # Add a progress comment -/jira transition # Change ticket status -/jira search # Search issues with JQL +/egc-jira get # Fetch and analyze a ticket +/egc-jira comment # Add a progress comment +/egc-jira transition # Change ticket status +/egc-jira search # Search issues with JQL ``` ## What This Command Does @@ -24,7 +24,7 @@ Interact with Jira tickets directly from your workflow — fetch tickets, analyz ## How It Works -### `/jira get ` +### `/egc-jira get ` 1. Fetch the ticket from Jira (via MCP `jira_get_issue` or REST API) 2. Extract all fields: summary, description, acceptance criteria, priority, labels, linked issues @@ -54,23 +54,23 @@ Dependencies: - [linked issues, APIs, services] Recommended Next Steps: -- /plan to create implementation plan -- /tdd to implement with tests first +- /egc-plan to create implementation plan +- /egc-tdd to implement with tests first ``` -### `/jira comment ` +### `/egc-jira comment ` 1. Summarize current session progress (what was built, tested, committed) 2. Format as a structured comment 3. Post to the Jira ticket -### `/jira transition ` +### `/egc-jira transition ` 1. Fetch available transitions for the ticket 2. Show options to user 3. Execute the selected transition -### `/jira search ` +### `/egc-jira search ` 1. Execute the JQL query against Jira 2. Return a summary table of matching issues @@ -94,11 +94,11 @@ If credentials are missing, stop and direct the user to set them up. ## Integration with Other Commands After analyzing a ticket: -- Use `/plan` to create an implementation plan from the requirements -- Use `/tdd` to implement with test-driven development -- Use `/code-review` after implementation -- Use `/jira comment` to post progress back to the ticket -- Use `/jira transition` to move the ticket when work is complete +- Use `/egc-plan` to create an implementation plan from the requirements +- Use `/egc-tdd` to implement with test-driven development +- Use `/egc-code-review` after implementation +- Use `/egc-jira comment` to post progress back to the ticket +- Use `/egc-jira transition` to move the ticket when work is complete ## Related diff --git a/workflows/learn.md b/workflows/learn.md index 07d302e..50270dd 100644 --- a/workflows/learn.md +++ b/workflows/learn.md @@ -2,13 +2,13 @@ description: Extract reusable patterns from the session and save as skills. --- -# /learn - Extract Reusable Patterns +# /egc-learn - Extract Reusable Patterns Analyze the current session and extract any patterns worth saving as skills. ## Trigger -Run `/learn` at any point during a session when you've solved a non-trivial problem. +Run `/egc-learn` at any point during a session when you've solved a non-trivial problem. ## What to Extract diff --git a/workflows/multi-backend.md b/workflows/multi-backend.md index 72c923b..510f0f7 100644 --- a/workflows/multi-backend.md +++ b/workflows/multi-backend.md @@ -125,7 +125,7 @@ Output solutions (at least 2), wait for user selection. - Context: Analysis results from Phase 2 - OUTPUT: File structure, function/class design, dependency relationships -Gemini synthesizes plan, save to `.gemini/plan/task-name.md` after user approval. +Gemini synthesizes plan, save to `.gemini/egc-plan/task-name.md` after user approval. ### Phase 4: Implementation diff --git a/workflows/multi-execute.md b/workflows/multi-execute.md index 74b500a..19509b6 100644 --- a/workflows/multi-execute.md +++ b/workflows/multi-execute.md @@ -117,7 +117,7 @@ TaskOutput({ task_id: "", block: true, timeout: 600000 }) `[Mode: Prepare]` 1. **Identify Input Type**: - - Plan file path (e.g., `.gemini/plan/xxx.md`) + - Plan file path (e.g., `.gemini/egc-plan/xxx.md`) - Direct task description 2. **Read Plan Content**: @@ -222,7 +222,7 @@ mcp__ace-tool__search_context({ - Refactor "dirty prototype" to **highly readable, maintainable, enterprise-grade code** - Remove redundant code - Ensure compliance with project's existing code standards - - **Do not generate comments/docs unless necessary**, code should be self-explanatory + - **Do not generate comments/egc-docs unless necessary**, code should be self-explanatory 4. **Minimal Scope**: - Changes limited to requirement scope only @@ -303,7 +303,7 @@ After audit passes, report to user: ```bash # Execute plan file -/ccg:execute .gemini/plan/feature-name.md +/ccg:execute .gemini/egc-plan/feature-name.md # Execute task directly (for plans already discussed in context) /ccg:execute implement user authentication based on previous plan diff --git a/workflows/multi-frontend.md b/workflows/multi-frontend.md index f1ca503..6153249 100644 --- a/workflows/multi-frontend.md +++ b/workflows/multi-frontend.md @@ -125,7 +125,7 @@ Output solutions (at least 2), wait for user selection. - Context: Analysis results from Phase 2 - OUTPUT: Component structure, UI flow, styling approach -Gemini synthesizes plan, save to `.gemini/plan/task-name.md` after user approval. +Gemini synthesizes plan, save to `.gemini/egc-plan/task-name.md` after user approval. ### Phase 4: Implementation diff --git a/workflows/multi-plan.md b/workflows/multi-plan.md index 698da34..a4e09e0 100644 --- a/workflows/multi-plan.md +++ b/workflows/multi-plan.md @@ -16,7 +16,7 @@ $ARGUMENTS - **Mandatory Parallel**: Codex/Gemini calls MUST use `run_in_background: true` (including single model calls, to avoid blocking main thread) - **Code Sovereignty**: External models have **zero filesystem write access**, all modifications by Gemini - **Stop-Loss Mechanism**: Do not proceed to next phase until current phase output is validated -- **Planning Only**: This command allows reading context and writing to `.gemini/plan/*` plan files, but **NEVER modify production code** +- **Planning Only**: This command allows reading context and writing to `.gemini/egc-plan/*` plan files, but **NEVER modify production code** --- @@ -199,19 +199,19 @@ Synthesize both analyses, generate **Step-by-step Implementation Plan**: **`/ccg:plan` responsibilities end here, MUST execute the following actions**: 1. Present complete implementation plan to user (including pseudo-code) -2. Save plan to `.gemini/plan/.md` (extract feature name from requirement, e.g., `user-auth`, `payment-module`) +2. Save plan to `.gemini/egc-plan/.md` (extract feature name from requirement, e.g., `user-auth`, `payment-module`) 3. Output prompt in **bold text** (MUST use actual saved file path): --- - **Plan generated and saved to `.gemini/plan/actual-feature-name.md`** + **Plan generated and saved to `.gemini/egc-plan/actual-feature-name.md`** **Please review the plan above. You can:** - **Modify plan**: Tell me what needs adjustment, I'll update the plan - **Execute plan**: Copy the following command to a new session ``` - /ccg:execute .gemini/plan/actual-feature-name.md + /ccg:execute .gemini/egc-plan/actual-feature-name.md ``` --- @@ -233,8 +233,8 @@ Synthesize both analyses, generate **Step-by-step Implementation Plan**: After planning completes, save plan to: -- **First planning**: `.gemini/plan/.md` -- **Iteration versions**: `.gemini/plan/-v2.md`, `.gemini/plan/-v3.md`... +- **First planning**: `.gemini/egc-plan/.md` +- **Iteration versions**: `.gemini/egc-plan/-v2.md`, `.gemini/egc-plan/-v3.md`... Plan file write should complete before presenting plan to user. @@ -245,7 +245,7 @@ Plan file write should complete before presenting plan to user. If user requests plan modifications: 1. Adjust plan content based on user feedback -2. Update `.gemini/plan/.md` file +2. Update `.gemini/egc-plan/.md` file 3. Re-present modified plan 4. Prompt user to review or execute again @@ -256,7 +256,7 @@ If user requests plan modifications: After user approves, **manually** execute: ```bash -/ccg:execute .gemini/plan/.md +/ccg:execute .gemini/egc-plan/.md ``` --- diff --git a/workflows/multi-workflow.md b/workflows/multi-workflow.md index 80a31ff..96ddf9d 100644 --- a/workflows/multi-workflow.md +++ b/workflows/multi-workflow.md @@ -152,7 +152,7 @@ Wait for results with `TaskOutput`. **Follow the `IMPORTANT` instructions in `Multi-Model Call Specification` above** -**Gemini Synthesis**: Adopt Codex backend plan + Gemini frontend plan, save to `.gemini/plan/task-name.md` after user approval. +**Gemini Synthesis**: Adopt Codex backend plan + Gemini frontend plan, save to `.gemini/egc-plan/task-name.md` after user approval. ### Phase 4: Implementation diff --git a/workflows/orchestrate.md b/workflows/orchestrate.md index 5d2a85a..190cad1 100644 --- a/workflows/orchestrate.md +++ b/workflows/orchestrate.md @@ -8,7 +8,7 @@ Sequential agent workflow for complex tasks. ## Usage -`/orchestrate [workflow-type] [task-description]` +`/egc-orchestrate [workflow-type] [task-description]` ## Workflow Types @@ -79,7 +79,7 @@ Between agents, create handoff document: ## Example: Feature Workflow ``` -/orchestrate feature "Add user authentication" +/egc-orchestrate feature "Add user authentication" ``` Executes: @@ -173,7 +173,7 @@ $ARGUMENTS: ## Custom Workflow Example ``` -/orchestrate custom "architect,tdd-guide,code-reviewer" "Redesign caching layer" +/egc-orchestrate custom "architect,tdd-guide,code-reviewer" "Redesign caching layer" ``` ## Tips diff --git a/workflows/prp-commit.md b/workflows/prp-commit.md index 85935b8..d61d886 100644 --- a/workflows/prp-commit.md +++ b/workflows/prp-commit.md @@ -94,8 +94,8 @@ Files: {count} file(s) changed Next steps: - git push → push to remote - - /prp-pr → create a pull request - - /code-review → review before pushing + - /egc-prp-pr → create a pull request + - /egc-code-review → review before pushing ``` --- @@ -104,9 +104,9 @@ Next steps: | You say | What happens | |---|---| -| `/prp-commit` | Stages all, auto-generates message | -| `/prp-commit staged` | Commits only what's already staged | -| `/prp-commit *.ts` | Stages all TypeScript files, commits | -| `/prp-commit except tests` | Stages everything except test files | -| `/prp-commit the database migration` | Finds DB migration files from status, stages them | -| `/prp-commit only new files` | Stages untracked files only | +| `/egc-prp-commit` | Stages all, auto-generates message | +| `/egc-prp-commit staged` | Commits only what's already staged | +| `/egc-prp-commit *.ts` | Stages all TypeScript files, commits | +| `/egc-prp-commit except tests` | Stages everything except test files | +| `/egc-prp-commit the database migration` | Finds DB migration files from status, stages them | +| `/egc-prp-commit only new files` | Stages untracked files only | diff --git a/workflows/prp-implement.md b/workflows/prp-implement.md index 479be68..119c85b 100644 --- a/workflows/prp-implement.md +++ b/workflows/prp-implement.md @@ -1,6 +1,6 @@ --- description: Execute an implementation plan with rigorous validation loops -argument-hint: +argument-hint: --- > Adapted from PRPs-agentic-eng by Wirasm. Part of the PRP workflow series. @@ -61,7 +61,7 @@ Extract these sections from the plan: If the file doesn't exist or isn't a valid plan: ``` Error: Plan file not found or invalid. -Run /prp-plan to create a plan first. +Run /egc-prp-plan to create a plan first. ``` **CHECKPOINT**: Plan loaded. All sections identified. Tasks extracted. @@ -267,8 +267,8 @@ Write report to `.gemini/PRPs/reports/{plan-name}-report.md`: | `path/to/test` | N tests | [area covered] | ## Next Steps -- [ ] Code review via `/code-review` -- [ ] Create PR via `/prp-pr` +- [ ] Code review via `/egc-code-review` +- [ ] Create PR via `/egc-prp-pr` ``` ### Update PRD (if applicable) @@ -326,7 +326,7 @@ Report to user: | Phase 2 | [next] | | ... | ... | -> Next step: Run `/prp-pr` to create a pull request, or `/code-review` to review changes first. +> Next step: Run `/egc-prp-pr` to create a pull request, or `/egc-code-review` to review changes first. ``` --- @@ -379,7 +379,7 @@ Report to user: ## Next Steps -- Run `/code-review` to review changes before committing -- Run `/prp-commit` to commit with a descriptive message -- Run `/prp-pr` to create a pull request -- Run `/prp-plan ` if the PRD has more phases +- Run `/egc-code-review` to review changes before committing +- Run `/egc-prp-commit` to commit with a descriptive message +- Run `/egc-prp-pr` to create a pull request +- Run `/egc-prp-plan ` if the PRD has more phases diff --git a/workflows/prp-plan.md b/workflows/prp-plan.md index f486be5..ab67b64 100644 --- a/workflows/prp-plan.md +++ b/workflows/prp-plan.md @@ -451,7 +451,7 @@ If this plan was generated from a PRD phase: - **Risks**: [top risk or "none identified"] - **Confidence Score**: [1-10] — likelihood of single-pass implementation -> Next step: Run `/prp-implement .gemini/PRPs/plans/{name}.plan.md` to execute this plan. +> Next step: Run `/egc-prp-implement .gemini/PRPs/plans/{name}.plan.md` to execute this plan. ``` --- @@ -496,7 +496,7 @@ A developer unfamiliar with this codebase should be able to implement the featur ## Next Steps -- Run `/prp-implement ` to execute this plan -- Run `/plan` for quick conversational planning without artifacts -- Run `/prp-prd` to create a PRD first if scope is unclear +- Run `/egc-prp-implement ` to execute this plan +- Run `/egc-plan` for quick conversational planning without artifacts +- Run `/egc-prp-prd` to create a PRD first if scope is unclear ```` diff --git a/workflows/prp-pr.md b/workflows/prp-pr.md index 92b853f..d01551d 100644 --- a/workflows/prp-pr.md +++ b/workflows/prp-pr.md @@ -29,7 +29,7 @@ git log origin/..HEAD --oneline | Check | Condition | Action if Failed | |---|---|---| | Not on base branch | Current branch ≠ base | Stop: "Switch to a feature branch first." | -| Clean working directory | No uncommitted changes | Warn: "You have uncommitted changes. Commit or stash first. Use `/prp-commit` to commit." | +| Clean working directory | No uncommitted changes | Warn: "You have uncommitted changes. Commit or stash first. Use `/egc-prp-commit` to commit." | | Has commits ahead | `git log origin/..HEAD` not empty | Stop: "No commits ahead of ``. Nothing to PR." | | No existing PR | `gh pr list --head --json number` is empty | Stop: "PR already exists: #. Use `gh pr view --web` to open it." | @@ -169,7 +169,7 @@ Artifacts referenced: Next steps: - gh pr view --web → open in browser - - /code-review → review the PR + - /egc-code-review → review the PR - gh pr merge → merge when ready ``` diff --git a/workflows/prp-prd.md b/workflows/prp-prd.md index 623d23b..a9a249b 100644 --- a/workflows/prp-prd.md +++ b/workflows/prp-prd.md @@ -389,7 +389,7 @@ After generating, report: ### To Start Implementation -Run: `/prp-plan .gemini/PRPs/prds/{name}.prd.md` +Run: `/egc-prp-plan .gemini/PRPs/prds/{name}.prd.md` This will automatically select the next pending phase and create an implementation plan. ``` @@ -433,9 +433,9 @@ This will automatically select the next pending phase and create an implementati ## Integration with ECC After PRD generation: -- Use `/prp-plan` to create implementation plans from PRD phases -- Use `/plan` for simpler planning without PRD structure -- Use `/save-session` to preserve PRD context across sessions +- Use `/egc-prp-plan` to create implementation plans from PRD phases +- Use `/egc-plan` for simpler planning without PRD structure +- Use `/egc-save-session` to preserve PRD context across sessions ## Success Criteria diff --git a/workflows/python-review.md b/workflows/python-review.md index ba594b2..fdf12df 100644 --- a/workflows/python-review.md +++ b/workflows/python-review.md @@ -17,7 +17,7 @@ This command invokes the **python-reviewer** agent for comprehensive Python-spec ## When to Use -Use `/python-review` when: +Use `/egc-python-review` when: - After writing or modifying Python code - Before committing Python changes - Reviewing pull requests with Python code @@ -77,7 +77,7 @@ pytest --cov=app --cov-report=term-missing ## Example Usage ```text -User: /python-review +User: /egc-python-review Agent: # Python Code Review Report @@ -172,9 +172,9 @@ Run: `black app/routes/user.py app/services/auth.py` ## Integration with Other Commands - Use `/python-test` first to ensure tests pass -- Use `/code-review` for non-Python specific concerns -- Use `/python-review` before committing -- Use `/build-fix` if static analysis tools fail +- Use `/egc-code-review` for non-Python specific concerns +- Use `/egc-python-review` before committing +- Use `/egc-build-fix` if static analysis tools fail ## Framework-Specific Reviews diff --git a/workflows/review-pr.md b/workflows/review-pr.md index 9fe08f1..e293c2c 100644 --- a/workflows/review-pr.md +++ b/workflows/review-pr.md @@ -6,7 +6,7 @@ Run a comprehensive multi-perspective review of a pull request. ## Usage -`/review-pr [PR-number-or-URL] [--focus=comments|tests|errors|types|code|simplify]` +`/egc-review-pr [PR-number-or-URL] [--focus=comments|tests|errors|types|code|simplify]` If no PR is specified, review the current branch's PR. If no focus is specified, run the full review stack. diff --git a/workflows/santa-loop.md b/workflows/santa-loop.md index a0e2e2d..c4af1a6 100644 --- a/workflows/santa-loop.md +++ b/workflows/santa-loop.md @@ -13,7 +13,7 @@ Run two independent reviewers (Gemini Ultra + an external model) against the cur ## Usage ``` -/santa-loop [file-or-glob | description] +/egc-santa-loop [file-or-glob | description] ``` ## Workflow diff --git a/workflows/sessions.md b/workflows/sessions.md index 993c151..b6b5ecc 100644 --- a/workflows/sessions.md +++ b/workflows/sessions.md @@ -4,11 +4,11 @@ description: Manage Gemini CLI session history, listing, and loading. # Sessions Command -Manage Gemini CLI session history - list, load, alias, and edit sessions stored in `~/.gemini/sessions/`. +Manage Gemini CLI session history - list, load, alias, and edit sessions stored in `~/.gemini/egc-sessions/`. ## Usage -`/sessions [list|load|alias|info|help] [options]` +`/egc-sessions [list|load|alias|info|help] [options]` ## Actions @@ -17,11 +17,11 @@ Manage Gemini CLI session history - list, load, alias, and edit sessions stored Display all sessions with metadata, filtering, and pagination. ```bash -/sessions # List all sessions (default) -/sessions list # Same as above -/sessions list --limit 10 # Show 10 sessions -/sessions list --date 2026-02-01 # Filter by date -/sessions list --search abc # Search by session ID +/egc-sessions # List all sessions (default) +/egc-sessions list # Same as above +/egc-sessions list --limit 10 # Show 10 sessions +/egc-sessions list --date 2026-02-01 # Filter by date +/egc-sessions list --search abc # Search by session ID ``` **Script:** @@ -58,10 +58,10 @@ for (const s of result.sessions) { Load and display a session's content (by ID or alias). ```bash -/sessions load # Load session -/sessions load 2026-02-01 # By date (for no-id sessions) -/sessions load a1b2c3d4 # By short ID -/sessions load my-alias # By alias name +/egc-sessions load # Load session +/egc-sessions load 2026-02-01 # By date (for no-id sessions) +/egc-sessions load a1b2c3d4 # By short ID +/egc-sessions load my-alias # By alias name ``` **Script:** @@ -87,7 +87,7 @@ const size = sm.getSessionSize(session.sessionPath); const aliases = aa.getAliasesForSession(session.filename); console.log('Session: ' + session.filename); -console.log('Path: ~/.gemini/sessions/' + session.filename); +console.log('Path: ~/.gemini/egc-sessions/' + session.filename); console.log(''); console.log('Statistics:'); console.log(' Lines: ' + stats.lineCount); @@ -122,8 +122,8 @@ if (session.metadata.lastUpdated) { Create a memorable alias for a session. ```bash -/sessions alias # Create alias -/sessions alias 2026-02-01 today-work # Create alias named "today-work" +/egc-sessions alias # Create alias +/egc-sessions alias 2026-02-01 today-work # Create alias named "today-work" ``` **Script:** @@ -137,7 +137,7 @@ const sessionId = process.argv[1]; const aliasName = process.argv[2]; if (!sessionId || !aliasName) { - console.log('Usage: /sessions alias '); + console.log('Usage: /egc-sessions alias '); process.exit(1); } @@ -163,8 +163,8 @@ if (result.success) { Delete an existing alias. ```bash -/sessions alias --remove # Remove alias -/sessions unalias # Same as above +/egc-sessions alias --remove # Remove alias +/egc-sessions unalias # Same as above ``` **Script:** @@ -175,7 +175,7 @@ const aa = require('./scripts/lib/session-aliases'); const aliasName = process.argv[1]; if (!aliasName) { - console.log('Usage: /sessions alias --remove '); + console.log('Usage: /egc-sessions alias --remove '); process.exit(1); } @@ -194,7 +194,7 @@ if (result.success) { Show detailed information about a session. ```bash -/sessions info # Show session details +/egc-sessions info # Show session details ``` **Script:** @@ -242,7 +242,7 @@ if (aliases.length > 0) { Show all session aliases. ```bash -/sessions aliases # List all aliases +/egc-sessions aliases # List all aliases ``` **Script:** @@ -290,27 +290,27 @@ $ARGUMENTS: ```bash # List all sessions -/sessions list +/egc-sessions list # Create an alias for today's session -/sessions alias 2026-02-01 today +/egc-sessions alias 2026-02-01 today # Load session by alias -/sessions load today +/egc-sessions load today # Show session info -/sessions info today +/egc-sessions info today # Remove alias -/sessions alias --remove today +/egc-sessions alias --remove today # List all aliases -/sessions aliases +/egc-sessions aliases ``` ## Notes -- Sessions are stored as markdown files in `~/.gemini/sessions/` +- Sessions are stored as markdown files in `~/.gemini/egc-sessions/` - Aliases are stored in `~/.gemini/session-aliases.json` - Session IDs can be shortened (first 4-8 characters usually unique enough) - Use aliases for frequently referenced sessions diff --git a/workflows/skill-create.md b/workflows/skill-create.md index 3d00fbe..5a4e2a4 100644 --- a/workflows/skill-create.md +++ b/workflows/skill-create.md @@ -4,17 +4,17 @@ description: Analyze local git history to extract coding patterns and generate S allowed_tools: ["Bash", "Read", "Write", "Grep", "Glob"] --- -# /skill-create - Local Skill Generation +# /egc-skill-create - Local Skill Generation Analyze your repository's git history to extract coding patterns and generate SKILL.md files that teach Gemini your team's practices. ## Usage ```bash -/skill-create # Analyze current repo -/skill-create --commits 100 # Analyze last 100 commits -/skill-create --output ./skills # Custom output directory -/skill-create --instincts # Also generate instincts for continuous-learning-v2 +/egc-skill-create # Analyze current repo +/egc-skill-create --commits 100 # Analyze last 100 commits +/egc-skill-create --output ./skills # Custom output directory +/egc-skill-create --instincts # Also generate instincts for continuous-learning-v2 ``` ## What It Does @@ -104,7 +104,7 @@ Prefix commits with: feat:, fix:, chore:, docs:, test:, refactor: ## Example Output -Running `/skill-create` on a TypeScript project might produce: +Running `/egc-skill-create` on a TypeScript project might produce: ```markdown --- @@ -165,9 +165,9 @@ For advanced features (10k+ commits, team sharing, auto-PRs), use the [Skill Cre ## Related Commands -- `/instinct-import` - Import generated instincts -- `/instinct-status` - View learned instincts -- `/evolve` - Cluster instincts into skills/agents +- `/egc-instinct-import` - Import generated instincts +- `/egc-instinct-status` - View learned instincts +- `/egc-evolve` - Cluster instincts into skills/agents --- diff --git a/workflows/tdd.md b/workflows/tdd.md index b04c653..e233222 100644 --- a/workflows/tdd.md +++ b/workflows/tdd.md @@ -16,7 +16,7 @@ This command invokes the **tdd-guide** agent to enforce test-driven development ## When to Use -Use `/tdd` when: +Use `/egc-tdd` when: - Implementing new features - Adding new functions/components - Fixing bugs (write test that reproduces bug first) @@ -49,7 +49,7 @@ REPEAT: Next feature/scenario ## Example Usage ``` -User: /tdd I need a function to calculate market liquidity score +User: /egc-tdd I need a function to calculate market liquidity score Agent (tdd-guide): # TDD Session: Market Liquidity Score Calculator @@ -285,7 +285,7 @@ Coverage: 100% ✅ (Target: 80%) - External service calls - React components with hooks -**E2E Tests** (use `/e2e` command): +**E2E Tests** (use `/egc-e2e` command): - Critical user flows - Multi-step processes - Full stack integration @@ -311,11 +311,11 @@ Never skip the RED phase. Never write code before tests. ## Integration with Other Commands -- Use `/plan` first to understand what to build -- Use `/tdd` to implement with tests +- Use `/egc-plan` first to understand what to build +- Use `/egc-tdd` to implement with tests - Use `/build-and-fix` if build errors occur -- Use `/code-review` to review implementation -- Use `/test-coverage` to verify coverage +- Use `/egc-code-review` to review implementation +- Use `/egc-test-coverage` to verify coverage ## Related Agents