From 2000b09c8a88077c193537a4f34fd86f87d1a206 Mon Sep 17 00:00:00 2001 From: "ecc-tools[bot]" <257055122+ecc-tools[bot]@users.noreply.github.com> Date: Thu, 2 Apr 2026 01:48:01 +0000 Subject: [PATCH] feat: add everything-claude-code-conventions ECC bundle (.agents/skills/everything-claude-code/SKILL.md) --- .../skills/everything-claude-code/SKILL.md | 287 ++++++++---------- 1 file changed, 132 insertions(+), 155 deletions(-) diff --git a/.agents/skills/everything-claude-code/SKILL.md b/.agents/skills/everything-claude-code/SKILL.md index 173826a8..6bc47cf7 100644 --- a/.agents/skills/everything-claude-code/SKILL.md +++ b/.agents/skills/everything-claude-code/SKILL.md @@ -5,7 +5,7 @@ description: Development conventions and patterns for everything-claude-code. Ja # Everything Claude Code Conventions -> Generated from [affaan-m/everything-claude-code](https://github.com/affaan-m/everything-claude-code) on 2026-03-20 +> Generated from [affaan-m/everything-claude-code](https://github.com/affaan-m/everything-claude-code) on 2026-04-02 ## Overview @@ -34,13 +34,13 @@ Follow these commit message conventions based on 500 analyzed commits. ### Prefixes Used - `fix` -- `test` - `feat` - `docs` +- `chore` ### Message Guidelines -- Average message length: ~65 characters +- Average message length: ~57 characters - Keep first line concise and descriptive - Use imperative mood ("Add feature" not "Added feature") @@ -48,49 +48,49 @@ Follow these commit message conventions based on 500 analyzed commits. *Commit message example* ```text -feat(rules): add C# language support +feat: add everything-claude-code ECC bundle (.claude/commands/add-or-update-command.md) ``` *Commit message example* ```text -chore(deps-dev): bump flatted (#675) +fix: port safe ci cleanup from backlog ``` *Commit message example* ```text -fix: auto-detect ECC root from plugin cache when CLAUDE_PLUGIN_ROOT is unset (#547) (#691) +refactor: collapse legacy command bodies into skills ``` *Commit message example* ```text -docs: add Antigravity setup and usage guide (#552) +docs: close bundle drift and sync plugin guidance ``` *Commit message example* ```text -merge: PR #529 — feat(skills): add documentation-lookup, bun-runtime, nextjs-turbopack; feat(agents): add rust-reviewer +chore: ignore local orchestration artifacts ``` *Commit message example* ```text -Revert "Add Kiro IDE support (.kiro/) (#548)" +feat: add everything-claude-code ECC bundle (.claude/commands/add-or-update-skill.md) ``` *Commit message example* ```text -Add Kiro IDE support (.kiro/) (#548) +feat: add everything-claude-code ECC bundle (.claude/commands/feature-development.md) ``` *Commit message example* ```text -feat: add block-no-verify hook for Claude Code and Cursor (#649) +feat: add everything-claude-code ECC bundle (.claude/enterprise/controls.md) ``` ## Architecture @@ -184,33 +184,11 @@ try { These workflows were detected from analyzing commit patterns. -### Database Migration - -Database schema changes with migration files - -**Frequency**: ~2 times per month - -**Steps**: -1. Create migration file -2. Update schema definitions -3. Generate/update types - -**Files typically involved**: -- `**/schema.*` -- `migrations/*` - -**Example commit sequence**: -``` -feat: implement --with/--without selective install flags (#679) -fix: sync catalog counts with filesystem (27 agents, 113 skills, 58 commands) (#693) -feat(rules): add Rust language rules (rebased #660) (#686) -``` - ### Feature Development Standard feature implementation workflow -**Frequency**: ~22 times per month +**Frequency**: ~19 times per month **Steps**: 1. Add feature implementation @@ -218,205 +196,204 @@ Standard feature implementation workflow 3. Update documentation **Files typically involved**: -- `manifests/*` -- `schemas/*` +- `.opencode/*` +- `.opencode/plugins/*` +- `.opencode/plugins/lib/*` - `**/*.test.*` -- `**/api/**` **Example commit sequence**: ``` -feat(skills): add documentation-lookup, bun-runtime, nextjs-turbopack; feat(agents): add rust-reviewer -docs(skills): align documentation-lookup with CONTRIBUTING template; add cross-harness (Codex/Cursor) skill copies -fix: address PR review — skill template (When to use, How it works, Examples), bun.lock, next build note, rust-reviewer CI note, doc-lookup privacy/uncertainty +feat: add GAN-style generator-evaluator harness (#1029) +feat(agents,skills): add opensource-pipeline — 3-agent workflow for safe public releases (#1036) +feat(install): add CodeBuddy(Tencent) adaptation with installation scripts (#1038) ``` -### Add Language Rules +### Refactoring -Adds a new programming language to the rules system, including coding style, hooks, patterns, security, and testing guidelines. +Code refactoring and cleanup workflow **Frequency**: ~2 times per month **Steps**: -1. Create a new directory under rules/{language}/ -2. Add coding-style.md, hooks.md, patterns.md, security.md, and testing.md files with language-specific content -3. Optionally reference or link to related skills +1. Ensure tests pass before refactor +2. Refactor code structure +3. Verify tests still pass **Files typically involved**: -- `rules/*/coding-style.md` -- `rules/*/hooks.md` -- `rules/*/patterns.md` -- `rules/*/security.md` -- `rules/*/testing.md` +- `src/**/*` **Example commit sequence**: ``` -Create a new directory under rules/{language}/ -Add coding-style.md, hooks.md, patterns.md, security.md, and testing.md files with language-specific content -Optionally reference or link to related skills +refactor: collapse legacy command bodies into skills +feat: add connected operator workflow skills +feat: expand lead intelligence outreach channels ``` -### Add New Skill +### Add Or Update Skill -Adds a new skill to the system, documenting its workflow, triggers, and usage, often with supporting scripts. +Adds a new skill or updates an existing skill, including documentation and configuration. + +**Frequency**: ~6 times per month + +**Steps**: +1. Create or update a SKILL.md file in the appropriate skills directory (e.g., skills/skill-name/SKILL.md or .agents/skills/skill-name/SKILL.md or .claude/skills/skill-name/SKILL.md). +2. Optionally update related manifests or documentation (e.g., AGENTS.md, README.md). + +**Files typically involved**: +- `skills/*/SKILL.md` +- `.agents/skills/*/SKILL.md` +- `.claude/skills/*/SKILL.md` + +**Example commit sequence**: +``` +Create or update a SKILL.md file in the appropriate skills directory (e.g., skills/skill-name/SKILL.md or .agents/skills/skill-name/SKILL.md or .claude/skills/skill-name/SKILL.md). +Optionally update related manifests or documentation (e.g., AGENTS.md, README.md). +``` + +### Add Or Update Command + +Adds a new workflow command or updates an existing command for agentic workflows. **Frequency**: ~4 times per month **Steps**: -1. Create a new directory under skills/{skill-name}/ -2. Add SKILL.md with documentation (When to Use, How It Works, Examples, etc.) -3. Optionally add scripts or supporting files under skills/{skill-name}/scripts/ -4. Address review feedback and iterate on documentation +1. Create or update a markdown file in the commands/ directory (e.g., commands/command-name.md). +2. Optionally update related documentation or reference files. **Files typically involved**: -- `skills/*/SKILL.md` -- `skills/*/scripts/*.sh` -- `skills/*/scripts/*.js` +- `commands/*.md` **Example commit sequence**: ``` -Create a new directory under skills/{skill-name}/ -Add SKILL.md with documentation (When to Use, How It Works, Examples, etc.) -Optionally add scripts or supporting files under skills/{skill-name}/scripts/ -Address review feedback and iterate on documentation +Create or update a markdown file in the commands/ directory (e.g., commands/command-name.md). +Optionally update related documentation or reference files. ``` -### Add New Agent +### Add Skill And Agents Bundle -Adds a new agent to the system for code review, build resolution, or other automated tasks. - -**Frequency**: ~2 times per month - -**Steps**: -1. Create a new agent markdown file under agents/{agent-name}.md -2. Register the agent in AGENTS.md -3. Optionally update README.md and docs/COMMAND-AGENT-MAP.md - -**Files typically involved**: -- `agents/*.md` -- `AGENTS.md` -- `README.md` -- `docs/COMMAND-AGENT-MAP.md` - -**Example commit sequence**: -``` -Create a new agent markdown file under agents/{agent-name}.md -Register the agent in AGENTS.md -Optionally update README.md and docs/COMMAND-AGENT-MAP.md -``` - -### Add New Workflow Surface - -Adds or updates a workflow entrypoint. Default to skills-first; only add a command shim when legacy slash compatibility is still required. - -**Frequency**: ~1 times per month - -**Steps**: -1. Create or update the canonical workflow under skills/{skill-name}/SKILL.md -2. Only if needed, add or update commands/{command-name}.md as a compatibility shim - -**Files typically involved**: -- `skills/*/SKILL.md` -- `commands/*.md` (only when a legacy shim is intentionally retained) - -**Example commit sequence**: -``` -Create or update the canonical skill under skills/{skill-name}/SKILL.md -Only if needed, add or update commands/{command-name}.md as a compatibility shim -``` - -### Sync Catalog Counts - -Synchronizes the documented counts of agents, skills, and commands in AGENTS.md and README.md with the actual repository state. +Adds a new feature or workflow by bundling new agents, skills, and supporting scripts or commands. **Frequency**: ~3 times per month **Steps**: -1. Update agent, skill, and command counts in AGENTS.md -2. Update the same counts in README.md (quick-start, comparison table, etc.) -3. Optionally update other documentation files +1. Create agent definition markdown files in agents/ (e.g., agents/agent-name.md). +2. Create a SKILL.md file in skills/ (e.g., skills/feature-name/SKILL.md). +3. Optionally add supporting scripts or commands. +4. Update documentation or manifests as needed. **Files typically involved**: -- `AGENTS.md` -- `README.md` +- `agents/*.md` +- `skills/*/SKILL.md` +- `scripts/*.sh` +- `commands/*.md` **Example commit sequence**: ``` -Update agent, skill, and command counts in AGENTS.md -Update the same counts in README.md (quick-start, comparison table, etc.) -Optionally update other documentation files +Create agent definition markdown files in agents/ (e.g., agents/agent-name.md). +Create a SKILL.md file in skills/ (e.g., skills/feature-name/SKILL.md). +Optionally add supporting scripts or commands. +Update documentation or manifests as needed. ``` -### Add Cross Harness Skill Copies +### Add Install Target -Adds skill copies for different agent harnesses (e.g., Codex, Cursor, Antigravity) to ensure compatibility across platforms. +Adds a new install target (integration with an external tool or platform) including scripts, schemas, and manifest updates. **Frequency**: ~2 times per month **Steps**: -1. Copy or adapt SKILL.md to .agents/skills/{skill}/SKILL.md and/or .cursor/skills/{skill}/SKILL.md -2. Optionally add harness-specific openai.yaml or config files -3. Address review feedback to align with CONTRIBUTING template +1. Add a new directory for the target (e.g., .codebuddy/, .gemini/), including README and install/uninstall scripts. +2. Update manifests/install-modules.json and schemas/ecc-install-config.schema.json. +3. Add or update scripts in scripts/lib/install-targets/. +4. Add or update tests for the new install target. **Files typically involved**: -- `.agents/skills/*/SKILL.md` -- `.cursor/skills/*/SKILL.md` -- `.agents/skills/*/agents/openai.yaml` +- `.codebuddy/*` +- `.gemini/*` +- `manifests/install-modules.json` +- `schemas/ecc-install-config.schema.json` +- `schemas/install-modules.schema.json` +- `scripts/lib/install-targets/*.js` +- `tests/lib/install-targets.test.js` **Example commit sequence**: ``` -Copy or adapt SKILL.md to .agents/skills/{skill}/SKILL.md and/or .cursor/skills/{skill}/SKILL.md -Optionally add harness-specific openai.yaml or config files -Address review feedback to align with CONTRIBUTING template +Add a new directory for the target (e.g., .codebuddy/, .gemini/), including README and install/uninstall scripts. +Update manifests/install-modules.json and schemas/ecc-install-config.schema.json. +Add or update scripts in scripts/lib/install-targets/. +Add or update tests for the new install target. ``` -### Add Or Update Hook +### Sync Or Update Codex Ecc Baseline -Adds or updates git or bash hooks to enforce workflow, quality, or security policies. +Synchronizes or updates configuration and scripts between ECC and Codex, ensuring consistency across tools. -**Frequency**: ~1 times per month +**Frequency**: ~2 times per month **Steps**: -1. Add or update hook scripts in hooks/ or scripts/hooks/ -2. Register the hook in hooks/hooks.json or similar config -3. Optionally add or update tests in tests/hooks/ +1. Update or create scripts in scripts/codex/ and scripts/sync-ecc-to-codex.sh. +2. Update configuration files such as package.json and related test files. +3. Update documentation (e.g., WORKING-CONTEXT.md). + +**Files typically involved**: +- `scripts/codex/*.js` +- `scripts/sync-ecc-to-codex.sh` +- `package.json` +- `tests/scripts/*.test.js` +- `WORKING-CONTEXT.md` + +**Example commit sequence**: +``` +Update or create scripts in scripts/codex/ and scripts/sync-ecc-to-codex.sh. +Update configuration files such as package.json and related test files. +Update documentation (e.g., WORKING-CONTEXT.md). +``` + +### Update Hooks And Hook Tests + +Updates hook configuration and logic, often with corresponding test updates. + +**Frequency**: ~3 times per month + +**Steps**: +1. Update hooks/hooks.json and/or scripts/hooks/*.js. +2. Update or add related test files in tests/hooks/ or tests/scripts/. +3. Optionally update documentation (e.g., WORKING-CONTEXT.md). **Files typically involved**: -- `hooks/*.hook` - `hooks/hooks.json` - `scripts/hooks/*.js` - `tests/hooks/*.test.js` -- `.cursor/hooks.json` +- `tests/scripts/*.test.js` +- `WORKING-CONTEXT.md` **Example commit sequence**: ``` -Add or update hook scripts in hooks/ or scripts/hooks/ -Register the hook in hooks/hooks.json or similar config -Optionally add or update tests in tests/hooks/ +Update hooks/hooks.json and/or scripts/hooks/*.js. +Update or add related test files in tests/hooks/ or tests/scripts/. +Optionally update documentation (e.g., WORKING-CONTEXT.md). ``` -### Address Review Feedback +### Update Or Add Documentation -Addresses code review feedback by updating documentation, scripts, or configuration for clarity, correctness, or convention alignment. +Adds or updates documentation files, including troubleshooting, guides, and context files. **Frequency**: ~4 times per month **Steps**: -1. Edit SKILL.md, agent, or command files to address reviewer comments -2. Update examples, headings, or configuration as requested -3. Iterate until all review feedback is resolved +1. Create or update markdown files in docs/ or root directory. +2. Optionally update related context files (e.g., WORKING-CONTEXT.md). **Files typically involved**: -- `skills/*/SKILL.md` -- `agents/*.md` -- `commands/*.md` -- `.agents/skills/*/SKILL.md` -- `.cursor/skills/*/SKILL.md` +- `docs/*.md` +- `WORKING-CONTEXT.md` +- `README.md` +- `README.zh-CN.md` **Example commit sequence**: ``` -Edit SKILL.md, agent, or command files to address reviewer comments -Update examples, headings, or configuration as requested -Iterate until all review feedback is resolved +Create or update markdown files in docs/ or root directory. +Optionally update related context files (e.g., WORKING-CONTEXT.md). ```