GitHub Actions Skill

Scaffold and validate GitHub Actions workflows for Go and Hugo components.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/monamaret/rook-reference --skill github-actions-skill-monamaret
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: GitHub Actions Skill
Source: https://github.com/monamaret/rook-reference/tree/main/.tabnine/agent/skills/github-actions
Command: npx skills add https://github.com/monamaret/rook-reference --skill github-actions-skill-monamaret

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill prevents CI/CD workflow drift in the rook-reference monorepo by encoding the canonical GitHub Actions conventions into repeatable scaffolding and validation steps.

Core Features & Use Cases

  • Scaffold per-component Go CI workflows: Generates .github/workflows/ci-<component>.yml files that delegate to the shared reusable workflow (_go-ci.yml).
  • Scaffold Hugo site CI workflows: Produces Hugo build workflows (ci-<site-dir>.yml) with correct triggers and working directories.
  • Validate existing workflow files: Checks workflow files against references/workflow-conventions.md, reporting PASS/FAIL/WARN with the offending rule and line when possible.
  • Debug failing pipelines: Helps pinpoint the failing step and correct common issues such as working-directory, pinned action versions, or Go module paths.

Quick Start

Use the GitHub Actions skill to scaffold and validate a new per-service Go CI workflow for a newly added microservice.

Frequently Asked Questions about GitHub Actions Skill

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

FAQPage Schema
How do I scaffold GitHub Actions workflows for a new Go component?

Validate GitHub Actions workflow files by checking them against workflow conventions, reporting PASS, FAIL, or WARN with the offending rule and line number to ensure pinned action versions and correct path triggers.

How do I create Hugo site CI workflows with correct triggers?

Debug failing CI pipelines by pinpointing the failing step and correcting common issues such as incorrect working-directory paths, unpinned action versions, or invalid Go module paths.

What is Workload Identity Federation and when do I need it for GitHub Actions releases?

Yes, you can validate changes under `.github/workflows/` by enforcing correct `paths` triggers, reusable workflow delegation, and pinned action versions in conformance with workflow conventions.

Why does my reusable workflow delegation fail validation in a monorepo?

When adding new rook-server services, scaffold per-component Go CI workflows that delegate to the shared `_go-ci.yml` reusable workflow to maintain CI/CD compliance.