github-actions_skill

Overview

This skill manages GitHub Actions workflows for LeanSpec. It helps trigger, monitor, debug, and retrieve artifacts using the GitHub CLI so you can automate CI/CD tasks cleanly and reproducibly. The skill encodes safe patterns: check status first, monitor runs, and download artifacts before they expire.

How this skill works

All interactions use the GitHub CLI (gh). The skill lists and inspects workflow runs, triggers manual workflow_dispatch inputs, watches runs until completion, views logs, reruns failed or full workflows, and downloads artifacts. It enforces conservative polling and explicit checks to avoid duplicate runs or rate-limit issues.

When to use it

• Manually trigger CI, publish, or platform builds
• Check build status before a release or merge
• Debug failed workflow runs and inspect logs
• Download build artifacts from completed runs
• Automate pre-release dry runs and validation

Best practices

• Always verify current run status before triggering a workflow to avoid duplicate runs
• Use gh run watch or periodic checks with minimum 30s intervals to respect rate limits
• Download important artifacts quickly—GitHub artifacts typically expire after 30 days
• Prefer dry_run/dev inputs for publish workflows to validate without releasing
• Rerun only failed jobs for transient issues; rerun full workflow for stateful or environment fixes

Example use cases

• Trigger a CI build and wait for completion before merging a PR
• Run a publish dry run to validate packaging, then perform the real publish
• Inspect failed CI logs, rerun failed jobs, and download artifacts for local debugging
• Build platform-specific desktop bundles and download platform artifacts for QA
• Check latest CI run on main before cutting a GitHub Release