averello/compound-engineering-plugin-mirror

mirror of https://github.com/EveryInc/compound-engineering-plugin.git synced 2026-06-26 12:23:01 +02:00

Files

T

Kieran Klaassen 4b0f058f2c refactor: Reduce core to 4 commands, extract workflow-automation and plugin-dev plugins

Based on PR feedback that 14 commands in core was too many:

- **compound-engineering-core** (14 agents, 4 commands, 5 skills)
  - Only 4 workflow commands: /workflows:plan, /workflows:review, /workflows:work, /workflows:compound
  - All code review agents stay in core (referenced by /workflows:review)

- **workflow-automation** (3 agents, 7 commands, 1 skill) - NEW
  - /resolve_pr_parallel, /plan_review, /resolve_parallel, /resolve_todo_parallel
  - /reproduce-bug, /triage, /changelog
  - bug-reproduction-validator, pr-comment-resolver, every-style-editor agents

- **plugin-dev** (3 commands, 2 skills) - NEW
  - /generate_command, /heal-skill, /create-agent-skill
  - skill-creator, create-agent-skills skills

All READMEs updated with "Works Best With" philosophy emphasizing that
core provides the foundation but real power comes from combining plugins.

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

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2025-12-15 17:15:12 -08:00

2.1 KiB

Raw Permalink Blame History

Workflow: Add a Script to a Skill

<required_reading> Read these reference files NOW:

references/using-scripts.md </required_reading>

## Step 1: Identify the Skill

Ask (if not already provided):

Which skill needs a script?
What operation should the script perform?

Step 2: Analyze Script Need

Confirm this is a good script candidate:

Same code runs across multiple invocations
Operation is error-prone when rewritten
Consistency matters more than flexibility

If not a good fit, suggest alternatives (inline code in workflow, reference examples).

Step 3: Create Scripts Directory

mkdir -p ~/.claude/skills/{skill-name}/scripts

Step 4: Design Script

Gather requirements:

What inputs does the script need?
What should it output or accomplish?
What errors might occur?
Should it be idempotent?

Choose language:

bash - Shell operations, file manipulation, CLI tools
python - Data processing, API calls, complex logic
node/ts - JavaScript ecosystem, async operations

Step 5: Write Script File

Create scripts/{script-name}.{ext} with:

Purpose comment at top
Usage instructions
Input validation
Error handling
Clear output/feedback

For bash scripts:

#!/bin/bash
set -euo pipefail

Step 6: Make Executable (if bash)

chmod +x ~/.claude/skills/{skill-name}/scripts/{script-name}.sh

Step 7: Update Workflow to Use Script

Find the workflow that needs this operation. Add:

<process>
...
N. Run `scripts/{script-name}.sh [arguments]`
N+1. Verify operation succeeded
...
</process>

Step 8: Test

Invoke the skill workflow and verify:

Script runs at the right step
Inputs are passed correctly
Errors are handled gracefully
Output matches expectations

<success_criteria> Script is complete when:

scripts/ directory exists
Script file has proper structure (comments, validation, error handling)
Script is executable (if bash)
At least one workflow references the script
No hardcoded secrets or credentials
Tested with real invocation </success_criteria>

2.1 KiB Raw Permalink Blame History