How do I install the CI CD skill?

Run npx skillmds@latest add tomevault-io/ci-cd-22 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is CI CD safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with CI CD?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is CI CD free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

CI CD by tomevault-io — Agent Skill

Name: CI CD
Author: tomevault-io

CI CD

CI/CD pipeline for haven-docker including the GitHub Actions workflow for GHCR publishing, Makefile-driven DockerHub release, cosign image signing, and version management. Use when modifying build automation, release processes, or image signing. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

CI/CD

GitHub Actions — `docker-publish.yml`

Located at .github/workflows/docker-publish.yml.

Triggers

Schedule: daily at 12:28 UTC
Push: to main branch or semver tags (v*.*.*)
Pull request: against main

Pipeline steps

Checkout repo
Install cosign (skipped on PRs)
Set up Docker Buildx
Log into GHCR (ghcr.io) using GITHUB_TOKEN
Extract Docker metadata (tags, labels)
Build and push image (push skipped on PRs, uses GHA cache)
Sign image with cosign (skipped on PRs, uses Sigstore/Fulcio)

Registry

GHCR: ghcr.io/sudocarlos/haven-docker (automated via Actions)
DockerHub: sudocarlos/haven (manual via make release)

Manual DockerHub Release — `Makefile`

make release

This runs the push and tag targets:

Extracts version from the TAG= line in Dockerfile
Builds with docker buildx (no cache), pushes latest + version tags
Commits all changes, creates an annotated git tag dockerhub-<version>
Pushes commits and tags

Individual steps can be run separately with make push or make tag.

Prerequisites

Logged into DockerHub (docker login)
Docker Buildx configured

Version Management

The Haven version is pinned in Dockerfile:

ARG TAG=v1.2.0-rc2
ARG COMMIT=986c21b79c93779a449a52f6414ea267c83428bb

The Makefile extracts the version with:

VERSION := $(shell awk -F '=' '/TAG=/{print $$NF}' Dockerfile)

To bump: update TAG and COMMIT in Dockerfile, then run make release.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: ci-cd-22description: CI/CD pipeline for haven-docker including the GitHub Actions workflow for GHCR publishing, Makefile-driven DockerHub release, cosign image signing, and version management. Use when modifying build automation, release processes, or image signing. Use when this capability is needed.---# CI/CD## GitHub Actions — `docker-publish.yml`Located at `.github/workflows/docker-publish.yml`.### Triggers- **Schedule**: daily at 12:28 UTC- **Push**: to `main` branch or semver tags (`v*.*.*`)- **Pull request**: against `main`### Pipeline steps1. Checkout repo2. Install cosign (skipped on PRs)3. Set up Docker Buildx4. Log into GHCR (`ghcr.io`) using `GITHUB_TOKEN`5. Extract Docker metadata (tags, labels)6. Build and push image (push skipped on PRs, uses GHA cache)7. Sign image with cosign (skipped on PRs, uses Sigstore/Fulcio)### Registry- **GHCR**: `ghcr.io/sudocarlos/haven-docker` (automated via Actions)- **DockerHub**: `sudocarlos/haven` (manual via `make release`)## Manual DockerHub Release — `Makefile````bashmake release```This runs the `push` and `tag` targets:1. Extracts version from the `TAG=` line in `Dockerfile`2. Builds with `docker buildx` (no cache), pushes `latest` + version tags3. Commits all changes, creates an annotated git tag `dockerhub-<version>`4. Pushes commits and tagsIndividual steps can be run separately with `make push` or `make tag`.### Prerequisites- Logged into DockerHub (`docker login`)- Docker Buildx configured## Version ManagementThe Haven version is pinned in `Dockerfile`:```dockerfileARG TAG=v1.2.0-rc2ARG COMMIT=986c21b79c93779a449a52f6414ea267c83428bb```The Makefile extracts the version with:```makefileVERSION := $(shell awk -F '=' '/TAG=/{print $$NF}' Dockerfile)```**To bump**: update `TAG` and `COMMIT` in `Dockerfile`, then run `make release`.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/sudocarlos) — claim your Tome and manage your conversions.

Frequently asked questions