feat: add everything-claude-code-conventions ECC bundle (.claude/commands/add-or-update-skill.md)

.agents/skills/everything-claude-code/SKILL.md

@@ -1,165 +1,433 @@
-```markdown
-# everything-claude-code Development Patterns
+---
+name: everything-claude-code-conventions
+description: Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.
+---
 
-> Auto-generated skill from repository analysis
+# Everything Claude Code Conventions
+
+> Generated from [affaan-m/everything-claude-code](https://github.com/affaan-m/everything-claude-code) on 2026-04-02
 
 ## Overview
 
-This skill teaches the core development patterns, coding conventions, and collaborative workflows used in the `everything-claude-code` JavaScript repository. The project is modular, skill-oriented, and emphasizes clear documentation, conventional commits, and extensibility via skills, agents, commands, and install targets. This guide will help you contribute effectively by following established patterns and using the right commands for common tasks.
+This skill teaches Claude the development patterns and conventions used in everything-claude-code.
 
-## Coding Conventions
+## Tech Stack
 
-**File Naming**
-- Use `camelCase` for JavaScript files and directories.
-  - Example: `mySkill.js`, `installTarget.js`
+- **Primary Language**: JavaScript
+- **Architecture**: hybrid module organization
+- **Test Location**: separate
 
-**Import Style**
-- Use relative imports.
-  - Example:
-    ```js
-    const helper = require('./helper');
-    import { doSomething } from '../utils/doSomething';
-    ```
+## When to Use This Skill
 
-**Export Style**
-- Mixed: both CommonJS (`module.exports`) and ES6 (`export`) exports are used.
-  - Example (CommonJS):
-    ```js
-    module.exports = function myFunction() { ... };
-    ```
-  - Example (ES6):
-    ```js
-    export function myFunction() { ... }
-    ```
+Activate this skill when:
+- Making changes to this repository
+- Adding new features following established patterns
+- Writing tests that match project conventions
+- Creating commits with proper message format
 
-**Commit Messages**
-- Use [Conventional Commits](https://www.conventionalcommits.org/):
-  - Prefixes: `fix`, `feat`, `docs`, `chore`
-  - Example: `feat: add new agent pipeline for document processing`
+## Commit Conventions
 
-## Workflows
+Follow these commit message conventions based on 500 analyzed commits.
 
-### Add New Skill
-**Trigger:** When introducing a new skill (capability/module) to the platform  
-**Command:** `/add-skill`
+### Commit Style: Conventional Commits
 
-1. Create a new `SKILL.md` under `skills/<skill-name>/` or `.agents/skills/<skill-name>/`.
-2. Optionally add related assets or references in the skill directory.
-3. Update documentation:
-    - `AGENTS.md`
-    - `README.md`
-    - `README.zh-CN.md`
-    - `docs/zh-CN/AGENTS.md`
-4. If the skill is installable, update:
-    - `manifests/install-components.json` or
-    - `manifests/install-modules.json`
-5. Optionally update `WORKING-CONTEXT.md`.
+### Prefixes Used
 
-**Example directory structure:**
-```
-skills/
-  myNewSkill/
-    SKILL.md
-    index.js
-    assets/
+- `fix`
+- `feat`
+- `docs`
+- `chore`
+
+### Message Guidelines
+
+- Average message length: ~57 characters
+- Keep first line concise and descriptive
+- Use imperative mood ("Add feature" not "Added feature")
+
+
+*Commit message example*
+
+```text
+feat: add everything-claude-code-conventions ECC bundle (.claude/commands/add-or-update-skill.md)
 ```
 
----
+*Commit message example*
 
-### Add New Agent or Pipeline
-**Trigger:** When introducing a new agent or orchestrated workflow (pipeline)  
-**Command:** `/add-agent-pipeline`
-
-1. Create agent definition files under `agents/`.
-2. Create or update a `SKILL.md` for the orchestrator under `skills/<pipeline-name>/`.
-3. Update `AGENTS.md` and `README.md` to document the new agent(s)/pipeline.
-4. Optionally add supporting commands, scripts, or documentation.
-
----
-
-### Add or Extend Command
-**Trigger:** When adding or enhancing CLI commands  
-**Command:** `/add-command`
-
-1. Create or update command markdown files under `commands/`.
-2. Incorporate review feedback and fixes as needed.
-3. Document new commands in `AGENTS.md` or other relevant docs.
-
----
-
-### Add Install Target or Adapter
-**Trigger:** When supporting a new install target (plugin, IDE, platform)  
-**Command:** `/add-install-target`
-
-1. Create a new directory for the install target (e.g., `.codebuddy/`, `.gemini/`).
-2. Add install/uninstall scripts and documentation in the new directory.
-3. Update `manifests/install-modules.json` and relevant schemas.
-4. Update or add scripts in `scripts/lib/install-targets/<target>.js`.
-5. Update or add tests for the new install target.
-
-**Example:**
-```
-.codebuddy/
-  install.sh
-  uninstall.sh
-  README.md
-scripts/lib/install-targets/codebuddy.js
-tests/lib/install-targets.test.js
+```text
+fix: port safe ci cleanup from backlog
 ```
 
----
+*Commit message example*
 
-### Update or Harden Hooks
-**Trigger:** When improving, refactoring, or fixing hooks (e.g., CI, formatting, session management)  
-**Command:** `/update-hook`
-
-1. Update `hooks/hooks.json` to change hook configuration.
-2. Update or add scripts in `scripts/hooks/*.js` or `scripts/hooks/*.sh`.
-3. Update or add tests for the affected hooks.
-4. Optionally update related documentation.
-
----
-
-### Documentation Sync and Guidance Update
-**Trigger:** When updating documentation to reflect new features, skills, or workflows  
-**Command:** `/sync-docs`
-
-1. Update `README.md`, `README.zh-CN.md`, and/or `AGENTS.md`.
-2. Update `docs/zh-CN/AGENTS.md` and `docs/zh-CN/README.md`.
-3. Update or add `WORKING-CONTEXT.md`.
-4. Optionally update `the-shortform-guide.md` or other guidance files.
-
----
-
-### Dependency Bump via Dependabot
-**Trigger:** When a dependency update is triggered by Dependabot or similar automation  
-**Command:** `/bump-dependency`
-
-1. Update `package.json` and/or `yarn.lock` for npm dependencies.
-2. Update `.github/workflows/*.yml` for GitHub Actions dependencies.
-3. Commit with a standardized message and co-author.
-
----
-
-## Testing Patterns
-
-- Test files use the pattern `*.test.js`.
-- Testing framework is not explicitly specified; check test files for usage.
-- Place tests alongside or within a `tests/` directory, matching the structure of the code under test.
-- Example test file:
-  ```
-  tests/lib/install-targets.test.js
-  ```
-
-## Commands
-
-| Command            | Purpose                                                          |
-|--------------------|------------------------------------------------------------------|
-| /add-skill         | Add a new skill, including docs and registration                 |
-| /add-agent-pipeline| Add a new agent or orchestrated pipeline                         |
-| /add-command       | Add or extend a CLI command                                      |
-| /add-install-target| Add support for a new install target or adapter                  |
-| /update-hook       | Refactor or fix hooks and related scripts                        |
-| /sync-docs         | Synchronize and update documentation across contexts/languages    |
-| /bump-dependency   | Automated dependency update via Dependabot or similar automation  |
+```text
+refactor: collapse legacy command bodies into skills
 ```
+
+*Commit message example*
+
+```text
+docs: close bundle drift and sync plugin guidance
+```
+
+*Commit message example*
+
+```text
+chore: ignore local orchestration artifacts
+```
+
+*Commit message example*
+
+```text
+feat: add everything-claude-code-conventions ECC bundle (.claude/commands/refactoring.md)
+```
+
+*Commit message example*
+
+```text
+feat: add everything-claude-code-conventions ECC bundle (.claude/commands/feature-development.md)
+```
+
+*Commit message example*
+
+```text
+feat: add everything-claude-code-conventions ECC bundle (.claude/enterprise/controls.md)
+```
+
+## Architecture
+
+### Project Structure: Single Package
+
+This project uses **hybrid** module organization.
+
+### Configuration Files
+
+- `.github/workflows/ci.yml`
+- `.github/workflows/maintenance.yml`
+- `.github/workflows/monthly-metrics.yml`
+- `.github/workflows/release.yml`
+- `.github/workflows/reusable-release.yml`
+- `.github/workflows/reusable-test.yml`
+- `.github/workflows/reusable-validate.yml`
+- `.opencode/package.json`
+- `.opencode/tsconfig.json`
+- `.prettierrc`
+- `eslint.config.js`
+- `package.json`
+
+### Guidelines
+
+- This project uses a hybrid organization
+- Follow existing patterns when adding new code
+
+## Code Style
+
+### Language: JavaScript
+
+### Naming Conventions
+
+| Element | Convention |
+|---------|------------|
+| Files | camelCase |
+| Functions | camelCase |
+| Classes | PascalCase |
+| Constants | SCREAMING_SNAKE_CASE |
+
+### Import Style: Relative Imports
+
+### Export Style: Mixed Style
+
+
+*Preferred import style*
+
+```typescript
+// Use relative imports
+import { Button } from '../components/Button'
+import { useAuth } from './hooks/useAuth'
+```
+
+## Testing
+
+### Test Framework
+
+No specific test framework detected — use the repository's existing test patterns.
+
+### File Pattern: `*.test.js`
+
+### Test Types
+
+- **Unit tests**: Test individual functions and components in isolation
+- **Integration tests**: Test interactions between multiple components/services
+
+### Coverage
+
+This project has coverage reporting configured. Aim for 80%+ coverage.
+
+
+## Error Handling
+
+### Error Handling Style: Try-Catch Blocks
+
+
+*Standard error handling pattern*
+
+```typescript
+try {
+  const result = await riskyOperation()
+  return result
+} catch (error) {
+  console.error('Operation failed:', error)
+  throw new Error('User-friendly message')
+}
+```
+
+## Common Workflows
+
+These workflows were detected from analyzing commit patterns.
+
+### Feature Development
+
+Standard feature implementation workflow
+
+**Frequency**: ~19 times per month
+
+**Steps**:
+1. Add feature implementation
+2. Add tests for feature
+3. Update documentation
+
+**Files typically involved**:
+- `.opencode/*`
+- `.opencode/plugins/*`
+- `.opencode/plugins/lib/*`
+- `**/*.test.*`
+- `**/api/**`
+
+**Example commit sequence**:
+```
+feat(agents,skills): add opensource-pipeline — 3-agent workflow for safe public releases (#1036)
+feat(install): add CodeBuddy(Tencent) adaptation with installation scripts (#1038)
+chore(deps-dev): bump c8 from 10.1.3 to 11.0.0 (#1065)
+```
+
+### Refactoring
+
+Code refactoring and cleanup workflow
+
+**Frequency**: ~3 times per month
+
+**Steps**:
+1. Ensure tests pass before refactor
+2. Refactor code structure
+3. Verify tests still pass
+
+**Files typically involved**:
+- `src/**/*`
+
+**Example commit sequence**:
+```
+refactor: collapse legacy command bodies into skills
+feat: add connected operator workflow skills
+feat: expand lead intelligence outreach channels
+```
+
+### Add Or Update Skill
+
+Adds or updates a skill module, including documentation and references, and registers it in manifests and documentation.
+
+**Frequency**: ~4 times per month
+
+**Steps**:
+1. Create or update SKILL.md in skills/<skill-name>/ or .agents/skills/<skill-name>/
+2. Optionally add or update references or assets under skills/<skill-name>/references/ or assets/
+3. Update manifests/install-modules.json and/or manifests/install-components.json
+4. Update AGENTS.md, README.md, README.zh-CN.md, and docs/zh-CN/* as needed
+5. Update WORKING-CONTEXT.md if context changes
+6. Optionally update or create related test files
+
+**Files typically involved**:
+- `skills/*/SKILL.md`
+- `.agents/skills/*/SKILL.md`
+- `skills/*/references/*.md`
+- `skills/*/assets/*`
+- `manifests/install-modules.json`
+- `manifests/install-components.json`
+- `AGENTS.md`
+- `README.md`
+- `README.zh-CN.md`
+- `docs/zh-CN/AGENTS.md`
+- `docs/zh-CN/README.md`
+- `WORKING-CONTEXT.md`
+
+**Example commit sequence**:
+```
+Create or update SKILL.md in skills/<skill-name>/ or .agents/skills/<skill-name>/
+Optionally add or update references or assets under skills/<skill-name>/references/ or assets/
+Update manifests/install-modules.json and/or manifests/install-components.json
+Update AGENTS.md, README.md, README.zh-CN.md, and docs/zh-CN/* as needed
+Update WORKING-CONTEXT.md if context changes
+Optionally update or create related test files
+```
+
+### Add Or Update Command Workflow
+
+Adds or updates command documentation and workflow scripts for agentic or PRP workflows.
+
+**Frequency**: ~2 times per month
+
+**Steps**:
+1. Create or update command markdown files under commands/ (e.g., prp-prd.md, code-review.md)
+2. If extending, update related commands (e.g., plan.md cross-references prp-plan.md)
+3. Address review feedback and iterate on command logic and documentation
+
+**Files typically involved**:
+- `commands/*.md`
+
+**Example commit sequence**:
+```
+Create or update command markdown files under commands/ (e.g., prp-prd.md, code-review.md)
+If extending, update related commands (e.g., plan.md cross-references prp-plan.md)
+Address review feedback and iterate on command logic and documentation
+```
+
+### Add Or Update Agent Or Agent Prompt
+
+Adds or updates agent configuration, prompt files, and registers agents in orchestration manifests.
+
+**Frequency**: ~2 times per month
+
+**Steps**:
+1. Create or update agent prompt files under .opencode/prompts/agents/
+2. Update .opencode/opencode.json to register or modify agent configuration
+3. Update AGENTS.md to document the new or updated agent
+
+**Files typically involved**:
+- `.opencode/prompts/agents/*.txt`
+- `.opencode/opencode.json`
+- `AGENTS.md`
+
+**Example commit sequence**:
+```
+Create or update agent prompt files under .opencode/prompts/agents/
+Update .opencode/opencode.json to register or modify agent configuration
+Update AGENTS.md to document the new or updated agent
+```
+
+### Feature Development Skill And Docs
+
+Implements a new feature or workflow by adding skills, updating documentation, and synchronizing manifests and context.
+
+**Frequency**: ~3 times per month
+
+**Steps**:
+1. Add or update SKILL.md and related files in skills/ or .agents/skills/
+2. Update or create supporting documentation (README.md, AGENTS.md, docs/zh-CN/*, WORKING-CONTEXT.md)
+3. Update manifests/install-modules.json and/or manifests/install-components.json
+4. Synchronize or update related scripts or test files
+
+**Files typically involved**:
+- `skills/*/SKILL.md`
+- `.agents/skills/*/SKILL.md`
+- `AGENTS.md`
+- `README.md`
+- `README.zh-CN.md`
+- `docs/zh-CN/AGENTS.md`
+- `docs/zh-CN/README.md`
+- `WORKING-CONTEXT.md`
+- `manifests/install-modules.json`
+- `manifests/install-components.json`
+
+**Example commit sequence**:
+```
+Add or update SKILL.md and related files in skills/ or .agents/skills/
+Update or create supporting documentation (README.md, AGENTS.md, docs/zh-CN/*, WORKING-CONTEXT.md)
+Update manifests/install-modules.json and/or manifests/install-components.json
+Synchronize or update related scripts or test files
+```
+
+### Refactor Or Sync Manifests And Context
+
+Refactors commands, skills, or agents and synchronizes manifests and working context documentation.
+
+**Frequency**: ~2 times per month
+
+**Steps**:
+1. Update or remove command files under commands/
+2. Update or create SKILL.md files as needed
+3. Update manifests/install-modules.json and/or install-components.json
+4. Update AGENTS.md, README.md, README.zh-CN.md, docs/zh-CN/*, WORKING-CONTEXT.md
+
+**Files typically involved**:
+- `commands/*.md`
+- `skills/*/SKILL.md`
+- `manifests/install-modules.json`
+- `manifests/install-components.json`
+- `AGENTS.md`
+- `README.md`
+- `README.zh-CN.md`
+- `docs/zh-CN/AGENTS.md`
+- `docs/zh-CN/README.md`
+- `WORKING-CONTEXT.md`
+
+**Example commit sequence**:
+```
+Update or remove command files under commands/
+Update or create SKILL.md files as needed
+Update manifests/install-modules.json and/or install-components.json
+Update AGENTS.md, README.md, README.zh-CN.md, docs/zh-CN/*, WORKING-CONTEXT.md
+```
+
+### Add Or Update Install Target
+
+Adds or updates an install target (e.g., CodeBuddy, Gemini) with scripts, schemas, and manifest registration.
+
+**Frequency**: ~2 times per month
+
+**Steps**:
+1. Add or update install/uninstall scripts under .<target>/
+2. Update or create README files for the target
+3. Update schemas (ecc-install-config.schema.json, install-modules.schema.json)
+4. Update scripts/lib/install-targets/<target>-project.js and registry.js
+5. Update manifests/install-modules.json
+6. Update or add related test files
+
+**Files typically involved**:
+- `.<target>/*`
+- `manifests/install-modules.json`
+- `schemas/ecc-install-config.schema.json`
+- `schemas/install-modules.schema.json`
+- `scripts/lib/install-manifests.js`
+- `scripts/lib/install-targets/<target>-project.js`
+- `scripts/lib/install-targets/registry.js`
+- `tests/lib/install-targets.test.js`
+
+**Example commit sequence**:
+```
+Add or update install/uninstall scripts under .<target>/
+Update or create README files for the target
+Update schemas (ecc-install-config.schema.json, install-modules.schema.json)
+Update scripts/lib/install-targets/<target>-project.js and registry.js
+Update manifests/install-modules.json
+Update or add related test files
+```
+
+
+## Best Practices
+
+Based on analysis of the codebase, follow these practices:
+
+### Do
+
+- Use conventional commit format (feat:, fix:, etc.)
+- Follow *.test.js naming pattern
+- Use camelCase for file names
+- Prefer mixed exports
+
+### Don't
+
+- Don't write vague commit messages
+- Don't skip tests for new features
+- Don't deviate from established patterns without discussion
+
+---
+
+*This skill was auto-generated by [ECC Tools](https://ecc.tools). Review and customize as needed for your team.*

.claude/commands/add-new-skill.md

@@ -1,42 +0,0 @@
----
-name: add-new-skill
-description: Workflow command scaffold for add-new-skill in everything-claude-code.
-allowed_tools: ["Bash", "Read", "Write", "Grep", "Glob"]
----
-
-# /add-new-skill
-
-Use this workflow when working on **add-new-skill** in `everything-claude-code`.
-
-## Goal
-
-Adds a new skill to the system, including documentation and registration in relevant indexes.
-
-## Common Files
-
-- `skills/*/SKILL.md`
-- `.agents/skills/*/SKILL.md`
-- `AGENTS.md`
-- `README.md`
-- `README.zh-CN.md`
-- `docs/zh-CN/AGENTS.md`
-
-## Suggested Sequence
-
-1. Understand the current state and failure mode before editing.
-2. Make the smallest coherent change that satisfies the workflow goal.
-3. Run the most relevant verification for touched files.
-4. Summarize what changed and what still needs review.
-
-## Typical Commit Signals
-
-- Create a new SKILL.md file under skills/<skill-name>/ or .agents/skills/<skill-name>/
-- Optionally add related assets or references under the skill directory
-- Update AGENTS.md, README.md, README.zh-CN.md, and docs/zh-CN/AGENTS.md to document the new skill
-- Update manifests/install-components.json or manifests/install-modules.json if the skill is installable
-- Optionally update WORKING-CONTEXT.md
-
-## Notes
-
-- Treat this as a scaffold, not a hard-coded script.
-- Update the command if the workflow evolves materially.

.claude/commands/add-or-update-skill.md

@@ -0,0 +1,42 @@
+---
+name: add-or-update-skill
+description: Workflow command scaffold for add-or-update-skill in everything-claude-code.
+allowed_tools: ["Bash", "Read", "Write", "Grep", "Glob"]
+---
+
+# /add-or-update-skill
+
+Use this workflow when working on **add-or-update-skill** in `everything-claude-code`.
+
+## Goal
+
+Adds or updates a skill module, including documentation and references, and registers it in manifests and documentation.
+
+## Common Files
+
+- `skills/*/SKILL.md`
+- `.agents/skills/*/SKILL.md`
+- `skills/*/references/*.md`
+- `skills/*/assets/*`
+- `manifests/install-modules.json`
+- `manifests/install-components.json`
+
+## Suggested Sequence
+
+1. Understand the current state and failure mode before editing.
+2. Make the smallest coherent change that satisfies the workflow goal.
+3. Run the most relevant verification for touched files.
+4. Summarize what changed and what still needs review.
+
+## Typical Commit Signals
+
+- Create or update SKILL.md in skills/<skill-name>/ or .agents/skills/<skill-name>/
+- Optionally add or update references or assets under skills/<skill-name>/references/ or assets/
+- Update manifests/install-modules.json and/or manifests/install-components.json
+- Update AGENTS.md, README.md, README.zh-CN.md, and docs/zh-CN/* as needed
+- Update WORKING-CONTEXT.md if context changes
+
+## Notes
+
+- Treat this as a scaffold, not a hard-coded script.
+- Update the command if the workflow evolves materially.

.claude/ecc-tools.json

@@ -2,7 +2,7 @@
   "version": "1.3",
   "schemaVersion": "1.0",
   "generatedBy": "ecc-tools",
-  "generatedAt": "2026-04-02T03:20:48.238Z",
+  "generatedAt": "2026-04-02T03:14:01.196Z",
   "repo": "https://github.com/affaan-m/everything-claude-code",
   "profiles": {
     "requested": "full",
@@ -150,7 +150,7 @@
     ".claude/enterprise/controls.md",
     ".claude/commands/feature-development.md",
     ".claude/commands/refactoring.md",
-    ".claude/commands/add-new-skill.md"
+    ".claude/commands/add-or-update-skill.md"
   ],
   "packageFiles": {
     "runtime-core": [
@@ -180,7 +180,7 @@
     "workflow-pack": [
       ".claude/commands/feature-development.md",
       ".claude/commands/refactoring.md",
-      ".claude/commands/add-new-skill.md"
+      ".claude/commands/add-or-update-skill.md"
     ]
   },
   "moduleFiles": {
@@ -211,7 +211,7 @@
     "workflow-pack": [
       ".claude/commands/feature-development.md",
       ".claude/commands/refactoring.md",
-      ".claude/commands/add-new-skill.md"
+      ".claude/commands/add-or-update-skill.md"
     ]
   },
   "files": [
@@ -297,8 +297,8 @@
     },
     {
       "moduleId": "workflow-pack",
-      "path": ".claude/commands/add-new-skill.md",
-      "description": "Workflow command scaffold for add-new-skill."
+      "path": ".claude/commands/add-or-update-skill.md",
+      "description": "Workflow command scaffold for add-or-update-skill."
     }
   ],
   "workflows": [
@@ -311,8 +311,8 @@
       "path": ".claude/commands/refactoring.md"
     },
     {
-      "command": "add-new-skill",
-      "path": ".claude/commands/add-new-skill.md"
+      "command": "add-or-update-skill",
+      "path": ".claude/commands/add-or-update-skill.md"
     }
   ],
   "adapters": {
@@ -322,7 +322,7 @@
       "commandPaths": [
         ".claude/commands/feature-development.md",
         ".claude/commands/refactoring.md",
-        ".claude/commands/add-new-skill.md"
+        ".claude/commands/add-or-update-skill.md"
       ]
     },
     "codex": {

.claude/identity.json

@@ -10,5 +10,5 @@
     "javascript"
   ],
   "suggestedBy": "ecc-tools-repo-analysis",
-  "createdAt": "2026-04-02T03:21:37.492Z"
+  "createdAt": "2026-04-02T03:20:17.389Z"
 }

.claude/research/everything-claude-code-research-playbook.md

@@ -18,4 +18,4 @@ Use this when the task is documentation-heavy, source-sensitive, or requires bro
 
 - Primary language: JavaScript
 - Framework: Not detected
-- Workflows detected: 9
+- Workflows detected: 8

.claude/rules/everything-claude-code-guardrails.md

@@ -26,7 +26,7 @@ Generated by ECC Tools from repository history. Review before treating it as a h
 
 - feature-development: Standard feature implementation workflow
 - refactoring: Code refactoring and cleanup workflow
-- add-new-skill: Adds a new skill to the system, including documentation and registration in relevant indexes.
+- add-or-update-skill: Adds or updates a skill module, including documentation and references, and registers it in manifests and documentation.
 
 ## Review Reminder
 

.claude/skills/everything-claude-code/SKILL.md

@@ -1,165 +1,433 @@
-```markdown
-# everything-claude-code Development Patterns
+---
+name: everything-claude-code-conventions
+description: Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.
+---
 
-> Auto-generated skill from repository analysis
+# Everything Claude Code Conventions
+
+> Generated from [affaan-m/everything-claude-code](https://github.com/affaan-m/everything-claude-code) on 2026-04-02
 
 ## Overview
 
-This skill teaches the core development patterns, coding conventions, and collaborative workflows used in the `everything-claude-code` JavaScript repository. The project is modular, skill-oriented, and emphasizes clear documentation, conventional commits, and extensibility via skills, agents, commands, and install targets. This guide will help you contribute effectively by following established patterns and using the right commands for common tasks.
+This skill teaches Claude the development patterns and conventions used in everything-claude-code.
 
-## Coding Conventions
+## Tech Stack
 
-**File Naming**
-- Use `camelCase` for JavaScript files and directories.
-  - Example: `mySkill.js`, `installTarget.js`
+- **Primary Language**: JavaScript
+- **Architecture**: hybrid module organization
+- **Test Location**: separate
 
-**Import Style**
-- Use relative imports.
-  - Example:
-    ```js
-    const helper = require('./helper');
-    import { doSomething } from '../utils/doSomething';
-    ```
+## When to Use This Skill
 
-**Export Style**
-- Mixed: both CommonJS (`module.exports`) and ES6 (`export`) exports are used.
-  - Example (CommonJS):
-    ```js
-    module.exports = function myFunction() { ... };
-    ```
-  - Example (ES6):
-    ```js
-    export function myFunction() { ... }
-    ```
+Activate this skill when:
+- Making changes to this repository
+- Adding new features following established patterns
+- Writing tests that match project conventions
+- Creating commits with proper message format
 
-**Commit Messages**
-- Use [Conventional Commits](https://www.conventionalcommits.org/):
-  - Prefixes: `fix`, `feat`, `docs`, `chore`
-  - Example: `feat: add new agent pipeline for document processing`
+## Commit Conventions
 
-## Workflows
+Follow these commit message conventions based on 500 analyzed commits.
 
-### Add New Skill
-**Trigger:** When introducing a new skill (capability/module) to the platform  
-**Command:** `/add-skill`
+### Commit Style: Conventional Commits
 
-1. Create a new `SKILL.md` under `skills/<skill-name>/` or `.agents/skills/<skill-name>/`.
-2. Optionally add related assets or references in the skill directory.
-3. Update documentation:
-    - `AGENTS.md`
-    - `README.md`
-    - `README.zh-CN.md`
-    - `docs/zh-CN/AGENTS.md`
-4. If the skill is installable, update:
-    - `manifests/install-components.json` or
-    - `manifests/install-modules.json`
-5. Optionally update `WORKING-CONTEXT.md`.
+### Prefixes Used
 
-**Example directory structure:**
-```
-skills/
-  myNewSkill/
-    SKILL.md
-    index.js
-    assets/
+- `fix`
+- `feat`
+- `docs`
+- `chore`
+
+### Message Guidelines
+
+- Average message length: ~57 characters
+- Keep first line concise and descriptive
+- Use imperative mood ("Add feature" not "Added feature")
+
+
+*Commit message example*
+
+```text
+feat: add everything-claude-code-conventions ECC bundle (.claude/commands/add-or-update-skill.md)
 ```
 
----
+*Commit message example*
 
-### Add New Agent or Pipeline
-**Trigger:** When introducing a new agent or orchestrated workflow (pipeline)  
-**Command:** `/add-agent-pipeline`
-
-1. Create agent definition files under `agents/`.
-2. Create or update a `SKILL.md` for the orchestrator under `skills/<pipeline-name>/`.
-3. Update `AGENTS.md` and `README.md` to document the new agent(s)/pipeline.
-4. Optionally add supporting commands, scripts, or documentation.
-
----
-
-### Add or Extend Command
-**Trigger:** When adding or enhancing CLI commands  
-**Command:** `/add-command`
-
-1. Create or update command markdown files under `commands/`.
-2. Incorporate review feedback and fixes as needed.
-3. Document new commands in `AGENTS.md` or other relevant docs.
-
----
-
-### Add Install Target or Adapter
-**Trigger:** When supporting a new install target (plugin, IDE, platform)  
-**Command:** `/add-install-target`
-
-1. Create a new directory for the install target (e.g., `.codebuddy/`, `.gemini/`).
-2. Add install/uninstall scripts and documentation in the new directory.
-3. Update `manifests/install-modules.json` and relevant schemas.
-4. Update or add scripts in `scripts/lib/install-targets/<target>.js`.
-5. Update or add tests for the new install target.
-
-**Example:**
-```
-.codebuddy/
-  install.sh
-  uninstall.sh
-  README.md
-scripts/lib/install-targets/codebuddy.js
-tests/lib/install-targets.test.js
+```text
+fix: port safe ci cleanup from backlog
 ```
 
----
+*Commit message example*
 
-### Update or Harden Hooks
-**Trigger:** When improving, refactoring, or fixing hooks (e.g., CI, formatting, session management)  
-**Command:** `/update-hook`
-
-1. Update `hooks/hooks.json` to change hook configuration.
-2. Update or add scripts in `scripts/hooks/*.js` or `scripts/hooks/*.sh`.
-3. Update or add tests for the affected hooks.
-4. Optionally update related documentation.
-
----
-
-### Documentation Sync and Guidance Update
-**Trigger:** When updating documentation to reflect new features, skills, or workflows  
-**Command:** `/sync-docs`
-
-1. Update `README.md`, `README.zh-CN.md`, and/or `AGENTS.md`.
-2. Update `docs/zh-CN/AGENTS.md` and `docs/zh-CN/README.md`.
-3. Update or add `WORKING-CONTEXT.md`.
-4. Optionally update `the-shortform-guide.md` or other guidance files.
-
----
-
-### Dependency Bump via Dependabot
-**Trigger:** When a dependency update is triggered by Dependabot or similar automation  
-**Command:** `/bump-dependency`
-
-1. Update `package.json` and/or `yarn.lock` for npm dependencies.
-2. Update `.github/workflows/*.yml` for GitHub Actions dependencies.
-3. Commit with a standardized message and co-author.
-
----
-
-## Testing Patterns
-
-- Test files use the pattern `*.test.js`.
-- Testing framework is not explicitly specified; check test files for usage.
-- Place tests alongside or within a `tests/` directory, matching the structure of the code under test.
-- Example test file:
-  ```
-  tests/lib/install-targets.test.js
-  ```
-
-## Commands
-
-| Command            | Purpose                                                          |
-|--------------------|------------------------------------------------------------------|
-| /add-skill         | Add a new skill, including docs and registration                 |
-| /add-agent-pipeline| Add a new agent or orchestrated pipeline                         |
-| /add-command       | Add or extend a CLI command                                      |
-| /add-install-target| Add support for a new install target or adapter                  |
-| /update-hook       | Refactor or fix hooks and related scripts                        |
-| /sync-docs         | Synchronize and update documentation across contexts/languages    |
-| /bump-dependency   | Automated dependency update via Dependabot or similar automation  |
+```text
+refactor: collapse legacy command bodies into skills
 ```
+
+*Commit message example*
+
+```text
+docs: close bundle drift and sync plugin guidance
+```
+
+*Commit message example*
+
+```text
+chore: ignore local orchestration artifacts
+```
+
+*Commit message example*
+
+```text
+feat: add everything-claude-code-conventions ECC bundle (.claude/commands/refactoring.md)
+```
+
+*Commit message example*
+
+```text
+feat: add everything-claude-code-conventions ECC bundle (.claude/commands/feature-development.md)
+```
+
+*Commit message example*
+
+```text
+feat: add everything-claude-code-conventions ECC bundle (.claude/enterprise/controls.md)
+```
+
+## Architecture
+
+### Project Structure: Single Package
+
+This project uses **hybrid** module organization.
+
+### Configuration Files
+
+- `.github/workflows/ci.yml`
+- `.github/workflows/maintenance.yml`
+- `.github/workflows/monthly-metrics.yml`
+- `.github/workflows/release.yml`
+- `.github/workflows/reusable-release.yml`
+- `.github/workflows/reusable-test.yml`
+- `.github/workflows/reusable-validate.yml`
+- `.opencode/package.json`
+- `.opencode/tsconfig.json`
+- `.prettierrc`
+- `eslint.config.js`
+- `package.json`
+
+### Guidelines
+
+- This project uses a hybrid organization
+- Follow existing patterns when adding new code
+
+## Code Style
+
+### Language: JavaScript
+
+### Naming Conventions
+
+| Element | Convention |
+|---------|------------|
+| Files | camelCase |
+| Functions | camelCase |
+| Classes | PascalCase |
+| Constants | SCREAMING_SNAKE_CASE |
+
+### Import Style: Relative Imports
+
+### Export Style: Mixed Style
+
+
+*Preferred import style*
+
+```typescript
+// Use relative imports
+import { Button } from '../components/Button'
+import { useAuth } from './hooks/useAuth'
+```
+
+## Testing
+
+### Test Framework
+
+No specific test framework detected — use the repository's existing test patterns.
+
+### File Pattern: `*.test.js`
+
+### Test Types
+
+- **Unit tests**: Test individual functions and components in isolation
+- **Integration tests**: Test interactions between multiple components/services
+
+### Coverage
+
+This project has coverage reporting configured. Aim for 80%+ coverage.
+
+
+## Error Handling
+
+### Error Handling Style: Try-Catch Blocks
+
+
+*Standard error handling pattern*
+
+```typescript
+try {
+  const result = await riskyOperation()
+  return result
+} catch (error) {
+  console.error('Operation failed:', error)
+  throw new Error('User-friendly message')
+}
+```
+
+## Common Workflows
+
+These workflows were detected from analyzing commit patterns.
+
+### Feature Development
+
+Standard feature implementation workflow
+
+**Frequency**: ~19 times per month
+
+**Steps**:
+1. Add feature implementation
+2. Add tests for feature
+3. Update documentation
+
+**Files typically involved**:
+- `.opencode/*`
+- `.opencode/plugins/*`
+- `.opencode/plugins/lib/*`
+- `**/*.test.*`
+- `**/api/**`
+
+**Example commit sequence**:
+```
+feat(agents,skills): add opensource-pipeline — 3-agent workflow for safe public releases (#1036)
+feat(install): add CodeBuddy(Tencent) adaptation with installation scripts (#1038)
+chore(deps-dev): bump c8 from 10.1.3 to 11.0.0 (#1065)
+```
+
+### Refactoring
+
+Code refactoring and cleanup workflow
+
+**Frequency**: ~3 times per month
+
+**Steps**:
+1. Ensure tests pass before refactor
+2. Refactor code structure
+3. Verify tests still pass
+
+**Files typically involved**:
+- `src/**/*`
+
+**Example commit sequence**:
+```
+refactor: collapse legacy command bodies into skills
+feat: add connected operator workflow skills
+feat: expand lead intelligence outreach channels
+```
+
+### Add Or Update Skill
+
+Adds or updates a skill module, including documentation and references, and registers it in manifests and documentation.
+
+**Frequency**: ~4 times per month
+
+**Steps**:
+1. Create or update SKILL.md in skills/<skill-name>/ or .agents/skills/<skill-name>/
+2. Optionally add or update references or assets under skills/<skill-name>/references/ or assets/
+3. Update manifests/install-modules.json and/or manifests/install-components.json
+4. Update AGENTS.md, README.md, README.zh-CN.md, and docs/zh-CN/* as needed
+5. Update WORKING-CONTEXT.md if context changes
+6. Optionally update or create related test files
+
+**Files typically involved**:
+- `skills/*/SKILL.md`
+- `.agents/skills/*/SKILL.md`
+- `skills/*/references/*.md`
+- `skills/*/assets/*`
+- `manifests/install-modules.json`
+- `manifests/install-components.json`
+- `AGENTS.md`
+- `README.md`
+- `README.zh-CN.md`
+- `docs/zh-CN/AGENTS.md`
+- `docs/zh-CN/README.md`
+- `WORKING-CONTEXT.md`
+
+**Example commit sequence**:
+```
+Create or update SKILL.md in skills/<skill-name>/ or .agents/skills/<skill-name>/
+Optionally add or update references or assets under skills/<skill-name>/references/ or assets/
+Update manifests/install-modules.json and/or manifests/install-components.json
+Update AGENTS.md, README.md, README.zh-CN.md, and docs/zh-CN/* as needed
+Update WORKING-CONTEXT.md if context changes
+Optionally update or create related test files
+```
+
+### Add Or Update Command Workflow
+
+Adds or updates command documentation and workflow scripts for agentic or PRP workflows.
+
+**Frequency**: ~2 times per month
+
+**Steps**:
+1. Create or update command markdown files under commands/ (e.g., prp-prd.md, code-review.md)
+2. If extending, update related commands (e.g., plan.md cross-references prp-plan.md)
+3. Address review feedback and iterate on command logic and documentation
+
+**Files typically involved**:
+- `commands/*.md`
+
+**Example commit sequence**:
+```
+Create or update command markdown files under commands/ (e.g., prp-prd.md, code-review.md)
+If extending, update related commands (e.g., plan.md cross-references prp-plan.md)
+Address review feedback and iterate on command logic and documentation
+```
+
+### Add Or Update Agent Or Agent Prompt
+
+Adds or updates agent configuration, prompt files, and registers agents in orchestration manifests.
+
+**Frequency**: ~2 times per month
+
+**Steps**:
+1. Create or update agent prompt files under .opencode/prompts/agents/
+2. Update .opencode/opencode.json to register or modify agent configuration
+3. Update AGENTS.md to document the new or updated agent
+
+**Files typically involved**:
+- `.opencode/prompts/agents/*.txt`
+- `.opencode/opencode.json`
+- `AGENTS.md`
+
+**Example commit sequence**:
+```
+Create or update agent prompt files under .opencode/prompts/agents/
+Update .opencode/opencode.json to register or modify agent configuration
+Update AGENTS.md to document the new or updated agent
+```
+
+### Feature Development Skill And Docs
+
+Implements a new feature or workflow by adding skills, updating documentation, and synchronizing manifests and context.
+
+**Frequency**: ~3 times per month
+
+**Steps**:
+1. Add or update SKILL.md and related files in skills/ or .agents/skills/
+2. Update or create supporting documentation (README.md, AGENTS.md, docs/zh-CN/*, WORKING-CONTEXT.md)
+3. Update manifests/install-modules.json and/or manifests/install-components.json
+4. Synchronize or update related scripts or test files
+
+**Files typically involved**:
+- `skills/*/SKILL.md`
+- `.agents/skills/*/SKILL.md`
+- `AGENTS.md`
+- `README.md`
+- `README.zh-CN.md`
+- `docs/zh-CN/AGENTS.md`
+- `docs/zh-CN/README.md`
+- `WORKING-CONTEXT.md`
+- `manifests/install-modules.json`
+- `manifests/install-components.json`
+
+**Example commit sequence**:
+```
+Add or update SKILL.md and related files in skills/ or .agents/skills/
+Update or create supporting documentation (README.md, AGENTS.md, docs/zh-CN/*, WORKING-CONTEXT.md)
+Update manifests/install-modules.json and/or manifests/install-components.json
+Synchronize or update related scripts or test files
+```
+
+### Refactor Or Sync Manifests And Context
+
+Refactors commands, skills, or agents and synchronizes manifests and working context documentation.
+
+**Frequency**: ~2 times per month
+
+**Steps**:
+1. Update or remove command files under commands/
+2. Update or create SKILL.md files as needed
+3. Update manifests/install-modules.json and/or install-components.json
+4. Update AGENTS.md, README.md, README.zh-CN.md, docs/zh-CN/*, WORKING-CONTEXT.md
+
+**Files typically involved**:
+- `commands/*.md`
+- `skills/*/SKILL.md`
+- `manifests/install-modules.json`
+- `manifests/install-components.json`
+- `AGENTS.md`
+- `README.md`
+- `README.zh-CN.md`
+- `docs/zh-CN/AGENTS.md`
+- `docs/zh-CN/README.md`
+- `WORKING-CONTEXT.md`
+
+**Example commit sequence**:
+```
+Update or remove command files under commands/
+Update or create SKILL.md files as needed
+Update manifests/install-modules.json and/or install-components.json
+Update AGENTS.md, README.md, README.zh-CN.md, docs/zh-CN/*, WORKING-CONTEXT.md
+```
+
+### Add Or Update Install Target
+
+Adds or updates an install target (e.g., CodeBuddy, Gemini) with scripts, schemas, and manifest registration.
+
+**Frequency**: ~2 times per month
+
+**Steps**:
+1. Add or update install/uninstall scripts under .<target>/
+2. Update or create README files for the target
+3. Update schemas (ecc-install-config.schema.json, install-modules.schema.json)
+4. Update scripts/lib/install-targets/<target>-project.js and registry.js
+5. Update manifests/install-modules.json
+6. Update or add related test files
+
+**Files typically involved**:
+- `.<target>/*`
+- `manifests/install-modules.json`
+- `schemas/ecc-install-config.schema.json`
+- `schemas/install-modules.schema.json`
+- `scripts/lib/install-manifests.js`
+- `scripts/lib/install-targets/<target>-project.js`
+- `scripts/lib/install-targets/registry.js`
+- `tests/lib/install-targets.test.js`
+
+**Example commit sequence**:
+```
+Add or update install/uninstall scripts under .<target>/
+Update or create README files for the target
+Update schemas (ecc-install-config.schema.json, install-modules.schema.json)
+Update scripts/lib/install-targets/<target>-project.js and registry.js
+Update manifests/install-modules.json
+Update or add related test files
+```
+
+
+## Best Practices
+
+Based on analysis of the codebase, follow these practices:
+
+### Do
+
+- Use conventional commit format (feat:, fix:, etc.)
+- Follow *.test.js naming pattern
+- Use camelCase for file names
+- Prefer mixed exports
+
+### Don't
+
+- Don't write vague commit messages
+- Don't skip tests for new features
+- Don't deviate from established patterns without discussion
+
+---
+
+*This skill was auto-generated by [ECC Tools](https://ecc.tools). Review and customize as needed for your team.*

.claude/team/everything-claude-code-team-config.json

@@ -9,7 +9,7 @@
   "commandFiles": [
     ".claude/commands/feature-development.md",
     ".claude/commands/refactoring.md",
-    ".claude/commands/add-new-skill.md"
+    ".claude/commands/add-or-update-skill.md"
   ],
-  "updatedAt": "2026-04-02T03:20:48.238Z"
+  "updatedAt": "2026-04-02T03:14:01.196Z"
 }