Eve Pipelines Workflows

Automates your build, release, and deploy flows through declarative YAML manifests and a CLI. Pipelines chain steps with dependency graphs, built-in actions track BuildSpec and BuildRun records, and you can stream logs in real time. The canonical pattern is build once in test, then promote the same artifacts by release_id to staging and prod. Workflows add AI agent steps with conditional execution, step-level harness overrides, and multi-layer env merging. It handles the boring stuff like webhook triggers, secret interpolation, and job tracking so you don't wire it manually every time. The direct deploy bypass flag is a nice escape hatch when pipelines get in the way.

skills.sh installs: 309
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add incept5/eve-skillpacks --skill eve-pipelines-workflows --agent claude-code

Installs into .claude/skills of the current project.

Files

Eve Pipelines and Workflows

Use these patterns to automate build and deploy actions and invoke workflow jobs.

Pipelines (v2 steps)

Define pipelines under pipelines in .eve/manifest.yaml.
Steps can be action, script, or agent.
Use depends_on to control ordering.
Built-in actions include build, release, deploy, run, job, create-pr.
Run manually:
- eve pipeline list
- eve pipeline show <project> <name>
- eve pipeline run <name> --ref <sha> --env <env> --repo-dir ./my-app
Trigger blocks exist in the manifest; GitHub and Slack webhooks can create pipeline runs.

Built-in Actions

`build` action

Build actions create BuildSpec and BuildRun records that are tracked and observable:

Creates BuildSpec (defines what to build) and BuildRun (execution record) in the database
Outputs include build_id and image_digests map (service name to SHA256 digest)
These outputs automatically flow to dependent steps (release uses build_id)
Inspect builds independently: eve build show, eve build diagnose, eve build runs, eve build logs