What is ECC?
ECC provides reusable workflows and configuration for AI coding tools. Its components cover planning, test-driven development, implementation, code review, security checks, and verification. Skills supply contextual knowledge and procedures, specialized agents support delegated tasks, and hooks automate actions around development sessions.
The toolkit installs into existing coding environments through native plugins or managed adapters. The sources describe Claude Code as its most complete target, with native plugin paths for Codex and Qoder and more limited adapters for other hosts. ECC is MIT-licensed; its open-source toolkit is distinct from the hosted ECC Pro GitHub App.
Key capabilities
- Development workflows: Skills cover testing, research, code review, documentation, and domain-specific engineering tasks.
- Specialized agents: Delegated roles support planning, architecture, security review, and build repair.
- Hooks and memory: Runtime hooks, session summaries, and continuous learning support context management and reusable working patterns.
- Configuration scanning: AgentShield scans prompts, hooks, MCP configuration, permissions, secrets, and agent files.
- Selective installation: Install profiles and component selection tailor the toolkit to a project and its coding environment.
- Usage reporting: A Claude Code cost-tracking skill reports token usage and estimated spending from local hook-generated logs.
Where ECC fits
ECC fits into development workflows where individuals or teams want recurring planning, testing, review, and verification procedures available inside their AI coding tools. Its skills also provide language conventions, framework patterns, reference material, and project onboarding guidance.
Before deployment, teams should check the support matrix for their chosen host, review package code and hook behavior, and confirm installation prerequisites and scope. Installation methods should not be stacked within the same host because they can duplicate skills, commands, hooks, or configuration. Cost reporting requires the relevant hook and an existing local metrics log; documentation lookup requires Context7 MCP to be configured.
Positioning and limitations
ECC suits developers and engineering teams already using AI coding tools who want a shared set of reusable workflows and configuration. It extends those tools rather than replacing them. Support is not uniform across hosts, some components require separate configuration, and the Claude Code plugin does not distribute rule packs.
Why it matters
ECC makes recurring engineering procedures available as reusable components rather than requiring them to be restated in each prompt. Its combination of skills, review roles, hooks, and memory provides a structure for AI-assisted work, while host-specific limitations and installation choices remain important deployment considerations.
ECC: key facts
- First published
- Profile updated
- Access
- Self-hosted
- Source model
- Open source
- GitHub repository stars
- 294,220
- Repository forks
- 43,564
- Main repository language
- JavaScript
- Recorded profile views
- 27
- Repository license
- MIT ↗
- Pricing model
- Open source
- Repository release
- v2.2.3 ↗ ·
- Website
- github.com ↗
- GitHub
- Source repository ↗
Compare ECC and explore alternatives
Compare deployment, pricing model and available integrations with tools that match your workload.
What to verify
Start from the users, systems and operating responsibilities the tool needs to support.
- Confirm current features, licensing and support terms.
- Validate deployment, data location and access control.
- Test integrations, exports and recovery workflows.
Reviews of ECC
No published reviews yet.
Loading review form…
