Slash Command393 repo starsupdated today

create-pipeline

The create-pipeline command scaffolds new multi-step workflows by analyzing repository context, detecting existing agents and skills, and generating pipeline components including Python detector hooks, agent manifests, and skill definitions. Use this command when you need to automate complex multi-stage processes like code review workflows, publishing pipelines, or safety verification systems, as it prevents duplication and integrates new pipelines into the routing infrastructure.

View source Repository: vexjoy-agent

Install in Claude Code

Copy

mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/notque/vexjoy-agent/HEAD/commands/create-pipeline.md -o ~/.claude/commands/create-pipeline.md

Then start a new Claude Code session; the slash command loads automatically.

Definition

create-pipeline.md

# create-pipeline

Entry point command for the Pipeline Creator meta-pipeline.

## Usage

```
/do create a pipeline for [task description]
```

## What It Does

1. **Context Detection** (`pipeline-context-detector` hook): Scans the repository for existing agents, skills, and hooks related to the task. Builds a JSON environment snapshot.
2. **Discovery** (`codebase-analyzer`): Analyzes existing components to prevent duplication and identify reusable patterns.
3. **Scaffolding** (fan-out via `workflow` skill, scaffolder phase): Dispatches parallel sub-agents to create:
   - Python detector hook (environment evaluation before LLM invocation)
   - Agent manifest (following `skills/skill-creator/references/agent-template.md`)
   - Skill definition (`SKILL.md` with phases and gates)
4. **Integration** (`routing-table-updater`): Injects the new pipeline into `/do` routing tables.

## Examples

```
/do create a pipeline for automated code review on push
/do create a pipeline for blog post publishing with voice validation
/do create a pipeline for database migration safety checks
```

## Routing

This command routes to `pipeline-orchestrator-engineer` with the `workflow` skill. The `/do` router recognizes these triggers:

- "create pipeline", "new pipeline", "scaffold pipeline"
- "build a pipeline for", "pipeline for"