Repo & Fork Assessment + Setup Recommendations

Date: 2026-03-21

What's Available

Repo: Infiniteyieldai/everything-claude-code

This is a fork of affaan-m/everything-claude-code (the upstream project with 50K+ stars, 6K+ forks).

This is the right repo to work from. It's the latest upstream version with no divergence or merge conflicts.

Current ~/.claude/ Installation

The existing Stop hook (stop-hook-git-check.sh) is solid — blocks session end on uncommitted/unpushed work. Keep it.

Install Profile Recommendations

The repo ships 5 install profiles. Choose based on your primary use case:

Profile: core (Minimum viable setup)

Fastest to install. Gets you commands, core agents, hooks runtime, and quality workflow.

Best for: Trying ECC out, minimal footprint, or a constrained environment.

node scripts/install-plan.js --profile core
node scripts/install-apply.js

Installs: rules-core, agents-core, commands-core, hooks-runtime, platform-configs, workflow-quality

Profile: developer (Recommended for daily dev work)

The default engineering profile for most ECC users.

Best for: General software development across app codebases.

node scripts/install-plan.js --profile developer
node scripts/install-apply.js

Adds over core: framework-language skills, database patterns, orchestration commands

Profile: security

Baseline runtime + security-specific agents and rules.

Best for: Security-focused workflows, code audits, vulnerability reviews.

Profile: research

Investigation, synthesis, and publishing workflows.

Best for: Content creation, investor materials, market research, cross-posting.

Profile: full

Everything — all 18 modules.

Best for: Power users who want the complete toolkit.

node scripts/install-plan.js --profile full
node scripts/install-apply.js

Priority Additions (High Value, Low Risk)

Regardless of profile, these components add immediate value:

1. Core Agents (highest ROI)

2. Key Commands

3. Hook Upgrades (from hooks/hooks.json)

The repo's hook system adds these over the current single Stop hook:

4. Rules (Always-on guidelines)

The rules/common/ directory provides baseline guidelines that fire on every session:

• security.md — Security guardrails
• testing.md — 80%+ coverage requirement
• git-workflow.md — Conventional commits, branch strategy
• coding-style.md — Cross-language style standards

What to Do With the Fork

Option A: Use as upstream tracker (current state)

Keep the fork synced with affaan-m/everything-claude-code upstream. Periodically merge upstream changes:

git fetch upstream
git merge upstream/main

Install from the local clone. This is clean and maintainable.

Option B: Customize the fork

Add personal skills, agents, or commands to the fork. Good for:

• Business-specific domain skills (your vertical)
• Team-specific coding conventions
• Custom hooks for your stack

The fork already has the EVALUATION.md and REPO-ASSESSMENT.md docs — that's fine for a working fork.

Option C: Install from npm (simplest for fresh machines)

npx ecc-universal install --profile developer

No need to clone the repo. This is the recommended install method for most users.

Recommended Setup Steps

1. Keep the existing Stop hook — it's doing its job
2. Run the developer profile install from the local fork:
   bashCopy

   cd /path/to/everything-claude-code
   node scripts/install-plan.js --profile developer
   node scripts/install-apply.js
   

3. Add language rules for your primary stack (TypeScript, Python, Go, etc.):
   bashCopy

   node scripts/install-plan.js --add rules/typescript
   node scripts/install-apply.js
   

4. Enable MCP Context7 for live documentation lookup:
   • Copy mcp-configs/mcp-servers.json into your project's .claude/ dir
5. Review hooks — enable the hooks/hooks.json additions selectively, starting with block-no-verify and pre-bash-git-push-reminder

Summary