ecc-workflow
/ecc-workflow
Obsługuje cykl inżynierski z wieloma agentami: planowanie, wdrażanie funkcji, naprawę błędów, TDD i przeglądy kodu w różnych narzędziach AI.
- Autor
- smartworldarafath ↗
- Repozytorium
- REA_Skill ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 10.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 5
Brak sygnałów. Repozytorium zmienione 10.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Obsługuje cykl inżynierski z wieloma agentami: planowanie, wdrażanie funkcji, naprawę błędów, TDD i przeglądy kodu w różnych narzędziach AI.
Oryginalny opis (EN)
Everything Claude Code (ECC) engineering harness and multi-agent workflow system. Use when planning, implementing features, fixing bugs, applying TDD, running code reviews, or orchestrating subagents across Claude Code, Codex, Antigravity, Cursor, and Windsurf.
Jak działa
- 🏛️ The 6-Stage ECC Development Pipeline
- 🔄 ECC Orchestration Workflows (orch-)
- 🤝 Pairing ECC with REA & Agent Reach
- 🛠️ Official ECC Setup & Tools
Podgląd SKILL.md
---
name: ecc-workflow
description: Everything Claude Code (ECC) engineering harness and multi-agent workflow system. Use when planning, implementing features, fixing bugs, applying TDD, running code reviews, or orchestrating subagents across Claude Code, Codex, Antigravity, Cursor, and Windsurf.
---
# ECC Workflow (Everything Claude Code Agent Harness)
The ultimate agent harness performance optimization system based on [affaan-m/everything-claude-code](https://github.com/affaan-m/everything-claude-code). It equips AI coding agents with research-first development, TDD discipline, systematic debugging, automated code reviews, and verification gates.
---
## 🏛️ The 6-Stage ECC Development Pipeline
Every non-trivial engineering task follows the ECC standard pipeline:
```mermaid
flowchart LR
A["0. Research & Reuse"] --> B["1. Plan First"]
B --> C["2. TDD (Red-Green-Refactor)"]
C --> D["3. Autonomous Code Review"]
D --> E["4. Pre-Commit Security Audit"]
E --> F["5. Verification Before Completion"]
```
### Stage 0: Research & Reuse (Mandatory Before Coding)
1. **GitHub Code Search First:** Search GitHub repositories and existing code for proven implementations or templates before writing anything new:
```bash
gh search repos "<keyword>" --limit 5
gh search code "<pattern>" --limit 5
```
2. **Library Docs First:** Confirm API signatures, versions, and patterns in official vendor documentation rather than guessing.
3. **Agent Reach for Web Intel:** When external platform discussions, issue threads, or benchmarks are needed, invoke `agent-reach` to gather structured findings without API fees.
4. **Registry Verification:** Search package managers (npm, PyPI, crates.io) for battle-tested libraries before writing custom utilities.
### Stage 1: Plan First
1. Never jump straight into code without a concrete sequence of implementation.
2. Produce structured architecture plans: PRD, technical design, edge-case analysis, and task checklist.
3. Establish clear acceptance criteria for every phase.
### Stage 2: Test-Driven Development (TDD)
1. **RED:** Write failing unit, integration, or E2E tests first. Observe the test fail to verify that it tests the right assertion.
2. **GREEN:** Write the minimal implementation required to make the tests pass.
3. **REFACTOR:** Clean up code, remove duplication, and improve performance while keeping tests green.
4. Target 80%+ test coverage across core business logic.
### Stage 3: Autonomous Code Review
Run immediate diff-level reviews before committing:
- **Null safety & edge cases:** Defend against unexpected nulls, undefined values, and unhandled exceptions.
- **Concurrency & Race Conditions:** Ensure thread safety, mutex discipline, and atomic state transitions.
- **Dependency & Regression Pitfalls:** Ensure existing features remain unbroken.
### Stage 4: Pre-Commit Security & Zero-Secret Audit
- **Strict Zero-Secret Law:** Under NO circumstances should ANY secret, private key, JWT, or credential be committed:
```bash
git diff --cached
```
- Ensure `.env`, `.env.local`, credentials, and tokens are strictly excluded in `.gitignore`.
- Sanitize git remote URLs (never embed access tokens).
### Stage 5: Verification Before Completion
- **Evidence Before Assertions:** Never claim a task is complete or fixed without running verification commands and checking exit codes.
- Run the full test suite, build process, and linter.
---
## 🔄 ECC Orchestration Workflows (`orch-*`)
| Workflow | Use Case | Execution Sequence |
| :--- | :--- | :--- |
| **`orch-add-feature`** | Brand new capability | Research & Reuse → Implementation Plan → TDD → Code Review → Verification → Gated Commit |
| **`orch-change-feature`**| Altering existing behavior | Spec Update → Update Tests to New Behavior → Code Adjustment → Verify Green → Review |
| **`orch-fix-defect`** | Bug or defect fix | Reproduce as Failing Regression Test → Root Cause Tracing → Fix to Green → Verification |
| **`orch-refine-code`** | Refactoring | Verify Green Baseline → Refactor Structure Without Changing Behavior → Verify Still Green |
---
## 🤝 Pairing ECC with REA & Agent Reach
When performing reverse engineering, vulnerability assessments, or app security with **REA**:
1. **Systematic Investigation:** Use ECC's `systematic-debugging` methodology to trace root causes in disassembled code rather than making speculative edits.
2. **Defensive Hardening via TDD:** When fixing a security vulnerability discovered by REA or the `website-security-audit`, write an automated test reproducing the vulnerable payload first, apply the remediation, and verify the test passes.
3. **Live Intelligence via Agent Reach:** Use Agent Reach to pull CVE bulletins, patch notes, and GitHub advisory threads directly into the ECC research phase.
---
## 🛠️ Official ECC Setup & Tools
Install ECC tools and universal configurations:
```bash
# ECC Universal NPM package
npm install -g ecc-universal
# ECC Security & AgentShield
npm install -g ecc-agentshield
```
Official Repository: [https://github.com/affaan-m/everything-claude-code](https://github.com/affaan-m/everything-claude-code)
Website: [https://ecc.tools](https://ecc.tools)
Pliki w paczce (2)
- SKILL.md 5 KB
- agents/openai.yaml 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · smartworldarafath/REA_Skill | 100 | MIT |
| eliozh/ecc-workflow | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 54a9b7d247aa (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100ecc
Instaluje i konfiguruje ECC (Everything Claude Code), otwartoźródłowy zestaw agentów, skilli, komend, reguł, hooków i wspólnej pamięci dla Claude Code i Codex, ze skanem konfiguracji AgentShield. - 100ecc
Instaluje, konfiguruje, weryfikuje, aktualizuje i naprawia ECC, czyli agentowy harness z wtyczkami Claude Code i Codex. - 95workflow-tdd
Prowadzi tworzenie funkcji i naprawę błędów metodą test-first: czerwony test, zielona implementacja, potem refaktoryzacja. - 90ecc-harness-os
Instaluje i konfiguruje ECC jako system operacyjny dla agentów kodujących: plan, testy, wdrożenie, przegląd i wspólne umiejętności między narzędziami. - 100brownfield-retrospective
Uruchamia proces inżynierski ECC wstecz na istniejącym wycinku projektu: audytuje stan, odtwarza decyzje, tworzy rejestr luk w czterech osiach i wdraża poprawki przez potok plan, TDD i przegląd. - 100tdd-workflow
Wymusza TDD z pokryciem co najmniej 80 proc., w tym testy jednostkowe, integracyjne i E2E, przy nowych funkcjach, naprawie błędów i refaktoryzacji.