github-actions — community github-actions, lean-spec, community, ide skills

v1.0.0
GitHub

About this Skill

Ideal for DevOps Agents requiring seamless GitHub Actions workflow automation using the GitHub CLI GitHub Actions workflow management for LeanSpec. Use when triggering CI/CD workflows, monitoring build status, debugging failed runs, managing artifacts, or checking CI before releases.

codervisor codervisor
[0]
[0]
Updated: 3/10/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
42
Canonical Locale
en
Detected Body Locale
en

Ideal for DevOps Agents requiring seamless GitHub Actions workflow automation using the GitHub CLI GitHub Actions workflow management for LeanSpec. Use when triggering CI/CD workflows, monitoring build status, debugging failed runs, managing artifacts, or checking CI before releases.

Core Value

Empowers agents to trigger, monitor, and manage GitHub Actions workflows using the `gh` CLI tool, ensuring efficient Spec-Driven Development for modern AI-powered projects with features like periodic status checks and artifact management

Ideal Agent Persona

Ideal for DevOps Agents requiring seamless GitHub Actions workflow automation using the GitHub CLI

↓ Capabilities Granted for github-actions

Automating workflow interactions for the LeanSpec project
Monitoring GitHub Actions workflow status until completion
Downloading important artifacts before expiration

! Prerequisites & Limits

  • Requires GitHub CLI (`gh`) installation
  • Dependent on GitHub Actions workflow configuration
  • Artifact storage limited to 30 days by default

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is github-actions?

Ideal for DevOps Agents requiring seamless GitHub Actions workflow automation using the GitHub CLI GitHub Actions workflow management for LeanSpec. Use when triggering CI/CD workflows, monitoring build status, debugging failed runs, managing artifacts, or checking CI before releases.

How do I install github-actions?

Run the command: npx killer-skills add codervisor/lean-spec/github-actions. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for github-actions?

Key use cases include: Automating workflow interactions for the LeanSpec project, Monitoring GitHub Actions workflow status until completion, Downloading important artifacts before expiration.

Which IDEs are compatible with github-actions?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for github-actions?

Requires GitHub CLI (`gh`) installation. Dependent on GitHub Actions workflow configuration. Artifact storage limited to 30 days by default.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add codervisor/lean-spec/github-actions. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use github-actions immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

github-actions

Install github-actions, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

GitHub Actions Skill

Teach agents how to trigger, monitor, and manage GitHub Actions workflows for the LeanSpec project.

Core Principles

  1. Use GitHub CLI (gh) - All workflow interactions use the gh CLI tool
  2. Check Status Before Acting - Always verify current run status before triggering new ones
  3. Monitor Until Completion - Background workflows need periodic status checks
  4. Artifacts Are Ephemeral - Download important artifacts before they expire (default: 30 days)
  5. Respect Rate Limits - Don't poll too frequently (minimum 30s between checks)

Available Workflows

WorkflowFileTriggersPurpose
CIci.ymlpush, PR to mainBuild, test, lint (Node.js + Rust)
Publishpublish.ymlrelease, manualPublish to npm (all platforms)
Desktop Builddesktop-build.ymlpush, PR, manualBuild Tauri desktop apps
Copilot Setupcopilot-setup-steps.ymlpush, PR, manualSetup environment for Copilot agent

Quick Reference

Check Workflow Status

bash
1# List recent workflow runs
2gh run list --limit 10
3
4# View specific workflow runs
5gh run list --workflow ci.yml --limit 5
6gh run list --workflow publish.yml --limit 5
7
8# Get details of a specific run
9gh run view <run-id>
10
11# Watch a run in progress
12gh run watch <run-id>

Trigger Workflows

bash
1# Trigger CI manually (usually automatic on push/PR)
2gh workflow run ci.yml
3
4# Trigger publish (dev version)
5gh workflow run publish.yml --field dev=true
6
7# Trigger publish (dry run - validates without publishing)
8gh workflow run publish.yml --field dev=true --field dry_run=true
9
10# Trigger desktop build
11gh workflow run desktop-build.yml

Debug Failed Runs

bash
1# View failed run logs
2gh run view <run-id> --log-failed
3
4# View full logs
5gh run view <run-id> --log
6
7# Re-run failed jobs only
8gh run rerun <run-id> --failed
9
10# Re-run entire workflow
11gh run rerun <run-id>

Manage Artifacts

bash
1# List artifacts from a run
2gh run view <run-id>
3
4# Download all artifacts from a run
5gh run download <run-id>
6
7# Download specific artifact
8gh run download <run-id> --name ui-dist
9gh run download <run-id> --name binaries-linux-x64

Decision Tree

Need to check if build passing?
└─> gh run list --workflow ci.yml --limit 1

Need to publish packages?
├─> Production: Create GitHub Release (recommended)
└─> Testing: gh workflow run publish.yml --field dev=true

Workflow failed?
├─> View logs: gh run view <id> --log-failed
├─> Transient: gh run rerun <id> --failed
└─> Real issue: Fix locally, push, let CI re-run

Need build artifacts?
└─> gh run download <run-id> --name <artifact-name>

Reference Documentation

Related Skills

Looking for an alternative to github-actions or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer