smartworldarafath/rea_skill

ecc-workflow

Everything Claude Code (ECC) engineering harness and multi-agent workflow system.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/smartworldarafath/rea_skill --skill ecc-workflow

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

ECC Workflow (Everything Claude Code Agent Harness)

The ultimate agent harness performance optimization system based on 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
  1. Library Docs First: Confirm API signatures, versions, and patterns in official vendor documentation rather than guessing.
  2. 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.
  3. 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-*)

WorkflowUse CaseExecution Sequence
`orch-add-feature`Brand new capabilityResearch & Reuse → Implementation Plan → TDD → Code Review → Verification → Gated Commit
`orch-change-feature`Altering existing behaviorSpec Update → Update Tests to New Behavior → Code Adjustment → Verify Green → Review
`orch-fix-defect`Bug or defect fixReproduce as Failing Regression Test → Root Cause Tracing → Fix to Green → Verification
`orch-refine-code`RefactoringVerify 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 Website: https://ecc.tools

같은 저장소의 Skills

더 많은 Skills

모든 Skills
smartworldarafath
커뮤니티

agent-introspection-debugging

Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.

1시간 설치 수
2
GitHub Stars
5
업데이트
11월 8일
smartworldarafath
커뮤니티

agent-reach

Read-only access to internet platforms (Twitter/X, Reddit, YouTube subtitles, GitHub, LinkedIn, Bilibili, web). Use when the agent needs to search, read web links, retrieve social discussions, CVE/vulnerability intel, or when standard web search/fetch is blocked or insufficient.

1시간 설치 수
2
GitHub Stars
5
업데이트
11월 8일
smartworldarafath
커뮤니티

agent-sort

Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.

1시간 설치 수
2
GitHub Stars
5
업데이트
11월 8일
smartworldarafath
커뮤니티

anti-ai-slop-writing

Produces human-sounding text that avoids detectable AI writing patterns. Activates on any writing task — tweets, emails, articles, bios, captions, reports, copy, messages, LinkedIn posts, cover letters, README files, or any content where the output must not read as AI-generated. Enforces banned vocabulary, structural variety, punctuation discipline, accuracy rules, and voice calibration. Use when the user says "write," "draft," "rewrite," "make this sound human," "anti-slop," "not AI," or any va

1시간 설치 수
2
GitHub Stars
5
업데이트
11월 8일