---
name: "woodpecker-ci-community-engine"
description: "Run a lightweight, open-source community fork of Drone CI on your own servers."
metadata:
  author: "Woodpecker CI"
  version: "1.0.0"
  runtime_compatibility:
    - "codex"
    - "claude-code"
    - "cursor"
    - "windsurf"
triggers:
  - "deploy woodpecker ci"
  - "write .woodpecker.yaml"
  - "woodpecker ci docker agent"
permissions:
  fs_read: true
  fs_write: "workspace"
  shell_exec: false
  net_access: false
---

# Woodpecker CI Community Container-Native Pipelines

Deploys Woodpecker CI: configuring Woodpecker server and agent, writing .woodpecker.yaml, pipeline steps and services, secret encryption, caching plugins, and running builds on ARM64 / AMD64 architectures.

## When to Invoke
Invoke this skill whenever you need to:
- deploy woodpecker ci
- write .woodpecker.yaml
- woodpecker ci docker agent

## Execution SOP & Rules
1. Launch server and agent containers configuring WOODPECKER_HOST and VCS credentials.
2. Define .woodpecker.yaml with pipeline steps specifying container image and commands.
3. Attach service containers (e.g. Postgres, Redis) in the services block for integration testing.
4. Monitor build queue and agent execution in the Woodpecker web UI.

## Verification Checklist
- Run local linting, syntax validation, and type-checks before reporting completion.
- Ensure all created or modified files adhere to workspace boundaries and avoid uncommitted secrets.
- Verify tests or build commands exit cleanly with return code 0.