skills.rest
Dicklesworthstone
DicklesworthstoneCOMMUNITY
Explore all skills by this author →
Website𝕏@doodlesteinGitHub

dsr

Reuse GitHub Actions workflows locally via nektos/act for cross-platform release builds.

29|4|Updated Jan 30, 2026
Search Tags:#security#build#release#workflows#fallback#ci#act
One-click install
npx skills add https://github.com/Dicklesworthstone/doodlestein_self_releaser --skill dsr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dsr
Source: https://github.com/Dicklesworthstone/doodlestein_self_releaser/tree/main
Command: npx skills add https://github.com/Dicklesworthstone/doodlestein_self_releaser --skill dsr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, curl, gh, jq, docker, act, minisign, syft.

What problem does it solve?

Replaces blocked or slow GitHub Actions pipelines with a local fallback release infrastructure that builds across platforms and prepares artifacts for release.

Core Features & Use Cases

  • Workflow reuse: Reuses existing GitHub Actions workflows locally via nektos/act to reproduce release steps without the cloud queue.
  • Cross‑platform builds: Builds Linux (via act), macOS, and Windows targets via native SSH on dedicated build hosts.
  • Security & provenance: Generates SBOMs and signs artifacts to maintain supply chain integrity.
  • Queue detection & fallback: Detects throttling and automatically orchestrates local builds and artifact uploads to releases.
  • Extensible tooling: Supports artifact naming, releases, signing, and optional attachments through a cohesive CLI.

Quick Start

Install dsr, configure your build hosts, and run a throttling check to trigger a fallback when needed.

Frequently Asked Questions about dsr

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

FAQPage Schema
How do I run GitHub Actions workflows locally when CI is throttled?▼

GitHub Actions workflows can run locally when CI is throttled by using nektos/act to reuse existing workflows, automatically detecting queue limits and orchestrating local builds to prepare cross-platform release artifacts.

What is a fallback release infrastructure for CI pipelines?▼

Fallback release infrastructure for CI pipelines replaces blocked or slow cloud queues with local builds across Linux, macOS, and Windows, maintaining supply chain integrity through SBOM generation and artifact signing.

How do I build cross-platform releases locally for Linux, macOS, and Windows?▼

Cross-platform releases are built locally by running Linux targets via nektos/act and connecting to macOS and Windows targets through native SSH on dedicated build hosts to prepare artifacts.

Do I need Docker and act to reuse existing GitHub Actions workflows locally?▼

Yes, Docker and act are required, along with git, curl, gh, jq, minisign, and syft, to reuse existing GitHub Actions workflows locally and handle artifact signing and SBOM generation.

Can I generate SBOMs and sign artifacts during a local release build?▼

Yes, SBOMs can be generated and artifacts signed during a local release build using built-in security tooling with syft for SBOM generation and minisign for signing to maintain supply chain integrity.

When should I avoid using a local fallback for GitHub Actions releases?▼

A local fallback for GitHub Actions releases should be avoided if you lack dedicated macOS and Windows build hosts for native SSH, or if your environment cannot support Docker for running act to reproduce cloud workflows.

Related Skills

Explore More Software Engineering Skills→
x-TheFoxx-TheFox

github-auth

Automate GitHub authentication setup for tokens, SSH keys, and gh login.

Community
Intermediate
dodygdodyg

dotnet-github-releases

Create and manage GitHub Releases for .NET projects with tag-based workflows.

Community
Intermediate
vecearvecear

artifact-sbom-publisher

no

Community
Advanced
KingInYellowsKingInYellows

ci-conventions

Standardize CI failure analysis for self-hosted GitHub Actions runners.

Official
Advanced