install-workflow

Create GitHub Actions workflows for automated package building and distribution. Use in package phase to automate .mojopkg building and release creation.

⭐8stars🔀4forks📁View on GitHub🕐Updated Jan 3, 2026

When & Why to Use This Skill

This Claude skill automates the generation of GitHub Actions workflows specifically designed for software package building and distribution. It streamlines the DevOps pipeline by creating standardized YAML configurations for building .mojopkg files, managing semantic versioning, and automating the creation of GitHub releases, ensuring a reliable and repeatable delivery process.

Use Cases

  • Automating the end-to-end build and release process of .mojopkg files whenever a new version tag (e.g., v1.0.0) is pushed to the repository.
  • Configuring manual 'workflow_dispatch' triggers to allow developers to generate and distribute packages on-demand with custom parameters.
  • Implementing CI validation in pull requests to ensure that code changes do not break the packaging scripts or environment setup.
  • Standardizing the release workflow by automatically uploading build artifacts to GitHub Releases and managing environment dependencies.
nameinstall-workflow
descriptionCreate GitHub Actions workflows for automated package building and distribution. Use in package phase to automate .mojopkg building and release creation.
mcp_fallbacknone
categoryci
user-invocablefalse

CI Package Workflow Skill

Create GitHub Actions workflows for automated packaging.

When to Use

  • Package phase of development
  • Automating release process
  • Building distributable packages
  • Creating GitHub releases

Quick Reference

name: Build Packages
on:
  push:
    tags:
      - 'v*'
  workflow_dispatch:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Build Packages
        run: ./scripts/build_all_packages.sh
      - uses: softprops/action-gh-release@v1
        with:
          files: packages/*.mojopkg

Workflow Structure

Triggers

on:
  push:
    tags:
      - 'v*.*.*'  # Semantic versioning
  workflow_dispatch:    # Manual trigger

Jobs

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Setup Mojo
        run: # Install Mojo environment
      - name: Build Packages
        run: ./scripts/build_all_packages.sh
      - name: Create Release
        uses: softprops/action-gh-release@v1

Workflow Types

1. Build on Tag Release

Automatically build when version tag created:

on:
  push:
    tags:
      - 'v*'

2. Build on PR

Validate packaging on pull requests:

on:
  pull_request:
    paths:
      - 'src/**'
      - 'scripts/build_*.sh'

3. Manual Trigger

Allow on-demand builds with parameters:

on:
  workflow_dispatch:
    inputs:
      version:
        description: 'Version to build'
        required: true

Best Practices

  • Cache dependencies between runs
  • Upload artifacts for inspection
  • Create GitHub releases with notes
  • Test installation in clean environment
  • Tag releases with semantic versioning
  • Document build requirements

Error Handling

Error Fix
Action version invalid Use latest stable version (v4, not @main)
Missing environment Add setup step before build
Build script not found Verify script path and permissions
Artifact not uploaded Check build produces expected files

References