zsp/everything-claude-code
1
0
Fork 0
mirror of https://github.com/affaan-m/everything-claude-code.git synced 2026-06-26 01:51:30 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'main' into feat-ml-adoption

Browse Source
This commit is contained in:
Sebastian
2026-06-10 17:51:17 -04:00
committed by GitHub
parent d4ed8baef3 c888d2b73f
commit 515c275b30
52 changed files with 1079 additions and 491 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/MCP-CONNECTOR-POLICY.md
+43
View File
@@ -0,0 +1,43 @@
# MCP Connector Policy
ECC ships exactly one default MCP connector. Everything else is a skill wrapping a CLI or REST API, or an opt-in entry in `mcp-configs/mcp-servers.json`.
## The rule
A default connector earns its slot only if both hold:
1. **Universal** — it applies to essentially every user of a coding agent, on every harness ECC targets.
2. **MCP beats a CLI/API wrapped in a skill** — the job genuinely needs what MCP provides: interactive session state, streaming, an auth handshake, or structured browsing. Stateless request/response work is a skill, not a server. Tool schemas load into every session; each default connector taxes every user's context window whether they use it or not.
The default set stays well under ten. In practice the 2026 field default across serious harnesses is zero to two connectors plus native built-ins.
## Current default set
| Server | Why it passes |
|---|---|
| `chrome-devtools` | Google's official DevTools MCP. Interactive CDP sessions — live debugging, performance traces, console and network inspection on a stateful browser. This is the textbook case where MCP beats a CLI: the value is the held-open session, not a one-shot command. Keyless. |
## The six it replaced (June 2026 audit)
| Former default | Verdict | Replacement |
|---|---|---|
| `github` | drop for skill | `gh` CLI via the `github-ops` skill. `gh` is in every model's training data, composes one-shot commands with minimal token overhead, and auths once via `gh auth login`. The MCP server's ~30 tool schemas taxed every session. |
| `context7` | drop for skill | The `documentation-lookup` skill targeting Context7's public REST API (`/api/v2/libs/search`, `/api/v2/context`). Two stateless calls with a bearer key — no session state to justify a server. |
| `exa` | drop for skill | Harness-native search (Claude Code WebSearch, Codex web_search, Cursor @Web) by default; the `exa-search` skill remains for API-key holders. Also required an API key, which fails the universality test for a default. |
| `memory` | drop entirely | Native harness memory (Claude Code auto-memory directories, Cursor memories, AGENTS.md conventions) plus ECC's instinct/continuous-learning system. The knowledge-graph server solved a 2024 problem harnesses have since absorbed. |
| `playwright` | drop for skill | Microsoft's own `@playwright/cli` agent surface — the vendor itself moved agent workflows off MCP because returning full accessibility trees per step burns context. ECC's e2e skills already drive the CLI. Browser *debugging* (the interactive case) is covered by `chrome-devtools`. |
| `sequential-thinking` | drop entirely | Native extended thinking in every modern harness. The server wrapped no external system — a prompting pattern dressed as a connector. |
All six remain available as opt-in entries in `mcp-configs/mcp-servers.json` for users who want them.
## Opt-out
`ECC_DISABLED_MCPS` filters ECC-generated MCP configs at install/sync time:
```bash
export ECC_DISABLED_MCPS="chrome-devtools"
```
## Adding a connector
Open a PR that argues both prongs of the rule explicitly. "Popular" is not an argument; "the job is stateful and universal" is.
docs/SELECTIVE-INSTALL-ARCHITECTURE.md
+1 -1
View File
@@ -703,7 +703,7 @@ Suggested payload:
"skippedModules": []
},
"source": {
"repoVersion": "2.0.0-rc.1",
"repoVersion": "2.0.0",
"repoCommit": "git-sha",
"manifestVersion": 1
},
docs/de-DE/README.md
+6 -7
View File
@@ -1533,10 +1533,9 @@ ECC bietet **GitHub-Copilot-Unterstützung** für VS Code über das native Instr
| Komponente | Datei | Zweck |
|-----------|------|---------|
| Kern-Instructions | `.github/copilot-instructions.md` | Stets geladene Rules: Coding-Style, Sicherheit, Testing, Git-Workflow |
| VS-Code-Einstellungen | `.vscode/settings.json` | Aufgabenspezifische Instruction-Dateien für Codegenerierung, Testgenerierung, Review und Commit-Nachrichten |
| VS-Code-Einstellungen | `.vscode/settings.json` | Aufgabenspezifische Instruction-Dateien für Codegenerierung, Testgenerierung und Commit-Nachrichten |
| Plan-Prompt | `.github/prompts/plan.prompt.md` | Phasenweise Implementierungsplanung |
| TDD-Prompt | `.github/prompts/tdd.prompt.md` | Red-Green-Improve-Zyklus |
| Code-Review-Prompt | `.github/prompts/code-review.prompt.md` | Qualitäts- und Sicherheitsreview |
| Security-Review-Prompt | `.github/prompts/security-review.prompt.md` | Tiefe, OWASP-orientierte Sicherheitsanalyse |
| Build-Fix-Prompt | `.github/prompts/build-fix.prompt.md` | Systematische Behebung von Build- und CI-Fehlern |
| Refactor-Prompt | `.github/prompts/refactor.prompt.md` | Beseitigung von totem Code und Vereinfachung |
@@ -1549,16 +1548,16 @@ Die eingecheckte `.vscode/settings.json` aktiviert `chat.promptFiles`, sodass VS
So verwendest du die Workflow-Prompts in Copilot Chat:
1. Öffne das Copilot-Chat-Panel in VS Code.
2. Klicke auf das **Büroklammer-/Anhängen-Symbol** und wähle **Prompt...**, oder tippe `/` und wähle einen Prompt.
3. Wähle den Prompt aus (z. B. `plan`, `tdd`, `code-review`).
3. Wähle den Prompt aus (z. B. `plan`, `tdd`, `security-review`).
### Wie es funktioniert
GitHub Copilot in VS Code liest zwei Dateitypen automatisch:
- **`.github/copilot-instructions.md`** — Instructions auf Repository-Ebene, die in jede Copilot-Chat-Anfrage injiziert werden. Enthält ECCs Kern-Coding-Standards, Sicherheits-Checkliste, Testanforderungen und Git-Workflow.
- **`.github/prompts/*.prompt.md`** — wiederverwendbare Prompt-Dateien, die Nutzer bei Bedarf aufrufen. Jeder Prompt führt Copilot durch einen bestimmten ECC-Workflow (plan → TDD → review → ship).
- **`.github/prompts/*.prompt.md`** — wiederverwendbare Prompt-Dateien, die Nutzer bei Bedarf aufrufen. Jeder Prompt führt Copilot durch einen bestimmten ECC-Workflow wie Planung, TDD, Security-Review, Build-Fix oder Refactor.
Die **`.vscode/settings.json`** fügt aufgabenspezifische Instruction-Overlays hinzu, sodass Copilot je nachdem, ob du Code generierst, Tests schreibst, eine Auswahl reviewst oder eine Commit-Nachricht entwirfst, den richtigen Kontext erhält.
Die **`.vscode/settings.json`** fügt aufgabenspezifische Instruction-Overlays hinzu, sodass Copilot für Codegenerierung, Testgenerierung und Commit-Nachrichten den richtigen Kontext erhält.
### Feature-Abdeckung
@@ -1568,7 +1567,7 @@ Die **`.vscode/settings.json`** fügt aufgabenspezifische Instruction-Overlays h
| Sicherheits-Checkliste | Stets aktiv + `security-review`-Prompt |
| Testing / TDD | Stets aktiv + `tdd`-Prompt |
| Implementierungsplanung | `plan`-Prompt |
| Code-Review | `code-review`-Prompt |
| Code-Review | Externes PR-Review über CodeRabbit + Greptile |
| Behebung von Build-Fehlern | `build-fix`-Prompt |
| Refactoring | `refactor`-Prompt |
| Commit-Nachrichten-Format | Aufgabenspezifische Instruction in `settings.json` |
@@ -1588,7 +1587,7 @@ ECC ist das **erste Plugin, das jedes große KI-Coding-Tool ausreizt**. So vergl
| Feature | Claude Code | Cursor IDE | Codex CLI | OpenCode | GitHub Copilot |
|---------|------------|------------|-----------|----------|----------------|
| **Agents** | 60 | Gemeinsam (AGENTS.md) | Gemeinsam (AGENTS.md) | 12 | Nicht verfügbar |
| **Commands** | 75 | Gemeinsam | Instruction-basiert | 35 | 6 Prompts |
| **Commands** | 75 | Gemeinsam | Instruction-basiert | 35 | 5 Prompts |
| **Skills** | 232 | Gemeinsam | 10 (natives Format) | 37 | Über Instructions |
| **Hook-Events** | 8 Typen | 15 Typen | Noch keine | 11 Typen | Keine |
| **Hook-Skripte** | 20+ Skripte | 16 Skripte (DRY-Adapter) | Nicht verfügbar | Plugin-Hooks | Nicht verfügbar |
docs/es/README.md
+3 -4
View File
@@ -1215,10 +1215,9 @@ ECC proporciona **soporte para GitHub Copilot** para VS Code mediante el sistema
| Componente | Archivo | Propósito |
|------------|---------|-----------|
| Instrucciones principales | `.github/copilot-instructions.md` | Reglas siempre cargadas: estilo de código, seguridad, pruebas, flujo de git |
| Configuración de VS Code | `.vscode/settings.json` | Archivos de instrucciones por tarea para generación de código, pruebas, revisión y mensajes de commit |
| Configuración de VS Code | `.vscode/settings.json` | Archivos de instrucciones por tarea para generación de código, pruebas y mensajes de commit |
| Prompt de plan | `.github/prompts/plan.prompt.md` | Planificación de implementación por fases |
| Prompt de TDD | `.github/prompts/tdd.prompt.md` | Ciclo Rojo-Verde-Mejorar |
| Prompt de revisión de código | `.github/prompts/code-review.prompt.md` | Revisión de calidad y seguridad |
| Prompt de revisión de seguridad | `.github/prompts/security-review.prompt.md` | Análisis de seguridad profundo alineado con OWASP |
| Prompt de corrección de build | `.github/prompts/build-fix.prompt.md` | Resolución sistemática de errores de build y CI |
| Prompt de refactorización | `.github/prompts/refactor.prompt.md` | Limpieza de código muerto y simplificación |
@@ -1231,7 +1230,7 @@ El `.vscode/settings.json` confirmado habilita `chat.promptFiles` para que VS Co
Para usar los prompts de flujo de trabajo en Copilot Chat:
1. Abre el panel de Copilot Chat en VS Code.
2. Haz clic en el icono de **clip / adjuntar** y selecciona **Prompt...**, o escribe `/` y elige un prompt.
3. Selecciona el prompt (por ejemplo, `plan`, `tdd`, `code-review`).
3. Selecciona el prompt (por ejemplo, `plan`, `tdd`, `security-review`).
---
@@ -1242,7 +1241,7 @@ ECC es el **primer plugin que maximiza todas las principales herramientas de cod
| Característica | Claude Code | Cursor IDE | Codex CLI | OpenCode | GitHub Copilot |
|----------------|-----------------------|------------|-----------|----------|----------------|
| **Agentes** | 63 | Compartidos (AGENTS.md) | Compartidos (AGENTS.md) | 12 | N/A |
| **Comandos** | 79 | Compartidos | Basados en instrucciones | 35 | 6 prompts |
| **Comandos** | 79 | Compartidos | Basados en instrucciones | 35 | 5 prompts |
| **Skills** | 249 | Compartidas | 10 (formato nativo) | 37 | Mediante instrucciones |
| **Eventos de Hook** | 8 tipos | 15 tipos | Ninguno aún | 11 tipos | Ninguno |
| **Scripts de Hook** | 20+ scripts | 16 scripts (adaptador DRY) | N/A | Hooks de plugin | N/A |
docs/pt-BR/README.md
+4
View File
@@ -80,6 +80,10 @@ Este repositório contém apenas o código. Os guias explicam tudo.
## O Que Há de Novo
### v2.0.0 — O Sistema Operacional do Harness de Agentes (Jun 2026)
Graduação estável da linha 2.0: 261 skills, substrato de control-pane, inventário MCP, serviço de ciclo de vida de worktrees e a comunidade no [Discord](https://discord.gg/36yGMHGFbR).
### v2.0.0-rc.1 — Sincronização de Superfície, Fluxos Operacionais e ECC 2.0 Alpha (Abr 2026)
- **Superfície pública sincronizada com o repositório real** — metadados, contagens de catálogo, manifests de plugin e documentação de instalação agora refletem a superfície OSS que realmente é entregue.
docs/releases/2.0.0/release-notes.md
+43
View File
@@ -0,0 +1,43 @@
# ECC 2.0.0 — The Agent Harness Operating System
ECC 2.0.0 is the stable graduation of the 2.0 line: ECC as a cross-harness operating system for agentic work. Claude Code stays first-class; Codex, OpenCode, Cursor, Gemini, Zed, and terminal-only workflows share the same skills, rules, hooks, MCP conventions, release gates, and operator workflows.
## Highlights
- 261 public skills across coding, research, security, media, enterprise ops, and agent workflows.
- ECC 2.0 control-pane substrate: harness-neutral session adapters (`ecc.session.v1`) covering Claude Code, Codex, OpenCode, and dmux.
- MCP inventory (`ecc.mcp.v1`): one normalized view of MCP server configs across harnesses, with fragmentation and drift detection and secret redaction.
- Worktree-lifecycle service: deterministic conflict prediction and safe garbage collection for parallel agent worktrees.
- `orch-*` orchestrator skill family plus dynamic workflow team orchestration.
- Rollout-derived optimization pack: `parallel-execution-optimizer`, `benchmark-optimization-loop`, `data-throughput-accelerator`, `latency-critical-systems`, `recursive-decision-ledger`.
## Hardening since rc.1
Roughly thirty PRs of fixes landed between rc.1 and stable. The ones worth knowing about:
- **Plugin hooks were silently no-ops on Node 21+** (#2184). The hook runner depended on `require.main` under `node -e`, which newer Node leaves undefined — every plugin hook exited cleanly without running. If you are on Node 21 or newer, update now.
- Windows reliability: `CLAUDE_PLUGIN_ROOT` path normalization (#2139), prompts passed via stdin so the shell does not mangle them (#2174), broken-symlink and chmod test guards (#2171, #2176).
- Security: curl credentials kept out of argv (#2175), gateguard now gates force/path checkouts as destructive (#2158) with env knobs for routine-command gating (#2161), advisory intake hardening.
- Correctness: session-end summaries no longer corrupt `$`-sequences in user messages (#2180), project detection matches package keys on boundaries so `preact` no longer reads as `react` (#2181), install manifest packaging gaps closed (#2172), corrupted legacy command shims truncated safely (#2167).
- Slimmer defaults: smaller OpenCode install surface with gated hooks-runtime (#2140), `rules/zh` out of the always-loaded default install (#2170).
- New surfaces: `kubernetes-patterns` skill (#2178), worktree-lifecycle service (#2164), MCP inventory (#2146), codex-worktree and opencode session adapters (#2145), the `orch-*` family (#2153).
## Community launch
The ECC Discord is live: <https://discord.gg/36yGMHGFbR>
- Release news lands in #announcements, auto-posted and pinned by the release workflow shipped in this very release (#2201).
- A live PR and issue feed runs in #pr-and-issues.
- The ECC bot answers `/skill`, `/docs`, and `/release` lookups in-server.
- #feedback and #feature-requests are read directly by the maintainer and shape the roadmap.
## Install or upgrade
```
/plugin marketplace add https://github.com/affaan-m/ECC
/plugin install ecc
```
Existing installs: `/plugin update ecc`
Full changelog: <https://github.com/affaan-m/ECC/compare/v2.0.0-rc.1...v2.0.0>
docs/tr/AGENTS.md
+1 -1
View File
@@ -2,7 +2,7 @@
Bu, yazılım geliştirme için 28 özel agent, 116 skill, 59 command ve otomatik hook iş akışları sağlayan **üretime hazır bir AI kodlama eklentisidir**.
**Sürüm:** 2.0.0-rc.1
**Sürüm:** 2.0.0
## Temel İlkeler
docs/tr/README.md
+4
View File
@@ -79,6 +79,10 @@ Bu repository yalnızca ham kodu içerir. Rehberler her şeyi açıklıyor.
## Yenilikler
### v2.0.0 — Ajan Harness İşletim Sistemi (Haz 2026)
2.0 hattının kararlı sürümü: 261 skill, control-pane altyapısı, MCP envanteri, worktree yaşam döngüsü servisi ve [Discord topluluğu](https://discord.gg/36yGMHGFbR).
### v2.0.0-rc.1 — Surface Sync, Operatör İş Akışları ve ECC 2.0 Alpha (Nis 2026)
- **Public surface canlı repo ile senkronlandı** — metadata, katalog sayıları, plugin manifest'leri ve kurulum odaklı dokümanlar artık gerçek OSS yüzeyiyle eşleşiyor.
docs/zh-CN/AGENTS.md
+1 -1
View File
@@ -2,7 +2,7 @@
这是一个**生产就绪的 AI 编码插件**，提供 64 个专业代理、262 项技能、84 条命令以及自动化钩子工作流，用于软件开发。
**版本:** 2.0.0-rc.1
**版本:** 2.0.0
## 核心原则
docs/zh-CN/README.md
+5 -1
View File
@@ -81,6 +81,10 @@
## 最新动态
### v2.0.0 — 智能体 Harness 操作系统（2026年6月）
2.0 主线稳定版：261 个技能、control-pane 基底（会话适配器 + MCP 清单）、worktree 生命周期服务，以及 [ECC Discord 社区](https://discord.gg/36yGMHGFbR)。
### v2.0.0-rc.1 — 表面同步、运营工作流与 ECC 2.0 Alpha（2026年4月）
* **公共表面已与真实仓库同步** —— 元数据、目录数量、插件清单以及安装文档现在都与实际开源表面保持一致。
@@ -1256,7 +1260,7 @@ ECC 是**第一个最大化利用每个主要 AI 编码工具的插件**。以
| **上下文文件** | CLAUDE.md + AGENTS.md | AGENTS.md | AGENTS.md | AGENTS.md |
| **秘密检测** | 基于钩子 | beforeSubmitPrompt 钩子 | 基于沙箱 | 基于钩子 |
| **自动格式化** | PostToolUse 钩子 | afterFileEdit 钩子 | N/A | file.edited 钩子 |
| **版本** | 插件 | 插件 | 参考配置 | 2.0.0-rc.1 |
| **版本** | 插件 | 插件 | 参考配置 | 2.0.0 |
**关键架构决策：**