woodpecker-authoring-pipelines
Use when writing or editing `.woodpecker.yml` or `.woodpecker/*.yaml`, porting a GitHub Actions or other CI config to Woodpecker, checking whether a Woodpecker config is valid, or when a Woodpecker step behaves differently than it does locally (shell syntax, file permissions, a s
Install
npx skills add https://github.com/technicalpickles/pickled-claude-plugins/tree/main/plugins/woodpecker/skills/woodpecker-authoring-pipelines
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install technicalpickles-pickled-claude-plugins@llmmart
git clone https://github.com/technicalpickles/pickled-claude-plugins.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole technicalpickles/pickled-claude-plugins collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Authoring Woodpecker pipelines
Validate before pushing
woodpecker-cli lint .woodpecker.yml # a file, or a .woodpecker/ directory
Exit 0 prints Config is valid. Errors print one line each and exit 1. It needs no server and no login, so it works on any machine with the CLI. A warning like "consider adding a when block with an event filter" is advice, not an error: without one, a step runs on every event.
woodpecker-cli exec runs a pipeline on the local machine. It defaults the event to manual, which skips any step filtered to push, so pass --pipeline-event push. What it mounts and how services behave depend on the backend and the machine; see references/runtime-facts.md.
Where "works locally, fails in CI" comes from
The shell, the user a step runs as, how services are named and what the checkout looks like all depend on the pipeline's backend, image and settings, so don't assume them. Add a throwaway probe step that prints id, ls -l /bin/sh and ls -ld .git, read its log, and fix against what it shows. Probes and the documented behavior (failure: ignore, skipped steps, event filters) are in references/runtime-facts.md.
Secrets
A step reads a secret with from_secret under environment: (or settings: for a plugin). Two settings on the secret itself decide whether the step gets it:
- Events. By default a secret is not exposed to
pull_requestpipelines. A step that runs on pull requests needs that event enabled on the secret. - Image filter. Leave it empty for a step with
commands:. A filter only works for plugin steps, and a normal step that uses a filtered secret fails the whole pipeline before any step runs.
Details and the exact error are in references/runtime-facts.md.
Conventions
Whether a repo gets Woodpecker at all is the user's call, usually stated in their rules or the repo's CLAUDE.md. Follow it without offering GitHub Actions as an alternative.
Trigger rules, base images and file layout are choices each repo makes. Read the repo's own CLAUDE.md and copy a sibling repo's pipeline before inventing structure.
Files (pickled-claude-plugins)
-
evals
-
eval_set.json 2.7 KB
Loading…
-
-
references
-
runtime-facts.md 3.5 KB
Loading…
-
-
SKILL.md 2.7 KB
--- name: woodpecker-authoring-pipelines description: Use when adding CI to a repo that has none and the user's setup puts that repo on Woodpecker, writing or editing `.woodpecker.yml` or `.woodpecker/*.yaml`, porting a GitHub Actions or other CI config to Woodpecker, giving a step a secret (`from_secret`) or advising what to set on a Woodpecker secret, checking whether a Woodpecker config is valid, or when a Woodpecker step behaves differently than it does locally (shell syntax, file permissions, a service on localhost). --- # Authoring Woodpecker pipelines ## Validate before pushing ```bash woodpecker-cli lint .woodpecker.yml # a file, or a .woodpecker/ directory ``` Exit 0 prints `Config is valid`. Errors print one line each and exit 1. It needs no server and no login, so it works on any machine with the CLI. A warning like "consider adding a `when` block with an `event` filter" is advice, not an error: without one, a step runs on every event. `woodpecker-cli exec` runs a pipeline on the local machine. It defaults the event to `manual`, which skips any step filtered to `push`, so pass `--pipeline-event push`. What it mounts and how services behave depend on the backend and the machine; see [references/runtime-facts.md](references/runtime-facts.md#local-runs-with-exec). ## Where "works locally, fails in CI" comes from The shell, the user a step runs as, how services are named and what the checkout looks like all depend on the pipeline's backend, image and settings, so don't assume them. Add a throwaway probe step that prints `id`, `ls -l /bin/sh` and `ls -ld .git`, read its log, and fix against what it shows. Probes and the documented behavior (`failure: ignore`, skipped steps, event filters) are in [references/runtime-facts.md](references/runtime-facts.md). ## Secrets A step reads a secret with `from_secret` under `environment:` (or `settings:` for a plugin). Two settings on the secret itself decide whether the step gets it: - **Events.** By default a secret is not exposed to `pull_request` pipelines. A step that runs on pull requests needs that event enabled on the secret. - **Image filter.** Leave it empty for a step with `commands:`. A filter only works for plugin steps, and a normal step that uses a filtered secret fails the whole pipeline before any step runs. Details and the exact error are in [references/runtime-facts.md](references/runtime-facts.md#secrets). ## Conventions Whether a repo gets Woodpecker at all is the user's call, usually stated in their rules or the repo's CLAUDE.md. Follow it without offering GitHub Actions as an alternative. Trigger rules, base images and file layout are choices each repo makes. Read the repo's own CLAUDE.md and copy a sibling repo's pipeline before inventing structure.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.