← ClaudeAtlas

ci-cdlisted

CI and CD of a GitHub repository in Tsukini's way - the CI (build check, unit tests, style check with xstyle, coverage) and the CD (GitHub releases from the CHANGELOG, RPM/DEB packages and their gh-pages repository, container images on ghcr.io, PyPI, docs on gh-pages, dispatch to other repositories), always asking first what to run, runs the jobs in the user's Docker images (ghcr.io/tsukini22 ci / unit-tests / package / git from the docker-image repository) or else the smallest official image that has what is needed, follows his conventions (names, vars.RUNNER, ccache, set -euo pipefail, annotations, dispatch keywords), and when one of his images misses a tool, adds it to the docker-image repository (Dockerfile, version, CHANGELOG, README) with a local commit only. Used by the project setup skills (cpp-project, python-project) when the project is a GitHub repository. Use whenever the user wants a CI, a CD, a release / deployment / publication pipeline, a GitHub workflow / action, or to change one.
TsukiNi22/ai-utils · ★ 1 · DevOps & Infrastructure · score 74
Install: claude install-skill TsukiNi22/ai-utils
# CI / CD `SKILL_DIR` = the directory of this file. Templates: CI `templates/style.yml` (xstyle), `templates/python.yml` (pytest); CD `templates/release.yml` (GitHub release from the CHANGELOG section of the tag), `templates/pypi.yml` (trusted publishing), `templates/container.yml` (image on ghcr.io, docker-image way), `templates/dispatch-repository.yml` (repository_dispatch to another repository); the C/C++ build / tests / packages / dispatch / release / docs workflows are those of **cpp_project_template** (`.github/workflows/` of a project made by `cpp-project`, already there; for another C++ project: copied from the local clone `~/personal_delivery/cpp/cpp_project_template` or its GitHub repository, then `template` / `TEMPLATE_` / `Core` renamed and the `# Don't run on template repository` condition removed, like its `setup.sh`; section 5 of `cpp-project` says what each one does). **Called by the project setup skills** (`cpp-project`, `python-project`) when the project is a GitHub repository (`git remote -v` shows `github.com`, or the user creates it with `gh repo create`): they hand over the CI/CD step here. Check: `python3 SKILL_DIR/scripts/check_workflows.py [files]` (YAML, actionlint when installed, the conventions below). ## 1. Ask first, always (AskUserQuestion, French) Even when the request looks clear, confirm what the CI/CD must do (multiSelect), with the project's obvious choices pre-selected in the description. The popup takes 4 options per question and 4 que