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

feat: add everything-claude-code ECC bundle (.claude/skills/everything-claude-code/SKILL.md)

Browse Source
This commit is contained in:
ecc-tools[bot]
2026-03-24 10:43:29 +00:00
committed by GitHub
parent 2f8abe36c1
commit 0ce8b82fbb
1 changed files with 112 additions and 106 deletions
Download Patch File Download Diff File Expand all files Collapse all files

218
.claude/skills/everything-claude-code/SKILL.md
View File

@@ -48,7 +48,7 @@ Follow these commit message conventions based on 500 analyzed commits.
*Commit message example* *Commit message example*
```text ```text
feat(ecc2): add split-pane dashboard resizing feat: add everything-claude-code ECC bundle (.claude/commands/add-or-update-skill-documentation.md)
``` ```
*Commit message example* *Commit message example*
@@ -78,19 +78,19 @@ security: remove supply chain risks, external promotions, and unauthorized credi
*Commit message example* *Commit message example*
```text ```text
feat: scaffold ECC 2.0 Rust TUI — agentic IDE control plane feat: add everything-claude-code ECC bundle (.claude/commands/feature-development.md)
``` ```
*Commit message example* *Commit message example*
```text ```text
feat(skills): add santa-method - multi-agent adversarial verification (#760) feat: add everything-claude-code ECC bundle (.claude/commands/database-migration.md)
``` ```
*Commit message example* *Commit message example*
```text ```text
feat: pending instinct TTL pruning and /prune command (#725) feat: add everything-claude-code ECC bundle (.claude/enterprise/controls.md)
``` ```
## Architecture ## Architecture
@@ -200,16 +200,16 @@ Database schema changes with migration files
**Example commit sequence**: **Example commit sequence**:
``` ```
feat(rules): add C# language support (#704) Add Turkish (tr) docs and update README (#744)
fix: sanitize SessionStart session summaries (#710) docs(zh-CN): translate code block(plain text) (#753)
feat: add MCP health-check hook (#711) fix(install): add rust, cpp, csharp to legacy language alias map (#747)
``` ```
### Feature Development ### Feature Development
Standard feature implementation workflow Standard feature implementation workflow
**Frequency**: ~16 times per month **Frequency**: ~21 times per month
**Steps**: **Steps**:
1. Add feature implementation 1. Add feature implementation
@@ -223,158 +223,164 @@ Standard feature implementation workflow
**Example commit sequence**: **Example commit sequence**:
``` ```
feat: agent description compression with lazy loading (#696) docs(pt-BR): add rules translation
feat: add nuxt 4 patterns skill (#702) docs(pt-BR): add examples translation
feat(rules): add C# language support (#704) docs(pt-BR): add commands translation
``` ```
### Add Or Update Skill Documentation ### Add Or Update Skill
Adds a new skill or updates documentation for an existing skill. Typically involves creating or modifying SKILL.md files under skills/ or docs/xx/skills/ directories. Adds a new skill or updates an existing skill, including documentation and configuration.
**Frequency**: ~4 times per month
**Steps**:
1. Create or update SKILL.md under skills/<skill-name>/ or docs/<lang>/skills/<skill-name>/
2. Optionally update AGENTS.md or README.md to reflect new skill count or catalog
3. Commit with message referencing the skill and a summary of changes
**Files typically involved**:
- `skills/*/SKILL.md`
- `docs/*/skills/*/SKILL.md`
- `AGENTS.md`
- `README.md`
**Example commit sequence**:
```
Create or update SKILL.md under skills/<skill-name>/ or docs/<lang>/skills/<skill-name>/
Optionally update AGENTS.md or README.md to reflect new skill count or catalog
Commit with message referencing the skill and a summary of changes
```
### Add Or Update Localization
Adds or updates documentation translations for a new or existing language. Involves creating or modifying multiple files under docs/<lang>/, often in bulk.
**Frequency**: ~3 times per month
**Steps**:
1. Add or update markdown files under docs/<lang>/ for agents, commands, skills, rules, etc.
2. Update README.md to include the new language or increment language count
3. Commit with message referencing the language and scope (e.g., pt-BR, zh-CN, tr)
**Files typically involved**:
- `docs/*/README.md`
- `docs/*/agents/*.md`
- `docs/*/commands/*.md`
- `docs/*/skills/*/SKILL.md`
- `docs/*/rules/**/*.md`
- `README.md`
**Example commit sequence**:
```
Add or update markdown files under docs/<lang>/ for agents, commands, skills, rules, etc.
Update README.md to include the new language or increment language count
Commit with message referencing the language and scope (e.g., pt-BR, zh-CN, tr)
```
### Add Or Update Hook
Adds a new hook or updates an existing one for agentic workflows. Involves changes to hooks.json and corresponding scripts.
**Frequency**: ~2 times per month **Frequency**: ~2 times per month
**Steps**: **Steps**:
1. Add or update entry in hooks/hooks.json 1. Create or update SKILL.md in the appropriate skills/ directory
2. Create or modify corresponding script in scripts/hooks/ 2. Optionally update related documentation or integration files
3. Optionally add or update tests in tests/hooks/ or tests/integration/
4. Commit with message referencing the hook and its purpose **Files typically involved**:
- `skills/*/SKILL.md`
- `docs/zh-CN/skills/*/SKILL.md`
- `docs/tr/skills/*/SKILL.md`
**Example commit sequence**:
```
Create or update SKILL.md in the appropriate skills/ directory
Optionally update related documentation or integration files
```
### Add Or Update Command Doc
Adds or updates documentation for a command, including translations.
**Frequency**: ~3 times per month
**Steps**:
1. Create or update command documentation in the commands/ directory
2. Optionally add or update translations in docs/zh-CN/commands/ or docs/tr/commands/
**Files typically involved**:
- `commands/*.md`
- `docs/zh-CN/commands/*.md`
- `docs/tr/commands/*.md`
- `docs/pt-BR/commands/*.md`
**Example commit sequence**:
```
Create or update command documentation in the commands/ directory
Optionally add or update translations in docs/zh-CN/commands/ or docs/tr/commands/
```
### Add Or Update Localization
Adds or updates documentation translations for a new or existing language.
**Frequency**: ~2 times per month
**Steps**:
1. Add or update translated files in docs/{lang}/ directories for agents, commands, skills, rules, etc.
2. Update README.md to reference the new or updated language
**Files typically involved**:
- `docs/zh-CN/**/*`
- `docs/pt-BR/**/*`
- `docs/tr/**/*`
- `README.md`
**Example commit sequence**:
```
Add or update translated files in docs/{lang}/ directories for agents, commands, skills, rules, etc.
Update README.md to reference the new or updated language
```
### Add Or Update Hook
Adds a new agentic hook or updates hook configuration/scripts.
**Frequency**: ~2 times per month
**Steps**:
1. Edit hooks/hooks.json to add or modify hook definitions
2. Update or add hook implementation scripts in scripts/hooks/
3. Optionally update related plugin files (e.g., .opencode/plugins/ecc-hooks.ts)
**Files typically involved**: **Files typically involved**:
- `hooks/hooks.json` - `hooks/hooks.json`
- `scripts/hooks/*.js` - `scripts/hooks/*.js`
- `tests/hooks/*.test.js` - `.opencode/plugins/*.ts`
- `tests/integration/*.test.js`
**Example commit sequence**: **Example commit sequence**:
``` ```
Add or update entry in hooks/hooks.json Edit hooks/hooks.json to add or modify hook definitions
Create or modify corresponding script in scripts/hooks/ Update or add hook implementation scripts in scripts/hooks/
Optionally add or update tests in tests/hooks/ or tests/integration/ Optionally update related plugin files (e.g., .opencode/plugins/ecc-hooks.ts)
Commit with message referencing the hook and its purpose
``` ```
### Add Or Update Session Adapter Feature ### Add Or Update Session Adapter
Adds or updates features in the session adapter, typically involving implementation, contract documentation, and tests. Adds or updates session adapter logic, including contract documentation and tests.
**Frequency**: ~1 times per month **Frequency**: ~2 times per month
**Steps**: **Steps**:
1. Update implementation in scripts/lib/session-adapters/canonical-session.js 1. Edit scripts/lib/session-adapters/*.js for implementation
2. Update contract documentation in docs/SESSION-ADAPTER-CONTRACT.md 2. Update docs/SESSION-ADAPTER-CONTRACT.md for documentation
3. Add or update corresponding tests in tests/lib/session-adapters.test.js 3. Update or add tests in tests/lib/session-adapters.test.js
**Files typically involved**: **Files typically involved**:
- `scripts/lib/session-adapters/canonical-session.js` - `scripts/lib/session-adapters/*.js`
- `docs/SESSION-ADAPTER-CONTRACT.md` - `docs/SESSION-ADAPTER-CONTRACT.md`
- `tests/lib/session-adapters.test.js` - `tests/lib/session-adapters.test.js`
**Example commit sequence**: **Example commit sequence**:
``` ```
Update implementation in scripts/lib/session-adapters/canonical-session.js Edit scripts/lib/session-adapters/*.js for implementation
Update contract documentation in docs/SESSION-ADAPTER-CONTRACT.md Update docs/SESSION-ADAPTER-CONTRACT.md for documentation
Add or update corresponding tests in tests/lib/session-adapters.test.js Update or add tests in tests/lib/session-adapters.test.js
``` ```
### Add Or Update Language Support ### Add Or Update Install Manifest
Adds or updates support for a programming language, including rules, patterns, and install scripts/tests. Extends language support or fixes install resolution logic for legacy or new languages.
**Frequency**: ~1 times per month **Frequency**: ~2 times per month
**Steps**: **Steps**:
1. Add or update rules under rules/<language>/ (coding-style.md, hooks.md, patterns.md, security.md, testing.md) 1. Edit scripts/lib/install-manifests.js for logic
2. Update scripts/lib/install-manifests.js and manifests/install-components.json for install support 2. Update manifests/install-components.json for manifest data
3. Add or update tests in tests/lib/install-manifests.test.js 3. Add or update tests in tests/lib/install-manifests.test.js
**Files typically involved**: **Files typically involved**:
- `rules/*/*.md`
- `scripts/lib/install-manifests.js` - `scripts/lib/install-manifests.js`
- `manifests/install-components.json` - `manifests/install-components.json`
- `tests/lib/install-manifests.test.js` - `tests/lib/install-manifests.test.js`
**Example commit sequence**: **Example commit sequence**:
``` ```
Add or update rules under rules/<language>/ (coding-style.md, hooks.md, patterns.md, security.md, testing.md) Edit scripts/lib/install-manifests.js for logic
Update scripts/lib/install-manifests.js and manifests/install-components.json for install support Update manifests/install-components.json for manifest data
Add or update tests in tests/lib/install-manifests.test.js Add or update tests in tests/lib/install-manifests.test.js
``` ```
### Codex Config Sync And Merge ### Add Or Update Ecc Bundle
Synchronizes and merges Codex configuration files, ensuring user content is preserved and ECC-managed sections are updated. Adds new ECC bundle files for commands, skills, team config, or research playbooks.
**Frequency**: ~1 times per month **Frequency**: ~2 times per month
**Steps**: **Steps**:
1. Update or create scripts/codex/merge-mcp-config.js or scripts/sync-ecc-to-codex.sh 1. Create or update files in .claude/commands/, .claude/skills/, .claude/team/, .claude/research/, .claude/rules/, etc.
2. Update AGENTS.md or .codex/AGENTS.md as needed
3. Update README.md to reflect server/catalog changes
4. Commit with message referencing sync/merge and affected files
**Files typically involved**: **Files typically involved**:
- `scripts/codex/merge-mcp-config.js` - `.claude/commands/*.md`
- `scripts/sync-ecc-to-codex.sh` - `.claude/skills/*/SKILL.md`
- `.codex/AGENTS.md` - `.claude/team/*.json`
- `README.md` - `.claude/research/*.md`
- `.claude/rules/*.md`
**Example commit sequence**: **Example commit sequence**:
``` ```
Update or create scripts/codex/merge-mcp-config.js or scripts/sync-ecc-to-codex.sh Create or update files in .claude/commands/, .claude/skills/, .claude/team/, .claude/research/, .claude/rules/, etc.
Update AGENTS.md or .codex/AGENTS.md as needed
Update README.md to reflect server/catalog changes
Commit with message referencing sync/merge and affected files
``` ```