devlab-cicd-onboardlisted

# DevLab CI/CD Onboard ## Purpose Use this Skill to introduce or evolve CI/CD in an application repository. It turns repository facts into a provider-neutral plan, then produces reviewed workflow and configuration changes for GitHub Actions, Jenkins, Woodpecker, or another established CI platform. It is an engineering workflow, not a platform-administration runbook. It does not create accounts, change global CI settings, install plugins, or access credentials. ## Inputs - Repository path or source archive. - Requested outcome: CI only, deployment pipeline, an environment change, or a migration between CI providers. - Optional target environments and the CI provider already used by the team. ## Outputs - A short repository and delivery-path assessment. - A reviewed pipeline design and project-local configuration template. - Workflow files or a patch when the repository has enough confirmed context. - A structured escalation when a CI platform, secret, runner, or deployment prerequisite needs an operator. ## Workflow 1. Inspect the repository before selecting a provider: language, package manager, tests, build output, containerization, deployment target, and any existing CI files. 2. Select the smallest provider-compatible path. Preserve an existing working provider unless the request explicitly asks for migration. For a new public repository, GitHub Actions is the default recommendation. 3. Separate configuration by ownership: - versioned repository