Compare commits

..

15 Commits

Author SHA1 Message Date
ecc-tools[bot]
179d1e4ca5 feat: add everything-claude-code-conventions ECC bundle (.claude/commands/add-new-skill.md) 2026-04-01 22:51:20 +00:00
ecc-tools[bot]
db49085cb1 feat: add everything-claude-code-conventions ECC bundle (.claude/commands/refactoring.md) 2026-04-01 22:51:19 +00:00
ecc-tools[bot]
e044007d29 feat: add everything-claude-code-conventions ECC bundle (.claude/commands/feature-development.md) 2026-04-01 22:51:18 +00:00
ecc-tools[bot]
6abc110793 feat: add everything-claude-code-conventions ECC bundle (.claude/enterprise/controls.md) 2026-04-01 22:51:18 +00:00
ecc-tools[bot]
f0ed07ed82 feat: add everything-claude-code-conventions ECC bundle (.claude/team/everything-claude-code-team-config.json) 2026-04-01 22:51:17 +00:00
ecc-tools[bot]
a90b855d4d feat: add everything-claude-code-conventions ECC bundle (.claude/research/everything-claude-code-research-playbook.md) 2026-04-01 22:51:16 +00:00
ecc-tools[bot]
1c53accde5 feat: add everything-claude-code-conventions ECC bundle (.claude/rules/everything-claude-code-guardrails.md) 2026-04-01 22:51:15 +00:00
ecc-tools[bot]
64684a64e6 feat: add everything-claude-code-conventions ECC bundle (.codex/agents/docs-researcher.toml) 2026-04-01 22:51:14 +00:00
ecc-tools[bot]
fe50d68257 feat: add everything-claude-code-conventions ECC bundle (.codex/agents/reviewer.toml) 2026-04-01 22:51:13 +00:00
ecc-tools[bot]
306b48245f feat: add everything-claude-code-conventions ECC bundle (.codex/agents/explorer.toml) 2026-04-01 22:51:12 +00:00
ecc-tools[bot]
8f058ea0c5 feat: add everything-claude-code-conventions ECC bundle (.claude/identity.json) 2026-04-01 22:51:11 +00:00
ecc-tools[bot]
b781af2d4d feat: add everything-claude-code-conventions ECC bundle (.agents/skills/everything-claude-code/agents/openai.yaml) 2026-04-01 22:51:11 +00:00
ecc-tools[bot]
ea96178ac1 feat: add everything-claude-code-conventions ECC bundle (.agents/skills/everything-claude-code/SKILL.md) 2026-04-01 22:51:10 +00:00
ecc-tools[bot]
0e63bb37de feat: add everything-claude-code-conventions ECC bundle (.claude/skills/everything-claude-code/SKILL.md) 2026-04-01 22:51:09 +00:00
ecc-tools[bot]
03dfdd2fa0 feat: add everything-claude-code-conventions ECC bundle (.claude/ecc-tools.json) 2026-04-01 22:51:08 +00:00
11 changed files with 378 additions and 401 deletions

View File

@@ -40,7 +40,7 @@ Follow these commit message conventions based on 500 analyzed commits.
### Message Guidelines
- Average message length: ~56 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
refactor: simplify redundant checks; normalize getInstalledPlugin inputs
feat: add everything-claude-code ECC bundle (.claude/commands/add-new-skill.md)
```
*Commit message example*
```text
fix: preserve file permissions in writeJsonAtomic
refactor: collapse legacy command bodies into skills
```
*Commit message example*
```text
style: apply linter formatting to pluginRegistry.js
fix: dedupe managed hooks by semantic identity
```
*Commit message example*
```text
chore: update yarn.lock
docs: close bundle drift and sync plugin guidance
```
*Commit message example*
```text
feat(plugin): add marketplace add/install system
chore: ignore local orchestration artifacts
```
*Commit message example*
```text
fix: ship marketplaces.json as empty stub to prevent duplicate-add error
feat: add everything-claude-code ECC bundle (.claude/commands/refactoring.md)
```
*Commit message example*
```text
fix: normalize lookups, atomic writes, reject empty marketplace specifier
feat: add everything-claude-code ECC bundle (.claude/commands/feature-development.md)
```
*Commit message example*
```text
refactor: extract shared readJsonFile helper; fix single-dash flag parsing
feat: add everything-claude-code ECC bundle (.claude/enterprise/controls.md)
```
## Architecture
@@ -188,7 +188,7 @@ These workflows were detected from analyzing commit patterns.
Standard feature implementation workflow
**Frequency**: ~14 times per month
**Frequency**: ~19 times per month
**Steps**:
1. Add feature implementation
@@ -203,187 +203,181 @@ Standard feature implementation workflow
**Example commit sequence**:
```
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)
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 New Command Or Agentic Workflow
### Refactoring
Adds a new command or agentic workflow to the system, often including new .md command files, agent definitions, and skill orchestrators.
Code refactoring and cleanup workflow
**Frequency**: ~3 times per month
**Frequency**: ~2 times per month
**Steps**:
1. Create one or more new command markdown files in commands/ (e.g., gan-build.md, santa-loop.md, prp-*.md)
2. Add or update agent definitions in agents/ (e.g., gan-generator.md, opensource-forker.md)
3. Add or update skill orchestrator in skills/ (e.g., skills/gan-style-harness/SKILL.md, skills/opensource-pipeline/SKILL.md)
4. Optionally add shell orchestrators or scripts (e.g., scripts/gan-harness.sh)
5. Optionally add documentation or examples
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 skill to the repository, enabling new agent capabilities or workflows.
**Frequency**: ~4 times per month
**Steps**:
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`
- `.agents/skills/*/SKILL.md`
- `.claude/skills/*/SKILL.md`
**Example commit sequence**:
```
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 Or Update Agent
Adds or updates agent definitions and registers them in configuration files.
**Frequency**: ~2 times per month
**Steps**:
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`
**Example commit sequence**:
```
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 Or Update Command
Adds or updates command workflow files for agentic operations.
**Frequency**: ~2 times per month
**Steps**:
1. Create or update command markdown file under commands/
2. Optionally update documentation or index files
**Files typically involved**:
- `commands/*.md`
**Example commit sequence**:
```
Create or update command markdown file under commands/
Optionally update documentation or index files
```
### Feature Or Skill Bundle
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**:
```
Create one or more new command markdown files in commands/ (e.g., gan-build.md, santa-loop.md, prp-*.md)
Add or update agent definitions in agents/ (e.g., gan-generator.md, opensource-forker.md)
Add or update skill orchestrator in skills/ (e.g., skills/gan-style-harness/SKILL.md, skills/opensource-pipeline/SKILL.md)
Optionally add shell orchestrators or scripts (e.g., scripts/gan-harness.sh)
Optionally add documentation or examples
Add multiple agent and/or skill files
Add supporting commands and scripts
Add or update documentation and examples
```
### Add Or Update Plugin Marketplace System
### Documentation Update
Implements or refines the plugin marketplace system, including registry helpers, CLI scripts, JSON stubs, and documentation.
Updates documentation to reflect new features, workflows, or guidance.
**Frequency**: ~2 times per month
**Frequency**: ~3 times per month
**Steps**:
1. Edit or create scripts/lib/pluginRegistry.js for registry helpers
2. Edit or create scripts/pluginMarketplace.js and/or scripts/pluginInstall.js for CLI commands
3. Edit .claude-plugin/marketplaces.json and/or .claude-plugin/installed-plugins.json as stubs or for schema changes
4. Update or add tests in tests/lib/pluginRegistry.test.js
5. Update or create documentation in commands/plugin-marketplace.md and/or commands/plugin-install.md
6. Optionally update root docs (README.md, AGENTS.md, etc.)
1. Edit documentation files (README.md, AGENTS.md, WORKING-CONTEXT.md, docs/...)
2. Optionally update or add new guidance files
**Files typically involved**:
- `scripts/lib/pluginRegistry.js`
- `scripts/pluginMarketplace.js`
- `scripts/pluginInstall.js`
- `.claude-plugin/marketplaces.json`
- `.claude-plugin/installed-plugins.json`
- `tests/lib/pluginRegistry.test.js`
- `commands/plugin-marketplace.md`
- `commands/plugin-install.md`
- `README.md`
- `AGENTS.md`
- `WORKING-CONTEXT.md`
- `docs/**/*.md`
**Example commit sequence**:
```
Edit or create scripts/lib/pluginRegistry.js for registry helpers
Edit or create scripts/pluginMarketplace.js and/or scripts/pluginInstall.js for CLI commands
Edit .claude-plugin/marketplaces.json and/or .claude-plugin/installed-plugins.json as stubs or for schema changes
Update or add tests in tests/lib/pluginRegistry.test.js
Update or create documentation in commands/plugin-marketplace.md and/or commands/plugin-install.md
Optionally update root docs (README.md, AGENTS.md, etc.)
Edit documentation files (README.md, AGENTS.md, WORKING-CONTEXT.md, docs/...)
Optionally update or add new guidance files
```
### Add New Install Target Or Adaptation
### Dependency Or Schema Update
Adds a new install target (e.g., Gemini, CodeBuddy) to the system, including scripts, schemas, and tests.
Updates dependencies or schema files, often in response to new features or external updates.
**Frequency**: ~2 times per month
**Steps**:
1. Add new install scripts and docs under a dedicated directory (e.g., .gemini/, .codebuddy/)
2. Update manifests/install-modules.json to register the new target
3. Update or add schema files (schemas/ecc-install-config.schema.json, schemas/install-modules.schema.json)
4. Edit or add scripts/lib/install-manifests.js and scripts/lib/install-targets/*.js for logic
5. Add or update tests in tests/lib/install-targets.test.js
6. Update documentation (README.md, .gemini/GEMINI.md, etc.)
**Files typically involved**:
- `.gemini/*`
- `.codebuddy/*`
- `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`
- `README.md`
**Example commit sequence**:
```
Add new install scripts and docs under a dedicated directory (e.g., .gemini/, .codebuddy/)
Update manifests/install-modules.json to register the new target
Update or add schema files (schemas/ecc-install-config.schema.json, schemas/install-modules.schema.json)
Edit or add scripts/lib/install-manifests.js and scripts/lib/install-targets/*.js for logic
Add or update tests in tests/lib/install-targets.test.js
Update documentation (README.md, .gemini/GEMINI.md, etc.)
```
### Add Or Update Hook Or Session Management
Implements or refines hooks and session management logic, including accumulator patterns, session start/end, and related tests.
**Frequency**: ~2 times per month
**Steps**:
1. Edit or create scripts/hooks/*.js for hook logic (e.g., post-edit-accumulator.js, stop-format-typecheck.js, session-start.js)
2. Update hooks/hooks.json for hook configuration
3. Add or update tests in tests/hooks/*.test.js
4. Optionally update shell scripts (scripts/hooks/*.sh)
5. Optionally update adapters (.cursor/hooks/after-file-edit.js)
**Files typically involved**:
- `scripts/hooks/*.js`
- `hooks/hooks.json`
- `tests/hooks/*.test.js`
- `scripts/hooks/*.sh`
- `.cursor/hooks/after-file-edit.js`
**Example commit sequence**:
```
Edit or create scripts/hooks/*.js for hook logic (e.g., post-edit-accumulator.js, stop-format-typecheck.js, session-start.js)
Update hooks/hooks.json for hook configuration
Add or update tests in tests/hooks/*.test.js
Optionally update shell scripts (scripts/hooks/*.sh)
Optionally update adapters (.cursor/hooks/after-file-edit.js)
```
### Add Or Update Skill Or Agent
Adds or updates a skill or agent definition, often including a new SKILL.md and/or agent .md, sometimes with supporting config.
**Frequency**: ~2 times per month
**Steps**:
1. Create or edit skills/*/SKILL.md
2. Create or edit agents/*.md
3. Optionally update mcp-configs/mcp-servers.json or other config files
4. Optionally update AGENTS.md or related documentation
**Files typically involved**:
- `skills/*/SKILL.md`
- `agents/*.md`
- `mcp-configs/mcp-servers.json`
- `AGENTS.md`
**Example commit sequence**:
```
Create or edit skills/*/SKILL.md
Create or edit agents/*.md
Optionally update mcp-configs/mcp-servers.json or other config files
Optionally update AGENTS.md or related documentation
```
### Dependabot Or Automated Dependency Update
Automated workflow to update dependencies via Dependabot or similar, touching lockfiles and workflow YAMLs.
**Frequency**: ~4 times per month
**Steps**:
1. Update package.json and/or yarn.lock
2. Update .github/workflows/*.yml as needed for new dependency versions
3. Commit with a standardized message referencing the dependency and version
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**:
- `package.json`
- `yarn.lock`
- `schemas/*.json`
**Example commit sequence**:
```
Edit package.json, yarn.lock, or other lockfiles
Edit schema files under schemas/
Optionally update related scripts or manifests
```
### Ci Cd Workflow Update
Updates CI/CD workflow files, usually for dependency bumps or workflow improvements.
**Frequency**: ~2 times per month
**Steps**:
1. Edit workflow files under .github/workflows/
**Files typically involved**:
- `.github/workflows/*.yml`
**Example commit sequence**:
```
Update package.json and/or yarn.lock
Update .github/workflows/*.yml as needed for new dependency versions
Commit with a standardized message referencing the dependency and version
Edit workflow files under .github/workflows/
```

View File

@@ -1,41 +0,0 @@
---
name: add-new-command-or-agentic-workflow
description: Workflow command scaffold for add-new-command-or-agentic-workflow in everything-claude-code.
allowed_tools: ["Bash", "Read", "Write", "Grep", "Glob"]
---
# /add-new-command-or-agentic-workflow
Use this workflow when working on **add-new-command-or-agentic-workflow** in `everything-claude-code`.
## Goal
Adds a new command or agentic workflow to the system, often including new .md command files, agent definitions, and skill orchestrators.
## Common Files
- `commands/*.md`
- `agents/*.md`
- `skills/*/SKILL.md`
- `scripts/*.sh`
- `examples/*`
## Suggested Sequence
1. Understand the current state and failure mode before editing.
2. Make the smallest coherent change that satisfies the workflow goal.
3. Run the most relevant verification for touched files.
4. Summarize what changed and what still needs review.
## Typical Commit Signals
- Create one or more new command markdown files in commands/ (e.g., gan-build.md, santa-loop.md, prp-*.md)
- Add or update agent definitions in agents/ (e.g., gan-generator.md, opensource-forker.md)
- Add or update skill orchestrator in skills/ (e.g., skills/gan-style-harness/SKILL.md, skills/opensource-pipeline/SKILL.md)
- Optionally add shell orchestrators or scripts (e.g., scripts/gan-harness.sh)
- Optionally add documentation or examples
## Notes
- Treat this as a scaffold, not a hard-coded script.
- Update the command if the workflow evolves materially.

View File

@@ -0,0 +1,37 @@
---
name: add-new-skill
description: Workflow command scaffold for add-new-skill in everything-claude-code.
allowed_tools: ["Bash", "Read", "Write", "Grep", "Glob"]
---
# /add-new-skill
Use this workflow when working on **add-new-skill** in `everything-claude-code`.
## Goal
Adds a new skill to the repository, enabling new agent capabilities or workflows.
## Common Files
- `skills/*/SKILL.md`
- `.agents/skills/*/SKILL.md`
- `.claude/skills/*/SKILL.md`
## Suggested Sequence
1. Understand the current state and failure mode before editing.
2. Make the smallest coherent change that satisfies the workflow goal.
3. Run the most relevant verification for touched files.
4. Summarize what changed and what still needs review.
## Typical Commit Signals
- 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)
## Notes
- Treat this as a scaffold, not a hard-coded script.
- Update the command if the workflow evolves materially.

View File

@@ -1,42 +0,0 @@
---
name: add-or-update-plugin-marketplace-system
description: Workflow command scaffold for add-or-update-plugin-marketplace-system in everything-claude-code.
allowed_tools: ["Bash", "Read", "Write", "Grep", "Glob"]
---
# /add-or-update-plugin-marketplace-system
Use this workflow when working on **add-or-update-plugin-marketplace-system** in `everything-claude-code`.
## Goal
Implements or refines the plugin marketplace system, including registry helpers, CLI scripts, JSON stubs, and documentation.
## Common Files
- `scripts/lib/pluginRegistry.js`
- `scripts/pluginMarketplace.js`
- `scripts/pluginInstall.js`
- `.claude-plugin/marketplaces.json`
- `.claude-plugin/installed-plugins.json`
- `tests/lib/pluginRegistry.test.js`
## Suggested Sequence
1. Understand the current state and failure mode before editing.
2. Make the smallest coherent change that satisfies the workflow goal.
3. Run the most relevant verification for touched files.
4. Summarize what changed and what still needs review.
## Typical Commit Signals
- Edit or create scripts/lib/pluginRegistry.js for registry helpers
- Edit or create scripts/pluginMarketplace.js and/or scripts/pluginInstall.js for CLI commands
- Edit .claude-plugin/marketplaces.json and/or .claude-plugin/installed-plugins.json as stubs or for schema changes
- Update or add tests in tests/lib/pluginRegistry.test.js
- Update or create documentation in commands/plugin-marketplace.md and/or commands/plugin-install.md
## Notes
- Treat this as a scaffold, not a hard-coded script.
- Update the command if the workflow evolves materially.

View File

@@ -0,0 +1,35 @@
---
name: refactoring
description: Workflow command scaffold for refactoring in everything-claude-code.
allowed_tools: ["Bash", "Read", "Write", "Grep", "Glob"]
---
# /refactoring
Use this workflow when working on **refactoring** in `everything-claude-code`.
## Goal
Code refactoring and cleanup workflow
## Common Files
- `src/**/*`
## Suggested Sequence
1. Understand the current state and failure mode before editing.
2. Make the smallest coherent change that satisfies the workflow goal.
3. Run the most relevant verification for touched files.
4. Summarize what changed and what still needs review.
## Typical Commit Signals
- Ensure tests pass before refactor
- Refactor code structure
- Verify tests still pass
## Notes
- Treat this as a scaffold, not a hard-coded script.
- Update the command if the workflow evolves materially.

View File

@@ -2,7 +2,7 @@
"version": "1.3",
"schemaVersion": "1.0",
"generatedBy": "ecc-tools",
"generatedAt": "2026-04-01T22:56:13.232Z",
"generatedAt": "2026-04-01T22:44:14.561Z",
"repo": "https://github.com/affaan-m/everything-claude-code",
"profiles": {
"requested": "full",
@@ -149,8 +149,8 @@
".claude/team/everything-claude-code-team-config.json",
".claude/enterprise/controls.md",
".claude/commands/feature-development.md",
".claude/commands/add-new-command-or-agentic-workflow.md",
".claude/commands/add-or-update-plugin-marketplace-system.md"
".claude/commands/refactoring.md",
".claude/commands/add-new-skill.md"
],
"packageFiles": {
"runtime-core": [
@@ -179,8 +179,8 @@
],
"workflow-pack": [
".claude/commands/feature-development.md",
".claude/commands/add-new-command-or-agentic-workflow.md",
".claude/commands/add-or-update-plugin-marketplace-system.md"
".claude/commands/refactoring.md",
".claude/commands/add-new-skill.md"
]
},
"moduleFiles": {
@@ -210,8 +210,8 @@
],
"workflow-pack": [
".claude/commands/feature-development.md",
".claude/commands/add-new-command-or-agentic-workflow.md",
".claude/commands/add-or-update-plugin-marketplace-system.md"
".claude/commands/refactoring.md",
".claude/commands/add-new-skill.md"
]
},
"files": [
@@ -292,13 +292,13 @@
},
{
"moduleId": "workflow-pack",
"path": ".claude/commands/add-new-command-or-agentic-workflow.md",
"description": "Workflow command scaffold for add-new-command-or-agentic-workflow."
"path": ".claude/commands/refactoring.md",
"description": "Workflow command scaffold for refactoring."
},
{
"moduleId": "workflow-pack",
"path": ".claude/commands/add-or-update-plugin-marketplace-system.md",
"description": "Workflow command scaffold for add-or-update-plugin-marketplace-system."
"path": ".claude/commands/add-new-skill.md",
"description": "Workflow command scaffold for add-new-skill."
}
],
"workflows": [
@@ -307,12 +307,12 @@
"path": ".claude/commands/feature-development.md"
},
{
"command": "add-new-command-or-agentic-workflow",
"path": ".claude/commands/add-new-command-or-agentic-workflow.md"
"command": "refactoring",
"path": ".claude/commands/refactoring.md"
},
{
"command": "add-or-update-plugin-marketplace-system",
"path": ".claude/commands/add-or-update-plugin-marketplace-system.md"
"command": "add-new-skill",
"path": ".claude/commands/add-new-skill.md"
}
],
"adapters": {
@@ -321,8 +321,8 @@
"identityPath": ".claude/identity.json",
"commandPaths": [
".claude/commands/feature-development.md",
".claude/commands/add-new-command-or-agentic-workflow.md",
".claude/commands/add-or-update-plugin-marketplace-system.md"
".claude/commands/refactoring.md",
".claude/commands/add-new-skill.md"
]
},
"codex": {

View File

@@ -10,5 +10,5 @@
"javascript"
],
"suggestedBy": "ecc-tools-repo-analysis",
"createdAt": "2026-04-01T22:56:57.484Z"
"createdAt": "2026-04-01T22:51:05.478Z"
}

View File

@@ -18,4 +18,4 @@ Use this when the task is documentation-heavy, source-sensitive, or requires bro
- Primary language: JavaScript
- Framework: Not detected
- Workflows detected: 7
- Workflows detected: 9

View File

@@ -25,8 +25,8 @@ Generated by ECC Tools from repository history. Review before treating it as a h
## Detected Workflows
- feature-development: Standard feature implementation workflow
- add-new-command-or-agentic-workflow: Adds a new command or agentic workflow to the system, often including new .md command files, agent definitions, and skill orchestrators.
- add-or-update-plugin-marketplace-system: Implements or refines the plugin marketplace system, including registry helpers, CLI scripts, JSON stubs, and documentation.
- refactoring: Code refactoring and cleanup workflow
- add-new-skill: Adds a new skill to the repository, enabling new agent capabilities or workflows.
## Review Reminder

View File

@@ -40,7 +40,7 @@ Follow these commit message conventions based on 500 analyzed commits.
### Message Guidelines
- Average message length: ~56 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
refactor: simplify redundant checks; normalize getInstalledPlugin inputs
feat: add everything-claude-code ECC bundle (.claude/commands/add-new-skill.md)
```
*Commit message example*
```text
fix: preserve file permissions in writeJsonAtomic
refactor: collapse legacy command bodies into skills
```
*Commit message example*
```text
style: apply linter formatting to pluginRegistry.js
fix: dedupe managed hooks by semantic identity
```
*Commit message example*
```text
chore: update yarn.lock
docs: close bundle drift and sync plugin guidance
```
*Commit message example*
```text
feat(plugin): add marketplace add/install system
chore: ignore local orchestration artifacts
```
*Commit message example*
```text
fix: ship marketplaces.json as empty stub to prevent duplicate-add error
feat: add everything-claude-code ECC bundle (.claude/commands/refactoring.md)
```
*Commit message example*
```text
fix: normalize lookups, atomic writes, reject empty marketplace specifier
feat: add everything-claude-code ECC bundle (.claude/commands/feature-development.md)
```
*Commit message example*
```text
refactor: extract shared readJsonFile helper; fix single-dash flag parsing
feat: add everything-claude-code ECC bundle (.claude/enterprise/controls.md)
```
## Architecture
@@ -188,7 +188,7 @@ These workflows were detected from analyzing commit patterns.
Standard feature implementation workflow
**Frequency**: ~14 times per month
**Frequency**: ~19 times per month
**Steps**:
1. Add feature implementation
@@ -203,187 +203,181 @@ Standard feature implementation workflow
**Example commit sequence**:
```
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)
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 New Command Or Agentic Workflow
### Refactoring
Adds a new command or agentic workflow to the system, often including new .md command files, agent definitions, and skill orchestrators.
Code refactoring and cleanup workflow
**Frequency**: ~3 times per month
**Frequency**: ~2 times per month
**Steps**:
1. Create one or more new command markdown files in commands/ (e.g., gan-build.md, santa-loop.md, prp-*.md)
2. Add or update agent definitions in agents/ (e.g., gan-generator.md, opensource-forker.md)
3. Add or update skill orchestrator in skills/ (e.g., skills/gan-style-harness/SKILL.md, skills/opensource-pipeline/SKILL.md)
4. Optionally add shell orchestrators or scripts (e.g., scripts/gan-harness.sh)
5. Optionally add documentation or examples
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 skill to the repository, enabling new agent capabilities or workflows.
**Frequency**: ~4 times per month
**Steps**:
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`
- `.agents/skills/*/SKILL.md`
- `.claude/skills/*/SKILL.md`
**Example commit sequence**:
```
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 Or Update Agent
Adds or updates agent definitions and registers them in configuration files.
**Frequency**: ~2 times per month
**Steps**:
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`
**Example commit sequence**:
```
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 Or Update Command
Adds or updates command workflow files for agentic operations.
**Frequency**: ~2 times per month
**Steps**:
1. Create or update command markdown file under commands/
2. Optionally update documentation or index files
**Files typically involved**:
- `commands/*.md`
**Example commit sequence**:
```
Create or update command markdown file under commands/
Optionally update documentation or index files
```
### Feature Or Skill Bundle
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**:
```
Create one or more new command markdown files in commands/ (e.g., gan-build.md, santa-loop.md, prp-*.md)
Add or update agent definitions in agents/ (e.g., gan-generator.md, opensource-forker.md)
Add or update skill orchestrator in skills/ (e.g., skills/gan-style-harness/SKILL.md, skills/opensource-pipeline/SKILL.md)
Optionally add shell orchestrators or scripts (e.g., scripts/gan-harness.sh)
Optionally add documentation or examples
Add multiple agent and/or skill files
Add supporting commands and scripts
Add or update documentation and examples
```
### Add Or Update Plugin Marketplace System
### Documentation Update
Implements or refines the plugin marketplace system, including registry helpers, CLI scripts, JSON stubs, and documentation.
Updates documentation to reflect new features, workflows, or guidance.
**Frequency**: ~2 times per month
**Frequency**: ~3 times per month
**Steps**:
1. Edit or create scripts/lib/pluginRegistry.js for registry helpers
2. Edit or create scripts/pluginMarketplace.js and/or scripts/pluginInstall.js for CLI commands
3. Edit .claude-plugin/marketplaces.json and/or .claude-plugin/installed-plugins.json as stubs or for schema changes
4. Update or add tests in tests/lib/pluginRegistry.test.js
5. Update or create documentation in commands/plugin-marketplace.md and/or commands/plugin-install.md
6. Optionally update root docs (README.md, AGENTS.md, etc.)
1. Edit documentation files (README.md, AGENTS.md, WORKING-CONTEXT.md, docs/...)
2. Optionally update or add new guidance files
**Files typically involved**:
- `scripts/lib/pluginRegistry.js`
- `scripts/pluginMarketplace.js`
- `scripts/pluginInstall.js`
- `.claude-plugin/marketplaces.json`
- `.claude-plugin/installed-plugins.json`
- `tests/lib/pluginRegistry.test.js`
- `commands/plugin-marketplace.md`
- `commands/plugin-install.md`
- `README.md`
- `AGENTS.md`
- `WORKING-CONTEXT.md`
- `docs/**/*.md`
**Example commit sequence**:
```
Edit or create scripts/lib/pluginRegistry.js for registry helpers
Edit or create scripts/pluginMarketplace.js and/or scripts/pluginInstall.js for CLI commands
Edit .claude-plugin/marketplaces.json and/or .claude-plugin/installed-plugins.json as stubs or for schema changes
Update or add tests in tests/lib/pluginRegistry.test.js
Update or create documentation in commands/plugin-marketplace.md and/or commands/plugin-install.md
Optionally update root docs (README.md, AGENTS.md, etc.)
Edit documentation files (README.md, AGENTS.md, WORKING-CONTEXT.md, docs/...)
Optionally update or add new guidance files
```
### Add New Install Target Or Adaptation
### Dependency Or Schema Update
Adds a new install target (e.g., Gemini, CodeBuddy) to the system, including scripts, schemas, and tests.
Updates dependencies or schema files, often in response to new features or external updates.
**Frequency**: ~2 times per month
**Steps**:
1. Add new install scripts and docs under a dedicated directory (e.g., .gemini/, .codebuddy/)
2. Update manifests/install-modules.json to register the new target
3. Update or add schema files (schemas/ecc-install-config.schema.json, schemas/install-modules.schema.json)
4. Edit or add scripts/lib/install-manifests.js and scripts/lib/install-targets/*.js for logic
5. Add or update tests in tests/lib/install-targets.test.js
6. Update documentation (README.md, .gemini/GEMINI.md, etc.)
**Files typically involved**:
- `.gemini/*`
- `.codebuddy/*`
- `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`
- `README.md`
**Example commit sequence**:
```
Add new install scripts and docs under a dedicated directory (e.g., .gemini/, .codebuddy/)
Update manifests/install-modules.json to register the new target
Update or add schema files (schemas/ecc-install-config.schema.json, schemas/install-modules.schema.json)
Edit or add scripts/lib/install-manifests.js and scripts/lib/install-targets/*.js for logic
Add or update tests in tests/lib/install-targets.test.js
Update documentation (README.md, .gemini/GEMINI.md, etc.)
```
### Add Or Update Hook Or Session Management
Implements or refines hooks and session management logic, including accumulator patterns, session start/end, and related tests.
**Frequency**: ~2 times per month
**Steps**:
1. Edit or create scripts/hooks/*.js for hook logic (e.g., post-edit-accumulator.js, stop-format-typecheck.js, session-start.js)
2. Update hooks/hooks.json for hook configuration
3. Add or update tests in tests/hooks/*.test.js
4. Optionally update shell scripts (scripts/hooks/*.sh)
5. Optionally update adapters (.cursor/hooks/after-file-edit.js)
**Files typically involved**:
- `scripts/hooks/*.js`
- `hooks/hooks.json`
- `tests/hooks/*.test.js`
- `scripts/hooks/*.sh`
- `.cursor/hooks/after-file-edit.js`
**Example commit sequence**:
```
Edit or create scripts/hooks/*.js for hook logic (e.g., post-edit-accumulator.js, stop-format-typecheck.js, session-start.js)
Update hooks/hooks.json for hook configuration
Add or update tests in tests/hooks/*.test.js
Optionally update shell scripts (scripts/hooks/*.sh)
Optionally update adapters (.cursor/hooks/after-file-edit.js)
```
### Add Or Update Skill Or Agent
Adds or updates a skill or agent definition, often including a new SKILL.md and/or agent .md, sometimes with supporting config.
**Frequency**: ~2 times per month
**Steps**:
1. Create or edit skills/*/SKILL.md
2. Create or edit agents/*.md
3. Optionally update mcp-configs/mcp-servers.json or other config files
4. Optionally update AGENTS.md or related documentation
**Files typically involved**:
- `skills/*/SKILL.md`
- `agents/*.md`
- `mcp-configs/mcp-servers.json`
- `AGENTS.md`
**Example commit sequence**:
```
Create or edit skills/*/SKILL.md
Create or edit agents/*.md
Optionally update mcp-configs/mcp-servers.json or other config files
Optionally update AGENTS.md or related documentation
```
### Dependabot Or Automated Dependency Update
Automated workflow to update dependencies via Dependabot or similar, touching lockfiles and workflow YAMLs.
**Frequency**: ~4 times per month
**Steps**:
1. Update package.json and/or yarn.lock
2. Update .github/workflows/*.yml as needed for new dependency versions
3. Commit with a standardized message referencing the dependency and version
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**:
- `package.json`
- `yarn.lock`
- `schemas/*.json`
**Example commit sequence**:
```
Edit package.json, yarn.lock, or other lockfiles
Edit schema files under schemas/
Optionally update related scripts or manifests
```
### Ci Cd Workflow Update
Updates CI/CD workflow files, usually for dependency bumps or workflow improvements.
**Frequency**: ~2 times per month
**Steps**:
1. Edit workflow files under .github/workflows/
**Files typically involved**:
- `.github/workflows/*.yml`
**Example commit sequence**:
```
Update package.json and/or yarn.lock
Update .github/workflows/*.yml as needed for new dependency versions
Commit with a standardized message referencing the dependency and version
Edit workflow files under .github/workflows/
```

View File

@@ -8,8 +8,8 @@
],
"commandFiles": [
".claude/commands/feature-development.md",
".claude/commands/add-new-command-or-agentic-workflow.md",
".claude/commands/add-or-update-plugin-marketplace-system.md"
".claude/commands/refactoring.md",
".claude/commands/add-new-skill.md"
],
"updatedAt": "2026-04-01T22:56:13.232Z"
"updatedAt": "2026-04-01T22:44:14.561Z"
}