From cc45228eda79e0f1e3ed712318459d6973730ee1 Mon Sep 17 00:00:00 2001 From: "ecc-tools[bot]" <257055122+ecc-tools[bot]@users.noreply.github.com> Date: Thu, 2 Apr 2026 13:44:05 +0000 Subject: [PATCH] feat: add everything-claude-code-conventions ECC bundle (.claude/skills/everything-claude-code/SKILL.md) --- .../skills/everything-claude-code/SKILL.md | 368 +++++++++--------- 1 file changed, 189 insertions(+), 179 deletions(-) diff --git a/.claude/skills/everything-claude-code/SKILL.md b/.claude/skills/everything-claude-code/SKILL.md index 799c37f5..717f5303 100644 --- a/.claude/skills/everything-claude-code/SKILL.md +++ b/.claude/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: ~56 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(skills): add argus-dispatch — multi-model task dispatcher ``` *Commit message example* ```text -chore(deps-dev): bump flatted (#675) +refactor: extract social graph ranking core ``` *Commit message example* ```text -fix: auto-detect ECC root from plugin cache when CLAUDE_PLUGIN_ROOT is unset (#547) (#691) +fix: port safe ci cleanup from backlog ``` *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(skills): add brand voice and network ops lanes ``` *Commit message example* ```text -Add Kiro IDE support (.kiro/) (#548) +feat: sync the codex baseline and agent roles ``` *Commit message example* ```text -feat: add block-no-verify hook for Claude Code and Cursor (#649) +fix: harden install and codex sync portability ``` ## 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**: ~14 times per month **Steps**: 1. Add feature implementation @@ -218,205 +196,237 @@ 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(team-builder): use `claude agents` command for agent discovery (#1021) +fix: extract inline SessionStart bootstrap to separate file (#1035) +feat: add hexagonal architecture SKILL. (#1034) ``` -### Add Language Rules +### Refactoring -Adds a new programming language to the rules system, including coding style, hooks, patterns, security, and testing guidelines. - -**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 - -**Files typically involved**: -- `rules/*/coding-style.md` -- `rules/*/hooks.md` -- `rules/*/patterns.md` -- `rules/*/security.md` -- `rules/*/testing.md` - -**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 -``` - -### Add New Skill - -Adds a new skill to the system, documenting its workflow, triggers, and usage, often with supporting scripts. - -**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 - -**Files typically involved**: -- `skills/*/SKILL.md` -- `skills/*/scripts/*.sh` -- `skills/*/scripts/*.js` - -**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 -``` - -### Add New Agent - -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 Command - -Adds a new command to the system, often paired with a backing skill. - -**Frequency**: ~1 times per month - -**Steps**: -1. Create a new markdown file under commands/{command-name}.md -2. Optionally add or update a backing skill under skills/{skill-name}/SKILL.md - -**Files typically involved**: -- `commands/*.md` -- `skills/*/SKILL.md` - -**Example commit sequence**: -``` -Create a new markdown file under commands/{command-name}.md -Optionally add or update a backing skill under skills/{skill-name}/SKILL.md -``` - -### Sync Catalog Counts - -Synchronizes the documented counts of agents, skills, and commands in AGENTS.md and README.md with the actual repository state. +Code refactoring and cleanup workflow **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. 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 New Skill + +Adds a new AI agent skill to the codebase, including documentation and registration. + +**Frequency**: ~3 times per month + +**Steps**: +1. Create a new SKILL.md file in skills// or .agents/skills// +2. Optionally add supporting scripts or references under the skill directory +3. Update AGENTS.md and/or README.md to document the new skill +4. Update docs/zh-CN/AGENTS.md and docs/zh-CN/README.md for Chinese documentation +5. Update manifests/install-modules.json or install-components.json to register the skill + +**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` +- `manifests/install-modules.json` +- `manifests/install-components.json` + +**Example commit sequence**: +``` +Create a new SKILL.md file in skills// or .agents/skills// +Optionally add supporting scripts or references under the skill directory +Update AGENTS.md and/or README.md to document the new skill +Update docs/zh-CN/AGENTS.md and docs/zh-CN/README.md for Chinese documentation +Update manifests/install-modules.json or install-components.json to register the skill +``` + +### Add New Agent Or Pipeline + +Adds a new agent or multi-agent workflow pipeline, including agent definitions and orchestration skills. + +**Frequency**: ~2 times per month + +**Steps**: +1. Create one or more agent definition files in agents/ +2. Create or update a SKILL.md in skills// to orchestrate or document the workflow +3. Optionally add supporting commands, scripts, or examples +4. Update AGENTS.md and/or README.md to document the new pipeline + +**Files typically involved**: +- `agents/*.md` +- `skills/*/SKILL.md` +- `commands/*.md` +- `scripts/*.sh` +- `examples/*/README.md` - `AGENTS.md` - `README.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 one or more agent definition files in agents/ +Create or update a SKILL.md in skills// to orchestrate or document the workflow +Optionally add supporting commands, scripts, or examples +Update AGENTS.md and/or README.md to document the new pipeline ``` -### Add Cross Harness Skill Copies +### Add Or Update Command Workflow -Adds skill copies for different agent harnesses (e.g., Codex, Cursor, Antigravity) to ensure compatibility across platforms. +Adds or extends a CLI command for agent workflows, often with review feedback iterations. **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. Create or update one or more command markdown files in commands/ +2. Iterate with fixes based on review feedback (improving YAML frontmatter, usage, output, etc.) +3. Optionally update AGENTS.md or documentation to reference the new command **Files typically involved**: -- `.agents/skills/*/SKILL.md` -- `.cursor/skills/*/SKILL.md` -- `.agents/skills/*/agents/openai.yaml` +- `commands/*.md` +- `AGENTS.md` +- `README.md` **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 +Create or update one or more command markdown files in commands/ +Iterate with fixes based on review feedback (improving YAML frontmatter, usage, output, etc.) +Optionally update AGENTS.md or documentation to reference the new command ``` -### Add Or Update Hook +### Add Install Target Or Adapter -Adds or updates git or bash hooks to enforce workflow, quality, or security policies. +Adds support for a new install target (e.g., Gemini, CodeBuddy), including scripts, schemas, and manifest updates. -**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. Add a new directory for the install target (e.g., .gemini/, .codebuddy/) +2. Add install/uninstall scripts and README(s) +3. Update schemas/ecc-install-config.schema.json and/or install-modules.schema.json +4. Update manifests/install-modules.json +5. Update scripts/lib/install-manifests.js and scripts/lib/install-targets/.js +6. Add or update tests for the new install target **Files typically involved**: -- `hooks/*.hook` -- `hooks/hooks.json` -- `scripts/hooks/*.js` -- `tests/hooks/*.test.js` -- `.cursor/hooks.json` +- `./*` +- `schemas/ecc-install-config.schema.json` +- `schemas/install-modules.schema.json` +- `manifests/install-modules.json` +- `scripts/lib/install-manifests.js` +- `scripts/lib/install-targets/*.js` +- `tests/lib/install-targets.test.js` **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/ +Add a new directory for the install target (e.g., .gemini/, .codebuddy/) +Add install/uninstall scripts and README(s) +Update schemas/ecc-install-config.schema.json and/or install-modules.schema.json +Update manifests/install-modules.json +Update scripts/lib/install-manifests.js and scripts/lib/install-targets/.js +Add or update tests for the new install target ``` -### Address Review Feedback +### Update Hooks Or Automation -Addresses code review feedback by updating documentation, scripts, or configuration for clarity, correctness, or convention alignment. +Refactors or fixes hooks and automation scripts for CI, formatting, or agent workflow integration. + +**Frequency**: ~3 times per month + +**Steps**: +1. Edit hooks/hooks.json to update hook configuration +2. Edit or add scripts/hooks/*.js or scripts/hooks/*.sh for hook logic +3. Update or add tests for the hooks in tests/hooks/*.test.js +4. Optionally update related scripts or documentation + +**Files typically involved**: +- `hooks/hooks.json` +- `scripts/hooks/*.js` +- `scripts/hooks/*.sh` +- `tests/hooks/*.test.js` + +**Example commit sequence**: +``` +Edit hooks/hooks.json to update hook configuration +Edit or add scripts/hooks/*.js or scripts/hooks/*.sh for hook logic +Update or add tests for the hooks in tests/hooks/*.test.js +Optionally update related scripts or documentation +``` + +### Documentation Sync And Localization + +Updates documentation and ensures Chinese and English docs are in sync, including AGENTS.md and README files. + +**Frequency**: ~3 times per month + +**Steps**: +1. Edit AGENTS.md, README.md, README.zh-CN.md +2. Edit docs/zh-CN/AGENTS.md, docs/zh-CN/README.md +3. Optionally update skills/*/SKILL.md and .agents/skills/*/SKILL.md for doc improvements +4. Edit WORKING-CONTEXT.md or the-shortform-guide.md as needed + +**Files typically involved**: +- `AGENTS.md` +- `README.md` +- `README.zh-CN.md` +- `docs/zh-CN/AGENTS.md` +- `docs/zh-CN/README.md` +- `skills/*/SKILL.md` +- `.agents/skills/*/SKILL.md` +- `WORKING-CONTEXT.md` +- `the-shortform-guide.md` + +**Example commit sequence**: +``` +Edit AGENTS.md, README.md, README.zh-CN.md +Edit docs/zh-CN/AGENTS.md, docs/zh-CN/README.md +Optionally update skills/*/SKILL.md and .agents/skills/*/SKILL.md for doc improvements +Edit WORKING-CONTEXT.md or the-shortform-guide.md as needed +``` + +### Dependency Or Ci Update + +Updates dependencies or CI workflow files, often via automated bots like dependabot. **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. Edit .github/workflows/*.yml to update actions or workflow steps +2. Edit package.json, yarn.lock, or package-lock.json for dependency updates +3. Optionally update related scripts or lockfiles **Files typically involved**: -- `skills/*/SKILL.md` -- `agents/*.md` -- `commands/*.md` -- `.agents/skills/*/SKILL.md` -- `.cursor/skills/*/SKILL.md` +- `.github/workflows/*.yml` +- `package.json` +- `yarn.lock` +- `package-lock.json` **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 +Edit .github/workflows/*.yml to update actions or workflow steps +Edit package.json, yarn.lock, or package-lock.json for dependency updates +Optionally update related scripts or lockfiles ```