From 0e63bb37deedb23b010d9181e4a8514724ffacf6 Mon Sep 17 00:00:00 2001 From: "ecc-tools[bot]" <257055122+ecc-tools[bot]@users.noreply.github.com> Date: Wed, 1 Apr 2026 22:51:09 +0000 Subject: [PATCH] feat: add everything-claude-code-conventions ECC bundle (.claude/skills/everything-claude-code/SKILL.md) --- .../skills/everything-claude-code/SKILL.md | 243 ++++++++---------- 1 file changed, 102 insertions(+), 141 deletions(-) diff --git a/.claude/skills/everything-claude-code/SKILL.md b/.claude/skills/everything-claude-code/SKILL.md index 799c37f5..3dd4f830 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-01 ## 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-new-skill.md) ``` *Commit message example* ```text -chore(deps-dev): bump flatted (#675) +refactor: collapse legacy command bodies into skills ``` *Commit message example* ```text -fix: auto-detect ECC root from plugin cache when CLAUDE_PLUGIN_ROOT is unset (#547) (#691) +fix: dedupe managed hooks by semantic identity ``` *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/refactoring.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,188 @@ 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: install claude-hud plugin (jarrodwatts/claude-hud) (#1041) +feat: add GAN-style generator-evaluator harness (#1029) +feat(agents,skills): add opensource-pipeline — 3-agent workflow for safe public releases (#1036) ``` -### 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 -Adds a new skill to the system, documenting its workflow, triggers, and usage, often with supporting scripts. +Adds a new skill to the repository, enabling new agent capabilities or 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 a new SKILL.md file under skills/ or .agents/skills/ or .claude/skills/ +2. Optionally update documentation (AGENTS.md, README.md, WORKING-CONTEXT.md) +3. Optionally add supporting files (e.g., manifests/install-modules.json) **Files typically involved**: - `skills/*/SKILL.md` -- `skills/*/scripts/*.sh` -- `skills/*/scripts/*.js` +- `.agents/skills/*/SKILL.md` +- `.claude/skills/*/SKILL.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 a new SKILL.md file under skills/ or .agents/skills/ or .claude/skills/ +Optionally update documentation (AGENTS.md, README.md, WORKING-CONTEXT.md) +Optionally add supporting files (e.g., manifests/install-modules.json) ``` -### Add New Agent +### Add Or Update Agent -Adds a new agent to the system for code review, build resolution, or other automated tasks. +Adds or updates agent definitions and registers them in configuration files. **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 +1. Add or update agent definition file (e.g., agents/*.md or .opencode/prompts/agents/*.txt) +2. Update agent registry/configuration (e.g., .opencode/opencode.json, AGENTS.md) **Files typically involved**: - `agents/*.md` +- `.opencode/prompts/agents/*.txt` +- `.opencode/opencode.json` - `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 or update agent definition file (e.g., agents/*.md or .opencode/prompts/agents/*.txt) +Update agent registry/configuration (e.g., .opencode/opencode.json, AGENTS.md) ``` -### Add New Command +### Add Or Update Command -Adds a new command to the system, often paired with a backing skill. +Adds or updates command workflow files for agentic operations. -**Frequency**: ~1 times per month +**Frequency**: ~2 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 +1. Create or update command markdown file under commands/ +2. Optionally update documentation or index files **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 +Create or update command markdown file under commands/ +Optionally update documentation or index files ``` -### Sync Catalog Counts +### Feature Or Skill Bundle -Synchronizes the documented counts of agents, skills, and commands in AGENTS.md and README.md with the actual repository state. +Adds a bundle of related features, skills, and documentation for a new workflow or capability. + +**Frequency**: ~2 times per month + +**Steps**: +1. Add multiple agent and/or skill files +2. Add supporting commands and scripts +3. Add or update documentation and examples + +**Files typically involved**: +- `agents/*.md` +- `skills/*/SKILL.md` +- `commands/*.md` +- `scripts/*.sh` +- `examples/*` + +**Example commit sequence**: +``` +Add multiple agent and/or skill files +Add supporting commands and scripts +Add or update documentation and examples +``` + +### Documentation Update + +Updates documentation to reflect new features, workflows, or guidance. **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. Edit documentation files (README.md, AGENTS.md, WORKING-CONTEXT.md, docs/...) +2. Optionally update or add new guidance files **Files typically involved**: -- `AGENTS.md` - `README.md` +- `AGENTS.md` +- `WORKING-CONTEXT.md` +- `docs/**/*.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 +Edit documentation files (README.md, AGENTS.md, WORKING-CONTEXT.md, docs/...) +Optionally update or add new guidance files ``` -### Add Cross Harness Skill Copies +### Dependency Or Schema Update -Adds skill copies for different agent harnesses (e.g., Codex, Cursor, Antigravity) to ensure compatibility across platforms. +Updates dependencies or schema files, often in response to new features or external 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. Edit package.json, yarn.lock, or other lockfiles +2. Edit schema files under schemas/ +3. Optionally update related scripts or manifests **Files typically involved**: -- `.agents/skills/*/SKILL.md` -- `.cursor/skills/*/SKILL.md` -- `.agents/skills/*/agents/openai.yaml` +- `package.json` +- `yarn.lock` +- `schemas/*.json` **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 +Edit package.json, yarn.lock, or other lockfiles +Edit schema files under schemas/ +Optionally update related scripts or manifests ``` -### Add Or Update Hook +### Ci Cd Workflow Update -Adds or updates git or bash hooks to enforce workflow, quality, or security policies. +Updates CI/CD workflow files, usually for dependency bumps or workflow improvements. -**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. Edit workflow files under .github/workflows/ **Files typically involved**: -- `hooks/*.hook` -- `hooks/hooks.json` -- `scripts/hooks/*.js` -- `tests/hooks/*.test.js` -- `.cursor/hooks.json` +- `.github/workflows/*.yml` **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/ -``` - -### Address Review Feedback - -Addresses code review feedback by updating documentation, scripts, or configuration for clarity, correctness, or convention alignment. - -**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 - -**Files typically involved**: -- `skills/*/SKILL.md` -- `agents/*.md` -- `commands/*.md` -- `.agents/skills/*/SKILL.md` -- `.cursor/skills/*/SKILL.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 +Edit workflow files under .github/workflows/ ```