Agent skill · software engineering · jeremylongshore
coreweave-ci-integration
Integrate CoreWeave deployments into CI/CD pipelines with GitHub Actions.
Why this skill is useful
Provides specific GitHub Actions workflows and Kubernetes commands for deploying to CoreWeave that the AI wouldn't reliably generate on its own.
What it needs
Requires docker, kubectl installed locally. Requires coreweave account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
CoreWeave CI Integration Community-contributed. Not affiliated with, endorsed by, or sponsored by CoreWeave, Inc. CoreWeave is a registered trademark of CoreWeave, Inc. Overview Set up CI/CD for CoreWeave GPU cloud workloads: run unit tests with mocked Kubernetes clients on every PR, deploy inference containers to CoreWeave namespaces on merge to main, and validate GPU resource requests against quota. CoreWeave uses standard Kubernetes APIs with GPU-specific scheduling, so CI pipelines authenticate via kubeconfig and manage deployments through kubectl. GitHub Actions Workflow Prerequisites A repository with protected branches and a trusted runner policy. Mocked tests that need no cluster credential, plus a dedicated low-privilege staging identity for optional integration tests. Secret-manager-backed CI secrets available only to trusted, non-fork workflows. Instructions 1. Run deterministic unit and manifest validation on every pull request without credentials. 2. Run live integration checks only after merge or from an approved protected workflow. 3. Bound test resources, collect redacted pod events on failure, and revoke the staging identity if exposure is suspected. 4. Keep deploy approval and production rollout separate from the test job. Mock-Based Unit Tests Integration Tests Error Handling CI Issue Cause Fix ---------- ------- ----- KUBECONFIGDATA empty Secret not set Run gh secret set COREWEAVEKUBECONFIG --body "$(base64 -w0 kubeconfig)" Rollout timeout GPU nodes unavailable Increase --timeout or check CoreWeave GPU availability dashboard Image pull backoff GHCR auth expired Verify GHCRTOKEN secret and image registry permissions Quota exceeded GPU request exceeds namespace limit Check namespace quota with kubectl describe quota Pod pending No matching GPU node type Verify nodeSelector matches available GPU SKUs (A100, H100) Output A credential-free pull-request test lane and a trusted, scoped integration lane. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/coreweave-ci-integration