github-actions

Automate GitHub Actions CI/CD configuration and debugging for cross-platform builds.

Updated Oct 25, 2025
One-click install
npx skills add https://github.com/bartoszwarzocha/kalahari --skill github-actions-bartoszwarzocha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-actions
Source: https://github.com/bartoszwarzocha/kalahari/tree/main/.claude/skills/github-actions
Command: npx skills add https://github.com/bartoszwarzocha/kalahari --skill github-actions-bartoszwarzocha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes CI/CD setup across Windows, Linux, and macOS with predefined workflows, build matrices, and common failure patterns.

Core Features & Use Cases

  • Project CI Structure: Clear structure under .github/workflows/ (ci-windows.yml, ci-linux.yml, ci-macos.yml).
  • Build Matrix: Platform-specific compilers, generators, and triplets to ensure compatibility.
  • Best Practices: Cache vcpkg, handle timeouts, and provide debugging tips.
  • Workflow Template: Reusable workflow blocks for configure, build, and test.

Quick Start

Add the provided ci-windows.yml, ci-linux.yml, and ci-macos.yml to your .github/workflows to enable cross-platform builds.

Frequently Asked Questions about github-actions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up CI/CD workflows for cross-platform builds on Windows, Linux, and macOS?

Cross-platform CI/CD workflows automate builds across operating systems using platform-specific compilers and generators. This Skill provides ready-to-use workflow templates (ci-windows.yml, ci-linux.yml, ci-macos.yml) that configure MSVC, GCC, and Clang toolchains, handle vcpkg dependencies, and manage build matrices—eliminating manual per-platform setup and ensuring consistent output.

Can I use GitHub Actions with vcpkg and Ninja for multi-platform C++ builds?

Yes. GitHub Actions workflows can integrate vcpkg dependency management and Ninja build generation across platforms. This Skill standardizes that integration by providing matrix configurations that pair each platform with its optimal compiler and generator, caching vcpkg artifacts, and handling timeouts and submodule checkout automatically.

What's the best way to cache dependencies and handle build matrices in GitHub Actions?

Build matrices in GitHub Actions run parallel jobs for each platform-compiler combination, reducing total time. Caching vcpkg packages and build artifacts between runs avoids reinstalling dependencies. This Skill applies cache strategies and matrix syntax to Debug and Release configurations, cutting redundant compilation and dependency resolution.

How do I debug GitHub Actions workflows when builds fail across different platforms?

GitHub Actions failures often stem from platform-specific toolchain issues, timeout limits, or missing submodules. This Skill includes workflow debugging guidance, timeout controls, robust error handling, and artifact publishing for release builds—surfacing logs and binaries so you identify whether failures are compiler, dependency, or configuration issues.

Can I automate release artifact publishing from GitHub Actions workflows?

Yes. GitHub Actions can build, test, and publish release artifacts after successful matrix builds. This Skill includes artifact publishing patterns for release builds, ensuring binaries generated across Windows, Linux, and macOS are collected and made available without manual intervention.

Do I need to manage submodules in GitHub Actions workflows?

Submodules must be explicitly checked out during workflow runs; standard checkout does not fetch them by default. This Skill includes submodule checkout configuration in its workflow templates, ensuring dependencies tracked as submodules are pulled and built correctly across all platforms.