gh-aw-local-dev

Configure local gh-aw workflows by copying actions or switching to release mode.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/Mossaka/skills --skill gh-aw-local-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-aw-local-dev
Source: https://github.com/Mossaka/skills/tree/main/gh-aw-local-dev
Command: npx skills add https://github.com/Mossaka/skills --skill gh-aw-local-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When building and using gh-aw locally (not from a release), compiled workflows reference local actions such as actions/setup, which often don't exist in the target repository. This skill explains why these references break and how to resolve them by copying the required folders or switching to release mode for CI.

Core Features & Use Cases

  • Understand gh-aw action modes: dev (local), release (remote), and inline (embedded scripts) to select the appropriate reference strategy.
  • Provide practical steps to copy the actions/ folder or compile in release mode to ensure workflows run in both local development and CI.
  • Troubleshoot common forked-repo, CI/CD, and mixed local/CI scenarios to maintain consistent workflow behavior.

Quick Start

Follow this guide to configure local gh-aw development by copying the actions folder or switching to release mode.

Frequently Asked Questions about gh-aw-local-dev

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

FAQPage Schema
Why do compiled gh-aw workflows fail in local development?

Compiled gh-aw workflows fail in local development because they reference local actions, such as actions/setup, which often do not exist in the target repository.

What is the difference between dev mode and release mode in gh-aw action references?

Dev mode uses local actions while release mode references remote actions, allowing you to switch reference strategies to ensure workflows run consistently in both local development and CI.

How do I fix missing actions/setup references in forked OSS workflows?

To fix missing actions/setup references in forked OSS workflows, you can copy the required actions folder into the target repository or compile the workflows in release mode.

How do I validate workflow references for mixed local and CI scenarios?

To validate workflow references for mixed local and CI scenarios, detect the action mode and choose between copying the actions folder, using dev mode, or switching to release mode.

What is inline mode for embedded scripts in gh-aw workflows?

Inline mode is an action mode in gh-aw that uses embedded scripts, providing an alternative reference strategy alongside dev and release modes for workflow compilation.

When should I switch from dev mode to release mode for CI/CD workflows?

You should switch from dev mode to release mode for CI/CD workflows when compiled local references break, ensuring remote actions are used for consistent CI behavior.