ci-cd

Builds secure desktop CI/CD pipelines with signing, SBOM, and release automation.

3|1|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/Probably-Group/Dev-AID --skill ci-cd-probably-group
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-cd
Source: https://github.com/Probably-Group/Dev-AID/tree/main/.dev-aid/skills/expert/ci-cd
Command: npx skills add https://github.com/Probably-Group/Dev-AID --skill ci-cd-probably-group

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps prevent insecure, unreliable CI/CD pipelines by providing production-grade guidance for desktop app releases, including code signing, notarization, artifact handling, and release automation.

Core Features & Use Cases

  • Secure signing & notarization workflows: Generate, import, and manage signing credentials safely for Apple (keychain + notarization) and Windows (certificate import + Authenticode signing).
  • Release automation with provenance: Produce verifiable release outputs using SBOM generation, checksums, and build provenance/attestations before publishing artifacts.
  • Workflow security guardrails: Enforce minimum permissions, action pinning by SHA, secret hygiene, concurrency controls, and anti-hallucination patterns to avoid CI/CD exploitation paths.

Use case: You’re building a Tauri/Electron desktop app and need a cross-platform pipeline that signs every artifact, notarizes macOS builds, generates SBOM/checksums, and creates a trustworthy GitHub release.

Quick Start

Ask the AI to generate a secure GitHub Actions workflow for a Tauri desktop release pipeline that signs macOS and Windows artifacts, creates SBOM/checksums, and publishes the GitHub release with SLSA provenance.

Frequently Asked Questions about ci-cd

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

FAQPage Schema
How do I set up a secure GitHub Actions workflow for Tauri desktop release pipelines?

To generate SILVA provenance for GitHub Actions releases, you create workflows that output build attestations, SBOMs, and checksums before deployment. This provides verifiable release metadata ensuring artifact trustworthiness and supply chain security for desktop applications.

Does this CI/CD pipeline support Apple notarization and Windows Authenticode code signing?

Yes, this CI/CD pipeline supports Apple notarization and Windows Authenticode code signing. It safely generates, imports, and manages signing credentials using macOS keychain for notarization and certificate import for Windows targets across cross-platform builds.

What's the best way to prevent common CI/CD threats in desktop app release automation?

The best way to prevent common CI/CD threats in desktop app release automation is by enforcing workflow security guardrails. These include minimum permissions, SHA-pinned actions, secret hygiene, concurrency controls, and anti-hallucination patterns to block CI/CD exploitation paths.

How do I generate SBOM and checksums for Electron release workflows?

To generate SBOM and checksums for Electron release workflows, you configure the CI/CD pipeline to produce verifiable release outputs. The workflow generates SBOM files and creates checksums before publishing artifacts to ensure trustworthy GitHub releases.

Why do I need secret-safe command patterns for code signing in CI/CD pipelines?

You need secret-safe command patterns for code signing in CI/CD pipelines to prevent credential leakage during the build process. Enforcing secret hygiene alongside minimum permissions and artifact verification ensures signing credentials remain protected against exploitation.