egc

# EGC - Extended Global Context Conventions ## Overview This skill teaches the development patterns and conventions used in EGC (Extended Global Context). ## Tech Stack - **Primary Language**: JavaScript - **Architecture**: hybrid module organization - **Test Location**: separate ## When to Use This Skill Activate this skill when: - Making changes to this repository - Adding new features following established patterns - Writing tests that match project conventions - Creating commits with proper message format ## Commit Conventions Follow these commit message conventions based on 500 analyzed commits. ### Commit Style: Conventional Commits ### Prefixes Used - `fix` - `test` - `feat` - `docs` ### Message Guidelines - Average message length: ~65 characters - Keep first line concise and descriptive - Use imperative mood ("Add feature" not "Added feature") *Commit message example* ```text feat(rules): add C# language support ``` *Commit message example* ```text chore(deps-dev): bump flatted (#675) ``` *Commit message example* ```text fix: auto-detect EGC root from plugin cache when GEMINI_PLUGIN_ROOT is unset (#547) (#691) ``` *Commit message example* ```text docs: add Antigravity setup and usage guide (#552) ``` *Commit message example* ```text merge: PR #529: feat(skills): add documentation-lookup, bun-runtime, nextjs-turbopack; feat(agents): add rust-reviewer ``` *Commit message example* ```text Revert "Add Kiro IDE support (.kiro/) (#548)" ``` *Comm...