mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-04-02 15:13:28 +08:00
Compare commits
15 Commits
ecc-tools/
...
ecc-tools/
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
5145e24222 | ||
|
|
a16676fe9a | ||
|
|
36e47c6099 | ||
|
|
4203ed1baf | ||
|
|
0665df15db | ||
|
|
c700028be9 | ||
|
|
0bd78cf996 | ||
|
|
03c1a516b6 | ||
|
|
0eca0d1c46 | ||
|
|
19c0f59836 | ||
|
|
f5ab500e8f | ||
|
|
b32e022a24 | ||
|
|
b5d28c7354 | ||
|
|
62b838f230 | ||
|
|
0c65f4031d |
@@ -40,7 +40,7 @@ Follow these commit message conventions based on 500 analyzed commits.
|
||||
|
||||
### Message Guidelines
|
||||
|
||||
- Average message length: ~57 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: add everything-claude-code ECC bundle (.claude/commands/add-new-skill.md)
|
||||
refactor: simplify redundant checks; normalize getInstalledPlugin inputs
|
||||
```
|
||||
|
||||
*Commit message example*
|
||||
|
||||
```text
|
||||
refactor: collapse legacy command bodies into skills
|
||||
fix: preserve file permissions in writeJsonAtomic
|
||||
```
|
||||
|
||||
*Commit message example*
|
||||
|
||||
```text
|
||||
fix: dedupe managed hooks by semantic identity
|
||||
style: apply linter formatting to pluginRegistry.js
|
||||
```
|
||||
|
||||
*Commit message example*
|
||||
|
||||
```text
|
||||
docs: close bundle drift and sync plugin guidance
|
||||
chore: update yarn.lock
|
||||
```
|
||||
|
||||
*Commit message example*
|
||||
|
||||
```text
|
||||
chore: ignore local orchestration artifacts
|
||||
feat(plugin): add marketplace add/install system
|
||||
```
|
||||
|
||||
*Commit message example*
|
||||
|
||||
```text
|
||||
feat: add everything-claude-code ECC bundle (.claude/commands/refactoring.md)
|
||||
fix: ship marketplaces.json as empty stub to prevent duplicate-add error
|
||||
```
|
||||
|
||||
*Commit message example*
|
||||
|
||||
```text
|
||||
feat: add everything-claude-code ECC bundle (.claude/commands/feature-development.md)
|
||||
fix: normalize lookups, atomic writes, reject empty marketplace specifier
|
||||
```
|
||||
|
||||
*Commit message example*
|
||||
|
||||
```text
|
||||
feat: add everything-claude-code ECC bundle (.claude/enterprise/controls.md)
|
||||
refactor: extract shared readJsonFile helper; fix single-dash flag parsing
|
||||
```
|
||||
|
||||
## Architecture
|
||||
@@ -188,7 +188,7 @@ These workflows were detected from analyzing commit patterns.
|
||||
|
||||
Standard feature implementation workflow
|
||||
|
||||
**Frequency**: ~19 times per month
|
||||
**Frequency**: ~14 times per month
|
||||
|
||||
**Steps**:
|
||||
1. Add feature implementation
|
||||
@@ -203,181 +203,187 @@ Standard feature implementation workflow
|
||||
|
||||
**Example commit sequence**:
|
||||
```
|
||||
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)
|
||||
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)
|
||||
```
|
||||
|
||||
### Refactoring
|
||||
### Add New Command Or Agentic Workflow
|
||||
|
||||
Code refactoring and cleanup workflow
|
||||
Adds a new command or agentic workflow to the system, often including new .md command files, agent definitions, and skill orchestrators.
|
||||
|
||||
**Frequency**: ~2 times per month
|
||||
**Frequency**: ~3 times per month
|
||||
|
||||
**Steps**:
|
||||
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
|
||||
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
|
||||
|
||||
**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**:
|
||||
```
|
||||
Add multiple agent and/or skill files
|
||||
Add supporting commands and scripts
|
||||
Add or update documentation and examples
|
||||
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
|
||||
```
|
||||
|
||||
### Documentation Update
|
||||
### Add Or Update Plugin Marketplace System
|
||||
|
||||
Updates documentation to reflect new features, workflows, or guidance.
|
||||
|
||||
**Frequency**: ~3 times per month
|
||||
|
||||
**Steps**:
|
||||
1. Edit documentation files (README.md, AGENTS.md, WORKING-CONTEXT.md, docs/...)
|
||||
2. Optionally update or add new guidance files
|
||||
|
||||
**Files typically involved**:
|
||||
- `README.md`
|
||||
- `AGENTS.md`
|
||||
- `WORKING-CONTEXT.md`
|
||||
- `docs/**/*.md`
|
||||
|
||||
**Example commit sequence**:
|
||||
```
|
||||
Edit documentation files (README.md, AGENTS.md, WORKING-CONTEXT.md, docs/...)
|
||||
Optionally update or add new guidance files
|
||||
```
|
||||
|
||||
### Dependency Or Schema Update
|
||||
|
||||
Updates dependencies or schema files, often in response to new features or external updates.
|
||||
Implements or refines the plugin marketplace system, including registry helpers, CLI scripts, JSON stubs, and documentation.
|
||||
|
||||
**Frequency**: ~2 times per month
|
||||
|
||||
**Steps**:
|
||||
1. Edit package.json, yarn.lock, or other lockfiles
|
||||
2. Edit schema files under schemas/
|
||||
3. Optionally update related scripts or manifests
|
||||
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.)
|
||||
|
||||
**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`
|
||||
|
||||
**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.)
|
||||
```
|
||||
|
||||
### Add New Install Target Or Adaptation
|
||||
|
||||
Adds a new install target (e.g., Gemini, CodeBuddy) to the system, including scripts, schemas, and tests.
|
||||
|
||||
**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
|
||||
|
||||
**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**:
|
||||
```
|
||||
Edit workflow files under .github/workflows/
|
||||
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
|
||||
```
|
||||
|
||||
|
||||
|
||||
41
.claude/commands/add-new-command-or-agentic-workflow.md
Normal file
41
.claude/commands/add-new-command-or-agentic-workflow.md
Normal file
@@ -0,0 +1,41 @@
|
||||
---
|
||||
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.
|
||||
@@ -1,37 +0,0 @@
|
||||
---
|
||||
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.
|
||||
42
.claude/commands/add-or-update-plugin-marketplace-system.md
Normal file
42
.claude/commands/add-or-update-plugin-marketplace-system.md
Normal file
@@ -0,0 +1,42 @@
|
||||
---
|
||||
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.
|
||||
@@ -1,35 +0,0 @@
|
||||
---
|
||||
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.
|
||||
@@ -2,7 +2,7 @@
|
||||
"version": "1.3",
|
||||
"schemaVersion": "1.0",
|
||||
"generatedBy": "ecc-tools",
|
||||
"generatedAt": "2026-04-01T22:44:14.561Z",
|
||||
"generatedAt": "2026-04-01T22:56:13.232Z",
|
||||
"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/refactoring.md",
|
||||
".claude/commands/add-new-skill.md"
|
||||
".claude/commands/add-new-command-or-agentic-workflow.md",
|
||||
".claude/commands/add-or-update-plugin-marketplace-system.md"
|
||||
],
|
||||
"packageFiles": {
|
||||
"runtime-core": [
|
||||
@@ -179,8 +179,8 @@
|
||||
],
|
||||
"workflow-pack": [
|
||||
".claude/commands/feature-development.md",
|
||||
".claude/commands/refactoring.md",
|
||||
".claude/commands/add-new-skill.md"
|
||||
".claude/commands/add-new-command-or-agentic-workflow.md",
|
||||
".claude/commands/add-or-update-plugin-marketplace-system.md"
|
||||
]
|
||||
},
|
||||
"moduleFiles": {
|
||||
@@ -210,8 +210,8 @@
|
||||
],
|
||||
"workflow-pack": [
|
||||
".claude/commands/feature-development.md",
|
||||
".claude/commands/refactoring.md",
|
||||
".claude/commands/add-new-skill.md"
|
||||
".claude/commands/add-new-command-or-agentic-workflow.md",
|
||||
".claude/commands/add-or-update-plugin-marketplace-system.md"
|
||||
]
|
||||
},
|
||||
"files": [
|
||||
@@ -292,13 +292,13 @@
|
||||
},
|
||||
{
|
||||
"moduleId": "workflow-pack",
|
||||
"path": ".claude/commands/refactoring.md",
|
||||
"description": "Workflow command scaffold for refactoring."
|
||||
"path": ".claude/commands/add-new-command-or-agentic-workflow.md",
|
||||
"description": "Workflow command scaffold for add-new-command-or-agentic-workflow."
|
||||
},
|
||||
{
|
||||
"moduleId": "workflow-pack",
|
||||
"path": ".claude/commands/add-new-skill.md",
|
||||
"description": "Workflow command scaffold for add-new-skill."
|
||||
"path": ".claude/commands/add-or-update-plugin-marketplace-system.md",
|
||||
"description": "Workflow command scaffold for add-or-update-plugin-marketplace-system."
|
||||
}
|
||||
],
|
||||
"workflows": [
|
||||
@@ -307,12 +307,12 @@
|
||||
"path": ".claude/commands/feature-development.md"
|
||||
},
|
||||
{
|
||||
"command": "refactoring",
|
||||
"path": ".claude/commands/refactoring.md"
|
||||
"command": "add-new-command-or-agentic-workflow",
|
||||
"path": ".claude/commands/add-new-command-or-agentic-workflow.md"
|
||||
},
|
||||
{
|
||||
"command": "add-new-skill",
|
||||
"path": ".claude/commands/add-new-skill.md"
|
||||
"command": "add-or-update-plugin-marketplace-system",
|
||||
"path": ".claude/commands/add-or-update-plugin-marketplace-system.md"
|
||||
}
|
||||
],
|
||||
"adapters": {
|
||||
@@ -321,8 +321,8 @@
|
||||
"identityPath": ".claude/identity.json",
|
||||
"commandPaths": [
|
||||
".claude/commands/feature-development.md",
|
||||
".claude/commands/refactoring.md",
|
||||
".claude/commands/add-new-skill.md"
|
||||
".claude/commands/add-new-command-or-agentic-workflow.md",
|
||||
".claude/commands/add-or-update-plugin-marketplace-system.md"
|
||||
]
|
||||
},
|
||||
"codex": {
|
||||
|
||||
@@ -10,5 +10,5 @@
|
||||
"javascript"
|
||||
],
|
||||
"suggestedBy": "ecc-tools-repo-analysis",
|
||||
"createdAt": "2026-04-01T22:51:05.478Z"
|
||||
"createdAt": "2026-04-01T22:56:57.484Z"
|
||||
}
|
||||
@@ -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: 9
|
||||
- Workflows detected: 7
|
||||
@@ -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
|
||||
- refactoring: Code refactoring and cleanup workflow
|
||||
- add-new-skill: Adds a new skill to the repository, enabling new agent capabilities or workflows.
|
||||
- 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.
|
||||
|
||||
## Review Reminder
|
||||
|
||||
|
||||
@@ -40,7 +40,7 @@ Follow these commit message conventions based on 500 analyzed commits.
|
||||
|
||||
### Message Guidelines
|
||||
|
||||
- Average message length: ~57 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: add everything-claude-code ECC bundle (.claude/commands/add-new-skill.md)
|
||||
refactor: simplify redundant checks; normalize getInstalledPlugin inputs
|
||||
```
|
||||
|
||||
*Commit message example*
|
||||
|
||||
```text
|
||||
refactor: collapse legacy command bodies into skills
|
||||
fix: preserve file permissions in writeJsonAtomic
|
||||
```
|
||||
|
||||
*Commit message example*
|
||||
|
||||
```text
|
||||
fix: dedupe managed hooks by semantic identity
|
||||
style: apply linter formatting to pluginRegistry.js
|
||||
```
|
||||
|
||||
*Commit message example*
|
||||
|
||||
```text
|
||||
docs: close bundle drift and sync plugin guidance
|
||||
chore: update yarn.lock
|
||||
```
|
||||
|
||||
*Commit message example*
|
||||
|
||||
```text
|
||||
chore: ignore local orchestration artifacts
|
||||
feat(plugin): add marketplace add/install system
|
||||
```
|
||||
|
||||
*Commit message example*
|
||||
|
||||
```text
|
||||
feat: add everything-claude-code ECC bundle (.claude/commands/refactoring.md)
|
||||
fix: ship marketplaces.json as empty stub to prevent duplicate-add error
|
||||
```
|
||||
|
||||
*Commit message example*
|
||||
|
||||
```text
|
||||
feat: add everything-claude-code ECC bundle (.claude/commands/feature-development.md)
|
||||
fix: normalize lookups, atomic writes, reject empty marketplace specifier
|
||||
```
|
||||
|
||||
*Commit message example*
|
||||
|
||||
```text
|
||||
feat: add everything-claude-code ECC bundle (.claude/enterprise/controls.md)
|
||||
refactor: extract shared readJsonFile helper; fix single-dash flag parsing
|
||||
```
|
||||
|
||||
## Architecture
|
||||
@@ -188,7 +188,7 @@ These workflows were detected from analyzing commit patterns.
|
||||
|
||||
Standard feature implementation workflow
|
||||
|
||||
**Frequency**: ~19 times per month
|
||||
**Frequency**: ~14 times per month
|
||||
|
||||
**Steps**:
|
||||
1. Add feature implementation
|
||||
@@ -203,181 +203,187 @@ Standard feature implementation workflow
|
||||
|
||||
**Example commit sequence**:
|
||||
```
|
||||
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)
|
||||
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)
|
||||
```
|
||||
|
||||
### Refactoring
|
||||
### Add New Command Or Agentic Workflow
|
||||
|
||||
Code refactoring and cleanup workflow
|
||||
Adds a new command or agentic workflow to the system, often including new .md command files, agent definitions, and skill orchestrators.
|
||||
|
||||
**Frequency**: ~2 times per month
|
||||
**Frequency**: ~3 times per month
|
||||
|
||||
**Steps**:
|
||||
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
|
||||
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
|
||||
|
||||
**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**:
|
||||
```
|
||||
Add multiple agent and/or skill files
|
||||
Add supporting commands and scripts
|
||||
Add or update documentation and examples
|
||||
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
|
||||
```
|
||||
|
||||
### Documentation Update
|
||||
### Add Or Update Plugin Marketplace System
|
||||
|
||||
Updates documentation to reflect new features, workflows, or guidance.
|
||||
|
||||
**Frequency**: ~3 times per month
|
||||
|
||||
**Steps**:
|
||||
1. Edit documentation files (README.md, AGENTS.md, WORKING-CONTEXT.md, docs/...)
|
||||
2. Optionally update or add new guidance files
|
||||
|
||||
**Files typically involved**:
|
||||
- `README.md`
|
||||
- `AGENTS.md`
|
||||
- `WORKING-CONTEXT.md`
|
||||
- `docs/**/*.md`
|
||||
|
||||
**Example commit sequence**:
|
||||
```
|
||||
Edit documentation files (README.md, AGENTS.md, WORKING-CONTEXT.md, docs/...)
|
||||
Optionally update or add new guidance files
|
||||
```
|
||||
|
||||
### Dependency Or Schema Update
|
||||
|
||||
Updates dependencies or schema files, often in response to new features or external updates.
|
||||
Implements or refines the plugin marketplace system, including registry helpers, CLI scripts, JSON stubs, and documentation.
|
||||
|
||||
**Frequency**: ~2 times per month
|
||||
|
||||
**Steps**:
|
||||
1. Edit package.json, yarn.lock, or other lockfiles
|
||||
2. Edit schema files under schemas/
|
||||
3. Optionally update related scripts or manifests
|
||||
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.)
|
||||
|
||||
**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`
|
||||
|
||||
**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.)
|
||||
```
|
||||
|
||||
### Add New Install Target Or Adaptation
|
||||
|
||||
Adds a new install target (e.g., Gemini, CodeBuddy) to the system, including scripts, schemas, and tests.
|
||||
|
||||
**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
|
||||
|
||||
**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**:
|
||||
```
|
||||
Edit workflow files under .github/workflows/
|
||||
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
|
||||
```
|
||||
|
||||
|
||||
|
||||
@@ -8,8 +8,8 @@
|
||||
],
|
||||
"commandFiles": [
|
||||
".claude/commands/feature-development.md",
|
||||
".claude/commands/refactoring.md",
|
||||
".claude/commands/add-new-skill.md"
|
||||
".claude/commands/add-new-command-or-agentic-workflow.md",
|
||||
".claude/commands/add-or-update-plugin-marketplace-system.md"
|
||||
],
|
||||
"updatedAt": "2026-04-01T22:44:14.561Z"
|
||||
"updatedAt": "2026-04-01T22:56:13.232Z"
|
||||
}
|
||||
Reference in New Issue
Block a user