Claude-skill-registry install-workflow

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

install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/install-workflow" ~/.claude/skills/majiayu000-claude-skill-registry-install-workflow && rm -rf "$T"
manifest: skills/data/install-workflow/SKILL.md
source content

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

ErrorFix
Action version invalidUse latest stable version (v4, not @main)
Missing environmentAdd setup step before build
Build script not foundVerify script path and permissions
Artifact not uploadedCheck build produces expected files

References