← ClaudeAtlas

cpp-projectlisted

Set up a new C++20 project in Tsukini's way with the setup.sh of the cpp_project_template repository (TsukiNi22/cpp_project_template) - name / core class renaming, kind of project (binary, static .a or shared .so library, header-only; RPM/DEB/Arch packages of every variant, Windows MinGW-w64 build and packages), libutils v4 or not, exception codes, GTest tests, the CI/CD workflows of the template (dispatch, unit tests, build, packages, GitHub release from the CHANGELOG, docs) and the optional gh-pages branch (signed packages repository + docs), install script, README/CHANGELOG/docs written by the template, xstyle pre-commit hook - using the other skills (cmake-style, cpp-class, libutils-exception, readme-style, git-conventions, ci-cd, html-doc). Use whenever the user wants to create, bootstrap, initialize or scaffold a new C++ project or repository.
TsukiNi22/ai-utils · ★ 1 · AI & Automation · score 74
Install: claude install-skill TsukiNi22/ai-utils
# New C++ project `<name>` (a skill) = the folder of that skill: `~/.claude/skills/<name>` (setup.sh) or `${CLAUDE_SKILL_DIR}/../../*/<name>` (plugin of the marketplace). The base is always **`cpp_project_template`** and **its own `setup.sh`** (local clone `~/personal_delivery/cpp/cpp_project_template`, otherwise `https://github.com/TsukiNi22/cpp_project_template.git`): it renames, adapts the copy to the kind, writes the README, the CHANGELOG, the docs and the gh-pages branch. This skill drives it without git actions, then completes what it does not do (libutils freshness, no-libutils, `.gitignore`, the custom CI/CD, the checks). Skill synced with the template at `d3fd2a1` (2026-10-30: the packages `setup.sh` only registers the mirror, `--install` installs; before: Arch Linux packages, xstyle pre-commit hook, setup workflow fixes; before: Windows build, one CMake for every kind, `SRC` / `SRC_SHARED`, workflows dispatch / unit-tests / build / build-packages / release / docs, gh-pages, `install.sh`, CHANGELOG written by `setup.sh`, libutils `>= 4.1.0`): when its `HEAD` is newer (`git -C <clone> log --oneline 7fa7c9f..HEAD`, and `origin/main` after a `git fetch`), read its README (*Quick Setup*, *Generated project*, *Workflows/Release*) and its `setup.sh --help` before relying on the steps below. The other skills, each loaded when its step comes: `cmake-style` (CMake), `cpp-class` (classes, header question, main), `libutils-exception` (codes), `readme-style`, `git-conventions`