docs: Add /release-docs command, changelog page, and build instructions
- Add /release-docs command for regenerating documentation site - Add commands/README.md with usage instructions for all commands - Add changelog.html page rendering CHANGELOG.md in HTML format - Add changelog CSS styles to docs.css - Update navigation in all docs pages to include changelog link - Fix command count from 16 to 13 in navigation - Update CLAUDE.md with: - Documentation Site section explaining structure - /release-docs command in update checklist - Instructions for keeping docs up-to-date 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Claude
105
plugins/compounding-engineering/commands/README.md
Normal file
105
plugins/compounding-engineering/commands/README.md
Normal file
@@ -0,0 +1,105 @@
|
||||
# Commands
|
||||
|
||||
This directory contains all slash commands for the compounding-engineering plugin. Each `.md` file defines a command that can be invoked via `claude /command-name`.
|
||||
|
||||
## Documentation Management
|
||||
|
||||
### `/release-docs`
|
||||
|
||||
**Purpose:** Build and update the documentation site with current plugin components.
|
||||
|
||||
**Usage:**
|
||||
```bash
|
||||
# Full documentation release
|
||||
claude /release-docs
|
||||
|
||||
# Preview changes without writing files
|
||||
claude /release-docs --dry-run
|
||||
```
|
||||
|
||||
**What it does:**
|
||||
1. Inventories all current components (agents, commands, skills, MCP servers)
|
||||
2. Updates `docs/index.html` with accurate stats
|
||||
3. Regenerates reference pages (`agents.html`, `commands.html`, `skills.html`, `mcp-servers.html`)
|
||||
4. Updates `changelog.html` with latest version history
|
||||
5. Ensures counts in `plugin.json` and `marketplace.json` match actual files
|
||||
6. Validates all JSON files
|
||||
|
||||
**When to run:**
|
||||
- After adding, removing, or modifying any agent
|
||||
- After adding, removing, or modifying any command
|
||||
- After adding, removing, or modifying any skill
|
||||
- After adding, removing, or modifying any MCP server
|
||||
- Before releasing a new version
|
||||
|
||||
## Workflow Commands
|
||||
|
||||
### `/plan_review`
|
||||
Multi-agent plan review running in parallel for thorough analysis.
|
||||
|
||||
### `/resolve_parallel`
|
||||
Resolve TODO comments in the codebase in parallel.
|
||||
|
||||
### `/resolve_pr_parallel`
|
||||
Resolve PR comments in parallel.
|
||||
|
||||
### `/resolve_todo_parallel`
|
||||
Resolve TODO items from a list in parallel.
|
||||
|
||||
## Development Commands
|
||||
|
||||
### `/changelog`
|
||||
Create engaging changelogs for recent merges to main branch.
|
||||
|
||||
### `/generate_command`
|
||||
Generate new slash command files from a description.
|
||||
|
||||
### `/create-agent-skill`
|
||||
Create or edit Claude Code skills with best practices.
|
||||
|
||||
### `/heal-skill`
|
||||
Fix skill documentation issues and formatting.
|
||||
|
||||
### `/prime`
|
||||
Prime/setup command for initializing projects.
|
||||
|
||||
### `/reproduce-bug`
|
||||
Reproduce bugs using logs and console output.
|
||||
|
||||
### `/report-bug`
|
||||
Report bugs in the compounding-engineering plugin with structured workflow.
|
||||
|
||||
### `/triage`
|
||||
Triage and prioritize issues.
|
||||
|
||||
## Command File Structure
|
||||
|
||||
Each command file follows this structure:
|
||||
|
||||
```markdown
|
||||
---
|
||||
name: command-name
|
||||
description: Brief description of what the command does
|
||||
argument-hint: "[optional arguments description]"
|
||||
---
|
||||
|
||||
# Command Title
|
||||
|
||||
Instructions for Claude on how to execute this command...
|
||||
```
|
||||
|
||||
## Adding a New Command
|
||||
|
||||
1. Create a new `.md` file in this directory
|
||||
2. Add the frontmatter with `name`, `description`, and optional `argument-hint`
|
||||
3. Write detailed instructions for Claude
|
||||
4. Run `/release-docs` to update documentation
|
||||
5. Test with `claude /your-command-name`
|
||||
|
||||
## Best Practices
|
||||
|
||||
- Keep command names short and descriptive (use hyphens, not underscores)
|
||||
- Provide clear step-by-step instructions
|
||||
- Include examples of expected output
|
||||
- Document any prerequisites or dependencies
|
||||
- Use parallel agent invocation when tasks are independent
|
||||
211
plugins/compounding-engineering/commands/release-docs.md
Normal file
211
plugins/compounding-engineering/commands/release-docs.md
Normal file
@@ -0,0 +1,211 @@
|
||||
---
|
||||
name: release-docs
|
||||
description: Build and update the documentation site with current plugin components
|
||||
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.
|
||||
|
||||
## Overview
|
||||
|
||||
The documentation site is a static HTML/CSS/JS site based on the Evil Martians LaunchKit template. It needs to be regenerated whenever:
|
||||
|
||||
- Agents are added, removed, or modified
|
||||
- Commands are added, removed, or modified
|
||||
- Skills are added, removed, or modified
|
||||
- MCP servers are added, removed, or modified
|
||||
|
||||
## Step 1: Inventory Current Components
|
||||
|
||||
First, count and list all current components:
|
||||
|
||||
```bash
|
||||
# Count agents
|
||||
ls plugins/compounding-engineering/agents/*.md | wc -l
|
||||
|
||||
# Count commands
|
||||
ls plugins/compounding-engineering/commands/*.md | wc -l
|
||||
|
||||
# Count skills
|
||||
ls -d plugins/compounding-engineering/skills/*/ 2>/dev/null | wc -l
|
||||
|
||||
# Count MCP servers
|
||||
ls -d plugins/compounding-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`:
|
||||
- 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`:
|
||||
- Extract the frontmatter (name, description, argument-hint)
|
||||
- Categorize as Workflow or Utility command
|
||||
|
||||
### Skills
|
||||
For each skill directory in `plugins/compounding-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/*/`:
|
||||
- Read the configuration and README
|
||||
- List the tools provided
|
||||
|
||||
## Step 2: Update Documentation Pages
|
||||
|
||||
### 2a. Update `docs/index.html`
|
||||
|
||||
Update the stats section with accurate counts:
|
||||
```html
|
||||
<div class="stats-grid">
|
||||
<div class="stat-card">
|
||||
<span class="stat-number">[AGENT_COUNT]</span>
|
||||
<span class="stat-label">Specialized Agents</span>
|
||||
</div>
|
||||
<!-- Update all stat cards -->
|
||||
</div>
|
||||
```
|
||||
|
||||
Ensure the component summary sections list key components accurately.
|
||||
|
||||
### 2b. Update `docs/pages/agents.html`
|
||||
|
||||
Regenerate the complete agents reference page:
|
||||
- Group agents by category (Review, Research, Workflow, Design, Docs)
|
||||
- Include for each agent:
|
||||
- Name and description
|
||||
- Key responsibilities (bullet list)
|
||||
- Usage example: `claude agent [agent-name] "your message"`
|
||||
- Use cases
|
||||
|
||||
### 2c. Update `docs/pages/commands.html`
|
||||
|
||||
Regenerate the complete commands reference page:
|
||||
- Group commands by type (Workflow, Utility)
|
||||
- Include for each command:
|
||||
- Name and description
|
||||
- Arguments (if any)
|
||||
- Process/workflow steps
|
||||
- Example usage
|
||||
|
||||
### 2d. Update `docs/pages/skills.html`
|
||||
|
||||
Regenerate the complete skills reference page:
|
||||
- Group skills by category (Development Tools, Content & Workflow, Image Generation)
|
||||
- Include for each skill:
|
||||
- Name and description
|
||||
- Usage: `claude skill [skill-name]`
|
||||
- Features and capabilities
|
||||
|
||||
### 2e. Update `docs/pages/mcp-servers.html`
|
||||
|
||||
Regenerate the MCP servers reference page:
|
||||
- For each server:
|
||||
- Name and purpose
|
||||
- Tools provided
|
||||
- Configuration details
|
||||
- Supported frameworks/services
|
||||
|
||||
## Step 3: Update Metadata Files
|
||||
|
||||
Ensure counts are consistent across:
|
||||
|
||||
1. **`plugins/compounding-engineering/.claude-plugin/plugin.json`**
|
||||
- Update `description` with correct counts
|
||||
- Update `components` object with counts
|
||||
- Update `agents`, `commands` arrays with current items
|
||||
|
||||
2. **`.claude-plugin/marketplace.json`**
|
||||
- Update plugin `description` with correct counts
|
||||
|
||||
3. **`plugins/compounding-engineering/README.md`**
|
||||
- Update intro paragraph with counts
|
||||
- Update component lists
|
||||
|
||||
## Step 4: Validate
|
||||
|
||||
Run validation checks:
|
||||
|
||||
```bash
|
||||
# Validate JSON files
|
||||
cat .claude-plugin/marketplace.json | jq .
|
||||
cat plugins/compounding-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 "Commands in files: $(ls plugins/compounding-engineering/commands/*.md | wc -l)"
|
||||
grep -o "[0-9]* slash commands" plugins/compounding-engineering/docs/index.html
|
||||
```
|
||||
|
||||
## Step 5: Report Changes
|
||||
|
||||
Provide a summary of what was updated:
|
||||
|
||||
```
|
||||
## Documentation Release Summary
|
||||
|
||||
### Component Counts
|
||||
- Agents: X (previously Y)
|
||||
- Commands: X (previously Y)
|
||||
- Skills: X (previously Y)
|
||||
- MCP Servers: X (previously Y)
|
||||
|
||||
### Files Updated
|
||||
- docs/index.html - Updated stats and component summaries
|
||||
- docs/pages/agents.html - Regenerated with X agents
|
||||
- docs/pages/commands.html - Regenerated with X commands
|
||||
- docs/pages/skills.html - Regenerated with X skills
|
||||
- docs/pages/mcp-servers.html - Regenerated with X servers
|
||||
- plugin.json - Updated counts and component lists
|
||||
- marketplace.json - Updated description
|
||||
- README.md - Updated component lists
|
||||
|
||||
### New Components Added
|
||||
- [List any new agents/commands/skills]
|
||||
|
||||
### Components Removed
|
||||
- [List any removed agents/commands/skills]
|
||||
```
|
||||
|
||||
## Dry Run Mode
|
||||
|
||||
If `--dry-run` is specified:
|
||||
- Perform all inventory and validation steps
|
||||
- Report what WOULD be updated
|
||||
- Do NOT write any files
|
||||
- Show diff previews of proposed changes
|
||||
|
||||
## Error Handling
|
||||
|
||||
- If component files have invalid frontmatter, report the error and skip
|
||||
- If JSON validation fails, report and abort
|
||||
- Always maintain a valid state - don't partially update
|
||||
|
||||
## Post-Release
|
||||
|
||||
After successful release:
|
||||
1. Suggest updating CHANGELOG.md with documentation changes
|
||||
2. Remind to commit with message: `docs: Update documentation site to match plugin components`
|
||||
3. Remind to push changes
|
||||
|
||||
## Usage Examples
|
||||
|
||||
```bash
|
||||
# Full documentation release
|
||||
claude /release-docs
|
||||
|
||||
# Preview changes without writing
|
||||
claude /release-docs --dry-run
|
||||
|
||||
# After adding new agents
|
||||
claude /release-docs
|
||||
```
|
||||
Reference in New Issue
Block a user