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

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

Browse Source
This commit is contained in:
ecc-tools[bot]
2026-04-01 22:51:09 +00:00
committed by GitHub
parent 03dfdd2fa0
commit 0e63bb37de
1 changed files with 102 additions and 141 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -5,7 +5,7 @@ description: Development conventions and patterns for everything-claude-code. Ja
# Everything Claude Code Conventions # 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 ## Overview
@@ -34,13 +34,13 @@ Follow these commit message conventions based on 500 analyzed commits.
### Prefixes Used ### Prefixes Used
- `fix` - `fix`
- `test`
- `feat` - `feat`
- `docs` - `docs`
- `chore`
### Message Guidelines ### Message Guidelines
- Average message length: ~65 characters - Average message length: ~57 characters
- Keep first line concise and descriptive - Keep first line concise and descriptive
- Use imperative mood ("Add feature" not "Added feature") - 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* *Commit message example*
```text ```text
feat(rules): add C# language support feat: add everything-claude-code ECC bundle (.claude/commands/add-new-skill.md)
``` ```
*Commit message example* *Commit message example*
```text ```text
chore(deps-dev): bump flatted (#675) refactor: collapse legacy command bodies into skills
``` ```
*Commit message example* *Commit message example*
```text ```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* *Commit message example*
```text ```text
docs: add Antigravity setup and usage guide (#552) docs: close bundle drift and sync plugin guidance
``` ```
*Commit message example* *Commit message example*
```text ```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* *Commit message example*
```text ```text
Revert "Add Kiro IDE support (.kiro/) (#548)" feat: add everything-claude-code ECC bundle (.claude/commands/refactoring.md)
``` ```
*Commit message example* *Commit message example*
```text ```text
Add Kiro IDE support (.kiro/) (#548) feat: add everything-claude-code ECC bundle (.claude/commands/feature-development.md)
``` ```
*Commit message example* *Commit message example*
```text ```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 ## Architecture
@@ -184,33 +184,11 @@ try {
These workflows were detected from analyzing commit patterns. 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 ### Feature Development
Standard feature implementation workflow Standard feature implementation workflow
**Frequency**: ~22 times per month **Frequency**: ~19 times per month
**Steps**: **Steps**:
1. Add feature implementation 1. Add feature implementation
@@ -218,205 +196,188 @@ Standard feature implementation workflow
3. Update documentation 3. Update documentation
**Files typically involved**: **Files typically involved**:
- `manifests/*` - `.opencode/*`
- `schemas/*` - `.opencode/plugins/*`
- `.opencode/plugins/lib/*`
- `**/*.test.*` - `**/*.test.*`
- `**/api/**`
**Example commit sequence**: **Example commit sequence**:
``` ```
feat(skills): add documentation-lookup, bun-runtime, nextjs-turbopack; feat(agents): add rust-reviewer feat: install claude-hud plugin (jarrodwatts/claude-hud) (#1041)
docs(skills): align documentation-lookup with CONTRIBUTING template; add cross-harness (Codex/Cursor) skill copies feat: add GAN-style generator-evaluator harness (#1029)
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(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 **Frequency**: ~2 times per month
**Steps**: **Steps**:
1. Create a new directory under rules/{language}/ 1. Ensure tests pass before refactor
2. Add coding-style.md, hooks.md, patterns.md, security.md, and testing.md files with language-specific content 2. Refactor code structure
3. Optionally reference or link to related skills 3. Verify tests still pass
**Files typically involved**: **Files typically involved**:
- `rules/*/coding-style.md` - `src/**/*`
- `rules/*/hooks.md`
- `rules/*/patterns.md`
- `rules/*/security.md`
- `rules/*/testing.md`
**Example commit sequence**: **Example commit sequence**:
``` ```
Create a new directory under rules/{language}/ refactor: collapse legacy command bodies into skills
Add coding-style.md, hooks.md, patterns.md, security.md, and testing.md files with language-specific content feat: add connected operator workflow skills
Optionally reference or link to related skills feat: expand lead intelligence outreach channels
``` ```
### Add New Skill ### 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 **Frequency**: ~4 times per month
**Steps**: **Steps**:
1. Create a new directory under skills/{skill-name}/ 1. Create a new SKILL.md file under skills/ or .agents/skills/ or .claude/skills/
2. Add SKILL.md with documentation (When to Use, How It Works, Examples, etc.) 2. Optionally update documentation (AGENTS.md, README.md, WORKING-CONTEXT.md)
3. Optionally add scripts or supporting files under skills/{skill-name}/scripts/ 3. Optionally add supporting files (e.g., manifests/install-modules.json)
4. Address review feedback and iterate on documentation
**Files typically involved**: **Files typically involved**:
- `skills/*/SKILL.md` - `skills/*/SKILL.md`
- `skills/*/scripts/*.sh` - `.agents/skills/*/SKILL.md`
- `skills/*/scripts/*.js` - `.claude/skills/*/SKILL.md`
**Example commit sequence**: **Example commit sequence**:
``` ```
Create a new directory under skills/{skill-name}/ Create a new SKILL.md file under skills/ or .agents/skills/ or .claude/skills/
Add SKILL.md with documentation (When to Use, How It Works, Examples, etc.) Optionally update documentation (AGENTS.md, README.md, WORKING-CONTEXT.md)
Optionally add scripts or supporting files under skills/{skill-name}/scripts/ Optionally add supporting files (e.g., manifests/install-modules.json)
Address review feedback and iterate on documentation
``` ```
### 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 **Frequency**: ~2 times per month
**Steps**: **Steps**:
1. Create a new agent markdown file under agents/{agent-name}.md 1. Add or update agent definition file (e.g., agents/*.md or .opencode/prompts/agents/*.txt)
2. Register the agent in AGENTS.md 2. Update agent registry/configuration (e.g., .opencode/opencode.json, AGENTS.md)
3. Optionally update README.md and docs/COMMAND-AGENT-MAP.md
**Files typically involved**: **Files typically involved**:
- `agents/*.md` - `agents/*.md`
- `.opencode/prompts/agents/*.txt`
- `.opencode/opencode.json`
- `AGENTS.md` - `AGENTS.md`
- `README.md`
- `docs/COMMAND-AGENT-MAP.md`
**Example commit sequence**: **Example commit sequence**:
``` ```
Create a new agent markdown file under agents/{agent-name}.md Add or update agent definition file (e.g., agents/*.md or .opencode/prompts/agents/*.txt)
Register the agent in AGENTS.md Update agent registry/configuration (e.g., .opencode/opencode.json, AGENTS.md)
Optionally update README.md and docs/COMMAND-AGENT-MAP.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**: **Steps**:
1. Create a new markdown file under commands/{command-name}.md 1. Create or update command markdown file under commands/
2. Optionally add or update a backing skill under skills/{skill-name}/SKILL.md 2. Optionally update documentation or index files
**Files typically involved**: **Files typically involved**:
- `commands/*.md` - `commands/*.md`
- `skills/*/SKILL.md`
**Example commit sequence**: **Example commit sequence**:
``` ```
Create a new markdown file under commands/{command-name}.md Create or update command markdown file under commands/
Optionally add or update a backing skill under skills/{skill-name}/SKILL.md 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 **Frequency**: ~3 times per month
**Steps**: **Steps**:
1. Update agent, skill, and command counts in AGENTS.md 1. Edit documentation files (README.md, AGENTS.md, WORKING-CONTEXT.md, docs/...)
2. Update the same counts in README.md (quick-start, comparison table, etc.) 2. Optionally update or add new guidance files
3. Optionally update other documentation files
**Files typically involved**: **Files typically involved**:
- `AGENTS.md`
- `README.md` - `README.md`
- `AGENTS.md`
- `WORKING-CONTEXT.md`
- `docs/**/*.md`
**Example commit sequence**: **Example commit sequence**:
``` ```
Update agent, skill, and command counts in AGENTS.md Edit documentation files (README.md, AGENTS.md, WORKING-CONTEXT.md, docs/...)
Update the same counts in README.md (quick-start, comparison table, etc.) Optionally update or add new guidance files
Optionally update other documentation 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 **Frequency**: ~2 times per month
**Steps**: **Steps**:
1. Copy or adapt SKILL.md to .agents/skills/{skill}/SKILL.md and/or .cursor/skills/{skill}/SKILL.md 1. Edit package.json, yarn.lock, or other lockfiles
2. Optionally add harness-specific openai.yaml or config files 2. Edit schema files under schemas/
3. Address review feedback to align with CONTRIBUTING template 3. Optionally update related scripts or manifests
**Files typically involved**: **Files typically involved**:
- `.agents/skills/*/SKILL.md` - `package.json`
- `.cursor/skills/*/SKILL.md` - `yarn.lock`
- `.agents/skills/*/agents/openai.yaml` - `schemas/*.json`
**Example commit sequence**: **Example commit sequence**:
``` ```
Copy or adapt SKILL.md to .agents/skills/{skill}/SKILL.md and/or .cursor/skills/{skill}/SKILL.md Edit package.json, yarn.lock, or other lockfiles
Optionally add harness-specific openai.yaml or config files Edit schema files under schemas/
Address review feedback to align with CONTRIBUTING template 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**: **Steps**:
1. Add or update hook scripts in hooks/ or scripts/hooks/ 1. Edit workflow files under .github/workflows/
2. Register the hook in hooks/hooks.json or similar config
3. Optionally add or update tests in tests/hooks/
**Files typically involved**: **Files typically involved**:
- `hooks/*.hook` - `.github/workflows/*.yml`
- `hooks/hooks.json`
- `scripts/hooks/*.js`
- `tests/hooks/*.test.js`
- `.cursor/hooks.json`
**Example commit sequence**: **Example commit sequence**:
``` ```
Add or update hook scripts in hooks/ or scripts/hooks/ Edit workflow files under .github/workflows/
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
``` ```