gitlab-helm-deploylisted

# Generate GitLab CI/CD + Helm chart Generate a GitLab CI/CD pipeline and a Helm chart that builds the current project with kaniko, pushes to the GitLab Container Registry, and deploys to a Kubernetes namespace via a user-provided kubeconfig. Reusable across apps: inspect the repo first, ask for the unknowns, then generate only the stages and templates that apply. If no Dockerfile exists, generate one tailored to the detected runtime. ## When this fires The user wants to set up CI/CD for a project that will deploy to a Kubernetes namespace they have access to via a kubeconfig file. They will provide that kubeconfig as a base64-encoded GitLab CI variable named `KUBE_CONFIG_B64`. Build is **kaniko**, registry is **GitLab Container Registry**, deploy is **Helm**. If the user wants something different (Argo CD, Flux, plain `kubectl apply`, a cloud-native registry, Docker Hub, GitHub Actions), stop and confirm before proceeding. This skill is opinionated. ## Step 1: Inspect the repo first (always) Before writing a single file, read these. Then summarize what you found in 4-8 lines and ask the user about anything ambiguous **before** generating files. 1. **Runtime & build** - `Dockerfile`: base image, exposed port, `CMD`/`ENTRYPOINT`, `HEALTHCHECK`. **If missing, plan to generate one in Step 4.** - `package.json` / `pyproject.toml` / `go.mod` / `Cargo.toml` / `composer.json`: language, framework, scripts, runtime version (engines, python_requires, go directive). - L