بنقرة واحدة
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.