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

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

Browse Source
This commit is contained in:
ecc-tools[bot]
2026-04-01 04:43:41 +00:00
committed by GitHub
parent 8f152b9998
commit 6dfb99043e
1 changed files with 121 additions and 214 deletions
Download Patch File Download Diff File Expand all files Collapse all files

335
.agents/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-or-update-command.md)
``` ```
*Commit message example* *Commit message example*
```text ```text
chore(deps-dev): bump flatted (#675) fix: update ecc2 ratatui dependency
``` ```
*Commit message example* *Commit message example*
```text ```text
fix: auto-detect ECC root from plugin cache when CLAUDE_PLUGIN_ROOT is unset (#547) (#691) docs: tighten pr backlog classification
``` ```
*Commit message example* *Commit message example*
```text ```text
docs: add Antigravity setup and usage guide (#552) refactor: fold social graph ranking into lead intelligence
``` ```
*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/add-new-agent-or-skill.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**: ~20 times per month
**Steps**: **Steps**:
1. Add feature implementation 1. Add feature implementation
@@ -218,205 +196,134 @@ 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(team-builder): use `claude agents` command for agent discovery (#1021)
docs(skills): align documentation-lookup with CONTRIBUTING template; add cross-harness (Codex/Cursor) skill copies fix: extract inline SessionStart bootstrap to separate file (#1035)
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 hexagonal architecture SKILL. (#1034)
``` ```
### Add Language Rules ### Add New Skill Or Agent
Adds a new programming language to the rules system, including coding style, hooks, patterns, security, and testing guidelines. Adds a new agent or skill to the codebase, including documentation and configuration.
**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.
**Frequency**: ~3 times per month **Frequency**: ~3 times per month
**Steps**: **Steps**:
1. Update agent, skill, and command counts in AGENTS.md 1. Create a new SKILL.md or agent markdown file in the appropriate directory (skills/ or agents/).
2. Update the same counts in README.md (quick-start, comparison table, etc.) 2. Optionally add supporting files such as YAML configs or example usage.
3. Optionally update other documentation files 3. Update relevant index or manifest files if needed.
**Files typically involved**:
- `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
```
### Add Cross Harness Skill Copies
Adds skill copies for different agent harnesses (e.g., Codex, Cursor, Antigravity) to ensure compatibility across platforms.
**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
**Files typically involved**:
- `.agents/skills/*/SKILL.md`
- `.cursor/skills/*/SKILL.md`
- `.agents/skills/*/agents/openai.yaml`
**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 Or Update Hook
Adds or updates git or bash hooks to enforce workflow, quality, or security policies.
**Frequency**: ~1 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/
**Files typically involved**:
- `hooks/*.hook`
- `hooks/hooks.json`
- `scripts/hooks/*.js`
- `tests/hooks/*.test.js`
- `.cursor/hooks.json`
**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**: **Files typically involved**:
- `skills/*/SKILL.md` - `skills/*/SKILL.md`
- `agents/*.md` - `agents/*.md`
- `commands/*.md`
- `.agents/skills/*/SKILL.md` - `.agents/skills/*/SKILL.md`
- `.cursor/skills/*/SKILL.md` - `.claude/skills/*/SKILL.md`
**Example commit sequence**: **Example commit sequence**:
``` ```
Edit SKILL.md, agent, or command files to address reviewer comments Create a new SKILL.md or agent markdown file in the appropriate directory (skills/ or agents/).
Update examples, headings, or configuration as requested Optionally add supporting files such as YAML configs or example usage.
Iterate until all review feedback is resolved Update relevant index or manifest files if needed.
```
### Add Or Update Command
Adds or updates a command markdown file, defining new CLI commands or workflows.
**Frequency**: ~2 times per month
**Steps**:
1. Create or update a markdown file in the commands/ or .claude/commands/ directory.
2. Document the command's usage, arguments, and output.
3. Optionally update related documentation or index files.
**Files typically involved**:
- `commands/*.md`
- `.claude/commands/*.md`
**Example commit sequence**:
```
Create or update a markdown file in the commands/ or .claude/commands/ directory.
Document the command's usage, arguments, and output.
Optionally update related documentation or index files.
```
### Add Or Update Install Target
Adds or updates an install target, including scripts, schemas, and manifest entries for new integrations.
**Frequency**: ~2 times per month
**Steps**:
1. Add new install scripts (e.g., install.sh, install.js) in a dedicated directory.
2. Update manifests/install-modules.json and relevant schema files.
3. Update or add code in scripts/lib/install-manifests.js and install-targets/*.
4. Add or update tests for install targets.
**Files typically involved**:
- `manifests/install-modules.json`
- `schemas/ecc-install-config.schema.json`
- `schemas/install-modules.schema.json`
- `scripts/lib/install-manifests.js`
- `scripts/lib/install-targets/*.js`
- `tests/lib/install-targets.test.js`
- `.*/install.*`
**Example commit sequence**:
```
Add new install scripts (e.g., install.sh, install.js) in a dedicated directory.
Update manifests/install-modules.json and relevant schema files.
Update or add code in scripts/lib/install-manifests.js and install-targets/*.
Add or update tests for install targets.
```
### Update Hooks Or Hook Scripts
Updates hook configuration or scripts to change automation, formatting, or session management behaviors.
**Frequency**: ~3 times per month
**Steps**:
1. Edit hooks/hooks.json to add or modify hook definitions.
2. Update or add scripts in scripts/hooks/ or tests/hooks/.
3. Optionally update related shell scripts or adapters.
**Files typically involved**:
- `hooks/hooks.json`
- `scripts/hooks/*.js`
- `scripts/hooks/*.sh`
- `tests/hooks/*.test.js`
**Example commit sequence**:
```
Edit hooks/hooks.json to add or modify hook definitions.
Update or add scripts in scripts/hooks/ or tests/hooks/.
Optionally update related shell scripts or adapters.
```
### Dependency Bump Github Actions
Automated or manual updates to GitHub Actions dependencies for CI/CD workflows.
**Frequency**: ~4 times per month
**Steps**:
1. Update version numbers in .github/workflows/*.yml files for specific actions.
2. Commit with a standardized message indicating the dependency and new version.
**Files typically involved**:
- `.github/workflows/*.yml`
**Example commit sequence**:
```
Update version numbers in .github/workflows/*.yml files for specific actions.
Commit with a standardized message indicating the dependency and new version.
``` ```