claude

woodpecker

Investigate failed Woodpecker CI pipelines through woodpecker-cli (state, step states, first failed step log tail) and author .woodpecker.yml

13 on GitHubby Josh Nicholsv0.2.0MITupdated yesterday
/

Plugin woodpecker from marketplace pickled-claude-plugins in technicalpickles/pickled-claude-plugins. Commands read from the repo's manifest — yesterday.

What it installs

Skills (2)

  • 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 service on localhost)

  • woodpecker-investigating-pipelines

    Use when a Woodpecker CI pipeline failed or its status is unclear - a red `ci/woodpecker/...` check, "Pipeline failed" from `gh pr checks`, a Woodpecker `/repos/<id>/pipeline/<n>` URL, "why did CI fail" in a repo that builds with Woodpecker, or a push that has no CI result at all.

View source on GitHub

More from technicalpickles/pickled-claude-plugins

All 26 plugins →

Knowledge management for Obsidian vaults and structured markdown repositories

11 skills · 7 commands · hooks

13

dev-tools

claude

Developer productivity tools and utilities

8 skills · 2 commands

13

git

claude

Git workflow tools: commits, PRs, review inbox, checkout, and work triage

8 skills

13

Meta-development tools for agentic workflows

4 skills

13

Navigate and execute commands in monorepo subprojects

1 skill · 2 commands · hooks

13

Closes the LSP activation gap end-to-end (detection, setup, activation, failure diagnosis) for Rust, TypeScript, and Ruby projects

2 skills · hooks

13

Maintain woodpecker?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins26 plugins