github-actions

Guide GitHub Actions design for JavaScript, Docker, and composite actions.

Updated Sep 29, 2025
One-click install
npx skills add https://github.com/aRustyDev/homebrew-tap --skill github-actions-arustydev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-actions
Source: https://github.com/aRustyDev/homebrew-tap/tree/main/.claude/skills/github-actions
Command: npx skills add https://github.com/aRustyDev/homebrew-tap --skill github-actions-arustydev

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Guides developers to design, implement, and publish robust GitHub Actions across JavaScript/TypeScript, Docker, and composite formats, with reusable patterns and marketplace readiness in mind.

Core Features & Use Cases

  • Templates and boilerplates for TypeScript/JavaScript actions, Docker actions, and composite actions.
  • Guidance on action.yml structure, branding, inputs, outputs, permissions, and testing.
  • Best practices for publishing, versioning, and integrating with CI workflows across repositories.

Quick Start

Follow the provided templates to scaffold a new action project tailored to your chosen runtime.

Frequently Asked Questions about github-actions

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

FAQPage Schema
How do I create a GitHub Action with TypeScript and Docker?

To create a GitHub Action, use templates for TypeScript, JavaScript, Docker, or composite formats. Configure the action.yml file with required inputs, outputs, and branding to ensure proper runtime execution.

What is the correct structure for an action.yml file?

The action.yml file defines your GitHub Action's metadata, specifying required inputs, outputs, and branding. Proper configuration ensures reliable execution and marketplace readiness for JavaScript, Docker, or composite actions.

How do I publish and version GitHub Actions to the marketplace?

Publish and version GitHub Actions by following best practices for tagging releases and integrating CI workflows. This ensures reliable distribution across multiple repositories and marketplace readiness.

Can I use composite actions to reuse CI/CD workflows across repositories?

Composite actions allow you to combine multiple workflow steps into a single reusable action. This pattern simplifies CI/CD automation and testing across multiple repositories without writing custom JavaScript or Docker code.

What's the best way to test GitHub Actions before publishing?

Test GitHub Actions by integrating them into CI workflows before publishing. Follow provided patterns for JavaScript, TypeScript, and Docker actions to validate inputs, outputs, and permissions reliably.

When should I use a Docker action instead of a JavaScript action?

Use a Docker action when you need a specific Linux environment or dependencies not available in JavaScript. JavaScript and TypeScript actions run faster directly on the runner, while Docker provides isolated containerized execution.