[2.9.0] Rename plugin to compound-engineering

BREAKING: Plugin renamed from compounding-engineering to compound-engineering.
Users will need to reinstall with the new name:

  claude /plugin install compound-engineering

Changes:
- Renamed plugin directory and all references
- Updated documentation counts (24 agents, 19 commands)
- Added julik-frontend-races-reviewer to docs

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Kieran Klaassen
2025-12-02 17:32:04 -08:00
parent 4b49e5344d
commit 6c5b3e40db
121 changed files with 136 additions and 117 deletions

View File

@@ -1,7 +1,7 @@
{
"name": "compounding-engineering",
"version": "2.8.3",
"description": "AI-powered development tools. 24 agents, 16 commands, 11 skills, 2 MCP servers for code review, research, design, and workflow automation.",
"name": "compound-engineering",
"version": "2.9.0",
"description": "AI-powered development tools. 24 agents, 19 commands, 11 skills, 2 MCP servers for code review, research, design, and workflow automation.",
"author": {
"name": "Kieran Klaassen",
"email": "kieran@every.to",
@@ -12,7 +12,7 @@
"license": "MIT",
"keywords": [
"ai-powered",
"compounding-engineering",
"compound-engineering",
"workflow-automation",
"code-review",
"rails",

View File

@@ -1,10 +1,20 @@
# Changelog
All notable changes to the compounding-engineering plugin will be documented in this file.
All notable changes to the compound-engineering plugin will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [2.9.0] - 2025-12-02
### Changed
- **Plugin renamed** from `compounding-engineering` to `compound-engineering`. Shorter name, same philosophy. Users will need to reinstall with the new name.
### Fixed
- **Documentation counts** - Updated all documentation to reflect actual component counts (24 agents, 19 commands).
## [2.8.3] - 2025-11-29
### Fixed
@@ -63,7 +73,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
### Added
- **`/report-bug` command** - New slash command for reporting bugs in the compounding-engineering plugin. Provides a structured workflow that gathers bug information through guided questions, collects environment details automatically, and creates a GitHub issue in the EveryInc/every-marketplace repository. Designed to be user-friendly for anyone using the plugin.
- **`/report-bug` command** - New slash command for reporting bugs in the compound-engineering plugin. Provides a structured workflow that gathers bug information through guided questions, collects environment details automatically, and creates a GitHub issue in the EveryInc/every-marketplace repository. Designed to be user-friendly for anyone using the plugin.
## [2.4.1] - 2024-11-24
@@ -209,7 +219,7 @@ Major reorganization consolidating agents, commands, and skills from multiple so
## [1.0.0] - 2024-10-09
Initial release of the compounding-engineering plugin.
Initial release of the compound-engineering plugin.
### Added

View File

@@ -6,8 +6,8 @@ AI-powered development tools that get smarter with every use. Make each unit of
| Component | Count |
|-----------|-------|
| Agents | 23 |
| Commands | 16 |
| Agents | 24 |
| Commands | 19 |
| Skills | 11 |
| MCP Servers | 2 |
@@ -15,7 +15,7 @@ AI-powered development tools that get smarter with every use. Make each unit of
Agents are organized into categories for easier discovery.
### Review (10)
### Review (11)
| Agent | Description |
|-------|-------------|
@@ -29,6 +29,7 @@ Agents are organized into categories for easier discovery.
| `pattern-recognition-specialist` | Analyze code for patterns and anti-patterns |
| `performance-oracle` | Performance analysis and optimization |
| `security-sentinel` | Security audits and vulnerability assessments |
| `julik-frontend-races-reviewer` | Review JavaScript/Stimulus code for race conditions |
### Research (4)
@@ -86,7 +87,7 @@ Core workflow commands (use the short form for autocomplete):
| `/heal-skill` | Fix skill documentation issues |
| `/plan_review` | Multi-agent plan review in parallel |
| `/prime` | Prime/setup command |
| `/report-bug` | Report a bug in the compounding-engineering plugin |
| `/report-bug` | Report a bug in the compound-engineering plugin |
| `/reproduce-bug` | Reproduce bugs using logs and console |
| `/resolve_parallel` | Resolve TODO comments in parallel |
| `/resolve_pr_parallel` | Resolve PR comments in parallel |
@@ -161,7 +162,7 @@ MCP servers start automatically when the plugin is enabled.
## Installation
```bash
claude /plugin install compounding-engineering
claude /plugin install compound-engineering
```
## Known Issues

View File

@@ -13,17 +13,17 @@ Run these checks:
```bash
# Count components
echo "Agents: $(ls plugins/compounding-engineering/agents/*.md | wc -l)"
echo "Commands: $(ls plugins/compounding-engineering/commands/*.md | wc -l)"
echo "Skills: $(ls -d plugins/compounding-engineering/skills/*/ 2>/dev/null | wc -l)"
echo "Agents: $(ls plugins/compound-engineering/agents/*.md | wc -l)"
echo "Commands: $(ls plugins/compound-engineering/commands/*.md | wc -l)"
echo "Skills: $(ls -d plugins/compound-engineering/skills/*/ 2>/dev/null | wc -l)"
# Validate JSON
cat .claude-plugin/marketplace.json | jq . > /dev/null && echo "✓ marketplace.json valid"
cat plugins/compounding-engineering/.claude-plugin/plugin.json | jq . > /dev/null && echo "✓ plugin.json valid"
cat plugins/compound-engineering/.claude-plugin/plugin.json | jq . > /dev/null && echo "✓ plugin.json valid"
# Check all HTML files exist
for page in index agents commands skills mcp-servers changelog getting-started; do
if [ -f "plugins/compounding-engineering/docs/pages/${page}.html" ] || [ -f "plugins/compounding-engineering/docs/${page}.html" ]; then
if [ -f "plugins/compound-engineering/docs/pages/${page}.html" ] || [ -f "plugins/compound-engineering/docs/${page}.html" ]; then
echo "✓ ${page}.html exists"
else
echo "✗ ${page}.html MISSING"
@@ -34,7 +34,7 @@ done
## Step 2: Check for Uncommitted Changes
```bash
git status --porcelain plugins/compounding-engineering/docs/
git status --porcelain plugins/compound-engineering/docs/
```
If there are uncommitted changes, warn the user to commit first.
@@ -66,7 +66,7 @@ on:
push:
branches: [main]
paths:
- 'plugins/compounding-engineering/docs/**'
- 'plugins/compound-engineering/docs/**'
workflow_dispatch:
permissions:
@@ -89,7 +89,7 @@ jobs:
- uses: actions/configure-pages@v4
- uses: actions/upload-pages-artifact@v3
with:
path: 'plugins/compounding-engineering/docs'
path: 'plugins/compound-engineering/docs'
- uses: actions/deploy-pages@v4
```

View File

@@ -6,7 +6,7 @@ argument-hint: "[optional: --dry-run to preview changes without writing]"
# Release Documentation Command
You are a documentation generator for the compounding-engineering plugin. Your job is to ensure the documentation site at `plugins/compounding-engineering/docs/` is always up-to-date with the actual plugin components.
You are a documentation generator for the compound-engineering plugin. Your job is to ensure the documentation site at `plugins/compound-engineering/docs/` is always up-to-date with the actual plugin components.
## Overview
@@ -23,38 +23,38 @@ First, count and list all current components:
```bash
# Count agents
ls plugins/compounding-engineering/agents/*.md | wc -l
ls plugins/compound-engineering/agents/*.md | wc -l
# Count commands
ls plugins/compounding-engineering/commands/*.md | wc -l
ls plugins/compound-engineering/commands/*.md | wc -l
# Count skills
ls -d plugins/compounding-engineering/skills/*/ 2>/dev/null | wc -l
ls -d plugins/compound-engineering/skills/*/ 2>/dev/null | wc -l
# Count MCP servers
ls -d plugins/compounding-engineering/mcp-servers/*/ 2>/dev/null | wc -l
ls -d plugins/compound-engineering/mcp-servers/*/ 2>/dev/null | wc -l
```
Read all component files to get their metadata:
### Agents
For each agent file in `plugins/compounding-engineering/agents/*.md`:
For each agent file in `plugins/compound-engineering/agents/*.md`:
- Extract the frontmatter (name, description)
- Note the category (Review, Research, Workflow, Design, Docs)
- Get key responsibilities from the content
### Commands
For each command file in `plugins/compounding-engineering/commands/*.md`:
For each command file in `plugins/compound-engineering/commands/*.md`:
- Extract the frontmatter (name, description, argument-hint)
- Categorize as Workflow or Utility command
### Skills
For each skill directory in `plugins/compounding-engineering/skills/*/`:
For each skill directory in `plugins/compound-engineering/skills/*/`:
- Read the SKILL.md file for frontmatter (name, description)
- Note any scripts or supporting files
### MCP Servers
For each MCP server in `plugins/compounding-engineering/mcp-servers/*/`:
For each MCP server in `plugins/compound-engineering/mcp-servers/*/`:
- Read the configuration and README
- List the tools provided
@@ -117,7 +117,7 @@ Regenerate the MCP servers reference page:
Ensure counts are consistent across:
1. **`plugins/compounding-engineering/.claude-plugin/plugin.json`**
1. **`plugins/compound-engineering/.claude-plugin/plugin.json`**
- Update `description` with correct counts
- Update `components` object with counts
- Update `agents`, `commands` arrays with current items
@@ -125,7 +125,7 @@ Ensure counts are consistent across:
2. **`.claude-plugin/marketplace.json`**
- Update plugin `description` with correct counts
3. **`plugins/compounding-engineering/README.md`**
3. **`plugins/compound-engineering/README.md`**
- Update intro paragraph with counts
- Update component lists
@@ -136,14 +136,14 @@ Run validation checks:
```bash
# Validate JSON files
cat .claude-plugin/marketplace.json | jq .
cat plugins/compounding-engineering/.claude-plugin/plugin.json | jq .
cat plugins/compound-engineering/.claude-plugin/plugin.json | jq .
# Verify counts match
echo "Agents in files: $(ls plugins/compounding-engineering/agents/*.md | wc -l)"
grep -o "[0-9]* specialized agents" plugins/compounding-engineering/docs/index.html
echo "Agents in files: $(ls plugins/compound-engineering/agents/*.md | wc -l)"
grep -o "[0-9]* specialized agents" plugins/compound-engineering/docs/index.html
echo "Commands in files: $(ls plugins/compounding-engineering/commands/*.md | wc -l)"
grep -o "[0-9]* slash commands" plugins/compounding-engineering/docs/index.html
echo "Commands in files: $(ls plugins/compound-engineering/commands/*.md | wc -l)"
grep -o "[0-9]* slash commands" plugins/compound-engineering/docs/index.html
```
## Step 5: Report Changes

View File

@@ -1,12 +1,12 @@
---
name: report-bug
description: Report a bug in the compounding-engineering plugin
description: Report a bug in the compound-engineering plugin
argument-hint: "[optional: brief description of the bug]"
---
# Report a Compounding Engineering Plugin Bug
Report bugs encountered while using the compounding-engineering plugin. This command gathers structured information and creates a GitHub issue for the maintainer.
Report bugs encountered while using the compound-engineering plugin. This command gathers structured information and creates a GitHub issue for the maintainer.
## Step 1: Gather Bug Information
@@ -41,7 +41,7 @@ Use the AskUserQuestion tool to collect the following information:
Automatically gather:
```bash
# Get plugin version
cat ~/.claude/plugins/installed_plugins.json 2>/dev/null | grep -A5 "compounding-engineering" | head -10 || echo "Plugin info not found"
cat ~/.claude/plugins/installed_plugins.json 2>/dev/null | grep -A5 "compound-engineering" | head -10 || echo "Plugin info not found"
# Get Claude Code version
claude --version 2>/dev/null || echo "Claude CLI version unknown"
@@ -101,16 +101,16 @@ Use the GitHub CLI to create the issue:
```bash
gh issue create \
--repo EveryInc/every-marketplace \
--title "[compounding-engineering] Bug: [Brief description]" \
--title "[compound-engineering] Bug: [Brief description]" \
--body "[Formatted bug report from Step 3]" \
--label "bug,compounding-engineering"
--label "bug,compound-engineering"
```
**Note:** If labels don't exist, create without labels:
```bash
gh issue create \
--repo EveryInc/every-marketplace \
--title "[compounding-engineering] Bug: [Brief description]" \
--title "[compound-engineering] Bug: [Brief description]" \
--body "[Formatted bug report]"
```
@@ -127,9 +127,9 @@ After the issue is created:
✅ Bug report submitted successfully!
Issue: https://github.com/EveryInc/every-marketplace/issues/[NUMBER]
Title: [compounding-engineering] Bug: [description]
Title: [compound-engineering] Bug: [description]
Thank you for helping improve the compounding-engineering plugin!
Thank you for helping improve the compound-engineering plugin!
The maintainer will review your report and respond as soon as possible.
```

Some files were not shown because too many files have changed in this diff Show More