원클릭으로
cicd-pipeline
Generate CI/CD workflows (GitHub Actions, or self-hosted Woodpecker via provider)
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Generate CI/CD workflows (GitHub Actions, or self-hosted Woodpecker via provider)
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Flow: Auto - Full Issue Lifecycle in One Shot - Complete end-to-end workflow: start worktree → analyze issue → ELI5 plan + necessity gate → implement ...
Run quality checks (lint + test + typecheck + security) without committing
Flow: Finish - Quality Gates, Commit, Push, and Create PR - Run quality checks, commit changes, push the branch, and create a pull request.
Flow Commands - Streamlined worktree-based development workflow. No locks, no Redis - just git.
Flow: Merge PR and Clean Up - Merge the current branch's PR, then clean up the worktree and branch.
Diagnose flow workflow setup and environment
| name | cicd-pipeline |
| description | Generate CI/CD workflows (GitHub Actions, or self-hosted Woodpecker via provider) |
Generate CI/CD workflows from your Makefile targets. Defaults to GitHub Actions;
set pipeline.provider: woodpecker (or both) in .claude/cicd.yml to emit a
self-hosted Woodpecker .woodpecker.yml. For a hardened self-hosted pipeline
(secret-scan + image-security + runtime-smoke) and to scaffold the Woodpecker
server/agent, use /cicd-woodpecker instead.
.claude/cicd_tasks.yml exists, use it to inform pipeline generation:if [ -f ".claude/cicd_tasks.yml" ]; then
echo "Found cicd_tasks.yml manifest - pipeline will use manifest-defined steps"
# The manifest defines plan steps (lint, test, deploy, etc.) with exact commands.
# Pipeline generation should use these commands instead of defaults.
fi
When a manifest is present, the generated pipeline YAML should:
make <target> for steps not in the manifestlib/cicd:PYTHONPATH="$PWD/lib:$HOME/Projects/claude-power-pack/lib:$PYTHONPATH" python3 -m lib.cicd detect --quiet
PYTHONPATH="$PWD/lib:$HOME/Projects/claude-power-pack/lib:$PYTHONPATH" python3 -m lib.cicd pipeline
Review output with the user. Show the generated workflow YAML.
Check for existing files before writing:
.github/workflows/ci.yml exists, ask before overwritingWrite files if approved:
PYTHONPATH="$PWD/lib:$HOME/Projects/claude-power-pack/lib:$PYTHONPATH" python3 -m lib.cicd pipeline --write
## CI Pipeline Generated
Framework: {framework} ({package_manager})
Files created:
.github/workflows/ci.yml - CI pipeline with lint, test, build
Triggers: push to main, pull requests
Targets: make lint, make test, make typecheck (if available)
To view: cat .github/workflows/ci.yml
make <target> as steps (not direct tool commands).claude/cicd.yml if present.claude/cicd.yml:
pipeline:
provider: github-actions # github-actions | woodpecker | both
branches:
main: [lint, test, typecheck, build, deploy]
pr: [lint, test, typecheck]
matrix:
python: ["3.11", "3.12"]
provider: woodpecker (or both) and see
/cicd-woodpecker + docs/skills/woodpecker-ci.md for the hardening stages.