Menú
Covers CI/CD patterns using GitHub Actions with reusable workflows. Use when setting up pipelines, Taskfiles, or Dockerfiles for Datum Cloud services.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Covers GitHub conventions for pull requests, issues, and comments including linking, language style, formatting, and callout syntax. Use when creating PRs, writing issues, or posting comments on Datum Cloud repositories.
Turn raw engineering notes, PR/issue links, commit messages, or a one-line feature description into a changelog entry for Datum Cloud's GitHub Discussions Changelog category: a benefit-led title plus a markdown body, drafted for users and ready to hand off for final capture and publish. Use when someone says "write a changelog entry", "announce this in the changelog", or "post this to the changelog discussions" — this is the community-facing changelog POST, not the Keep a Changelog release file (that lives in `gtm-templates`).
Provides templates for go-to-market communications including blog posts, changelogs, social media, and enablement briefs. Use when writing launch announcements or marketing content.
Create a new GitHub release. Verifies CI is green on the release commit and refreshes the third-party NOTICE file before tagging, determines the next version from the latest tag, summarizes merged PRs since the last release, drafts release notes in the established style, and publishes via gh release create. Works for any datum-cloud service repository.
Scan a project repository for strict AGPL-3.0 license compliance across Go, Rust, and JavaScript/React codebases. Use this skill whenever the user asks to check, audit, verify, or enforce AGPL license compliance on a project, repo, or codebase. Triggers on phrases like "check agpl compliance", "audit license headers", "is this project agpl compliant", "scan for license headers", "check my license files", "agpl audit", or any request involving ensuring a project is properly licensed under AGPL. Always use this skill — don't wing AGPL compliance checks from general knowledge.
Covers producing weekly operational reports for the Datum AI Edge. Use when asked for an ops review, traffic report, latency analysis, provisioning report, or edge performance summary. Guides metric queries, anomaly detection, and publishing to datum-cloud/engineering.
| name | datum-ci |
| description | Covers CI/CD patterns using GitHub Actions with reusable workflows. Use when setting up pipelines, Taskfiles, or Dockerfiles for Datum Cloud services. |
This skill covers CI/CD patterns for Datum Cloud services.
Services use GitHub Actions with reusable workflows from datum-cloud/actions.
| File | Purpose |
|---|---|
github-actions.md | Workflow patterns |
validate → build → publish → deploy
# .github/workflows/ci.yaml
name: CI
on:
push:
branches: [main]
pull_request:
branches: [main]
jobs:
validate:
uses: datum-cloud/actions/.github/workflows/go-validate.yaml@main
with:
go-version: "1.21"
build:
needs: validate
uses: datum-cloud/actions/.github/workflows/container-build.yaml@main
with:
dockerfile: Dockerfile
context: .
secrets:
registry-username: ${{ secrets.REGISTRY_USERNAME }}
registry-password: ${{ secrets.REGISTRY_PASSWORD }}
publish:
needs: build
if: github.ref == 'refs/heads/main'
uses: datum-cloud/actions/.github/workflows/container-publish.yaml@main
with:
image-name: myservice
sign-image: true
secrets:
registry-username: ${{ secrets.REGISTRY_USERNAME }}
registry-password: ${{ secrets.REGISTRY_PASSWORD }}
signing-key: ${{ secrets.COSIGN_PRIVATE_KEY }}
Use Taskfile for local development:
# Taskfile.yaml
version: "3"
tasks:
generate:
desc: Run code generation
cmds:
- go generate ./...
- controller-gen object paths="./pkg/apis/..."
lint:
desc: Run linters
cmds:
- golangci-lint run ./...
test:
desc: Run tests
cmds:
- go test -race -coverprofile=coverage.out ./...
build:
desc: Build binary
cmds:
- go build -o bin/myservice ./cmd/myservice
docker-build:
desc: Build container image
cmds:
- docker build -t myservice:local .
# Build stage
FROM golang:1.21 AS builder
WORKDIR /workspace
COPY go.mod go.sum ./
RUN go mod download
COPY . .
RUN CGO_ENABLED=0 GOOS=linux go build -o /myservice ./cmd/myservice
# Runtime stage
FROM gcr.io/distroless/static-debian12:nonroot
COPY --from=builder /myservice /myservice
USER nonroot:nonroot
ENTRYPOINT ["/myservice"]
github-actions.md — Detailed workflow patterns