migrate-pipeline

This skill should be used when the user asks to "migrate from Jenkins to GitHub Actions", "move from GitLab CI to GitHub Actions", "convert my Jenkinsfile", "switch CI platforms", "migrate pipeline", "move from CircleCI", "upgrade my CI", "modernize my pipeline", or "refactor pipeline architecture". Migrates CI/CD pipelines between platforms or upgrades pipeline architecture -- Jenkins to GitHub Actions, Jenkins to GitLab CI, GitLab to GitHub Actions, CircleCI to GitHub Actions, Travis CI to GitHub Actions, Buildkite to GitHub Actions, and any other cross-platform migration, plus major version upgrades (reusable workflows adoption, composite actions refactoring, monorepo strategy changes). Produces a phased migration plan with feature parity mapping and rollback at each stage.

الانتقال إلى التثبيت

المستودع: TheMizeGuy/cicd-expert-public
آخر نشاط في المصدر: ٥ يوليو ٢٠٢٦ في ٠٤:٥٨
لغة SKILL.md المكتشفة: الإنجليزية
النجوم: ٠
التفرعات: ٠

خيارات التثبيت

يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.

npx skills add https://github.com/TheMizeGuy/cicd-expert-public --skill migrate-pipeline

يبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.

تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.

مراجعة ملفات المصدر

اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.

SKILL.md

تعليمات المصدر · معاينة للقراءة فقط

العودة إلى البحث العودة إلى التثبيت

cross-project-pipeline-audit

This skill should be used when the user asks to run a "cross-project pipeline audit", "multi-repo pipeline audit", or "audit all my pipelines" across 3+ repositories in parallel, or passes the `--team` flag on other skills. Dispatches the cicd-team-lead agent (running on the session model), which maps each repo's pipeline surface, partitions work into focused scopes (build validation, security posture, deployment path, runner fleet, observability, cross-repo patterns), dispatches parallel cicd-expert sub-agents (bounded by the fan-out budget), and consolidates findings into a unified report with overall verdict + per-repo deltas + cross-cutting pattern detection. Do NOT trigger on generic "audit my pipeline" (single-repo -- use `review-pipeline` or `audit-pipeline-security`).

2026-07-05

audit-pipeline-security

This skill should be used when the user asks to "audit my pipeline security", "is my CI secure", "pipeline security review", "supply chain audit", "check my workflow security", "harden my CI", "SLSA compliance", "action pinning audit", "are my actions pinned", "CI security check", or "pipeline security". Runs a CI/CD pipeline security and supply chain audit checking permissions (least privilege, GITHUB_TOKEN scoping), action pinning (SHA vs tag, CVE-2025-30066), script injection (attacker-controlled context), fork PR safety (pull_request vs pull_request_target), secret management (environment vs repo vs org scoping, OIDC), supply chain (SLSA, Sigstore, SBOMs, attestations, Scorecard, StepSecurity), runner isolation (trust zoning, ephemeral vs persistent), and workflow scanning (zizmor, CodeQL for Actions). Produces a pass/fail assessment per category with concrete remediation.

2026-07-05

cicd-expert

This skill should be used when the user mentions pipelines in the context of design, review, debugging, optimization, security, migration, self-hosted runners, or deployment, and the specific workflow is not obvious -- for example "design a pipeline for...", "review my CI", "pipeline is slow", "optimize this workflow", "secure my pipeline", "migrate from Jenkins to GitHub Actions", "audit my self-hosted setup". This is the main entry point for the CI/CD Expert plugin: it classifies the request, dispatches the cicd-expert agent (running on the session model), and routes to the right workflow (design / review / optimize / debug / audit-security / migrate / self-hosted-audit). If the scope is explicitly a cross-project audit (3+ repos OR "cross-project pipeline audit" OR `--team`), it routes to the `cross-project-pipeline-audit` skill instead.

2026-07-05

عرض الكل من هذا المستودع

name	migrate-pipeline
description	This skill should be used when the user asks to "migrate from Jenkins to GitHub Actions", "move from GitLab CI to GitHub Actions", "convert my Jenkinsfile", "switch CI platforms", "migrate pipeline", "move from CircleCI", "upgrade my CI", "modernize my pipeline", or "refactor pipeline architecture". Migrates CI/CD pipelines between platforms or upgrades pipeline architecture -- Jenkins to GitHub Actions, Jenkins to GitLab CI, GitLab to GitHub Actions, CircleCI to GitHub Actions, Travis CI to GitHub Actions, Buildkite to GitHub Actions, and any other cross-platform migration, plus major version upgrades (reusable workflows adoption, composite actions refactoring, monorepo strategy changes). Produces a phased migration plan with feature parity mapping and rollback at each stage.
argument-hint	[optional: source platform -> target platform, or migration scope]
allowed-tools	Agent, Read, Grep, Glob, Bash, TodoWrite, WebSearch, WebFetch, mcp__plugin_context7_context7__resolve-library-id, mcp__plugin_context7_context7__query-docs