github-actions

Generate GitHub Actions workflows for React Native iOS and Android artifact builds.

28|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/bidah/react-native-hifi --skill github-actions-bidah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-actions
Source: https://github.com/bidah/react-native-hifi/tree/main/skills/github-actions
Command: npx skills add https://github.com/bidah/react-native-hifi --skill github-actions-bidah

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Building reliable React Native CI pipelines that produce inspectable iOS simulator and Android emulator artifacts is hard, and this skill captures reusable workflows, artifact uploads, and download-ready metadata in one place.

Core Features & Use Cases

  • Reusable composite actions for iOS simulator .app.tar.gz builds and Android emulator .apk builds that resolve RN project folders, variant names, and custom identifiers.
  • Workflow wiring guidance that installs Node, CocoaPods, and Gradle tooling, invokes both platform jobs, and surfaces artifact names, IDs, and URLs centrally.
  • Artifact retrieval lessons showing how to use gh run download and GitHub REST API calls to fetch artifacts and how to keep permissions and naming deterministic.

Quick Start

Ask the agent to assemble a GitHub Actions workflow that launches the reusable RN iOS and Android composite jobs, uploads artifacts, and prints the artifact IDs for gh downloads.

Frequently Asked Questions about github-actions

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

FAQPage Schema
How do I build React Native iOS simulator and Android emulator artifacts in GitHub Actions CI?

To build React Native CI artifacts in GitHub Actions, use reusable composite actions that resolve project folders and variants to produce iOS simulator `.app.tar.gz` and Android emulator `.apk` files. Workflows install Node, CocoaPods, and Gradle tooling to invoke platform build jobs.

How do I upload and retrieve React Native build artifacts using the gh CLI?

Upload React Native build artifacts using the `actions/upload-artifact` action, which exposes artifact-name, ID, and URL outputs. Retrieve these artifacts deterministically via `gh run download` commands or GitHub REST API calls for automated downstream downloads.

What's the best way to structure a GitHub Actions workflow for React Native iOS and Android builds?

The best way to structure React Native GitHub Actions workflows is wiring separate iOS and Android composite jobs that install platform-specific tooling, invoke builds, and centrally surface artifact metadata. This ensures deterministic naming and permissions for artifact retrieval.

Does this GitHub Actions workflow provide outputs for automated artifact downloads?

Yes, the GitHub Actions workflows expose artifact-name, artifact ID, and artifact URL outputs. These outputs enable automated downloads using `gh run download` or GitHub REST API calls, ensuring artifacts are retrievable programmatically after CI completion.

Can I use custom identifiers and variant names for React Native Android emulator APK builds?

Yes, the reusable composite actions for Android emulator builds resolve custom variant names and identifiers. This allows you to specify particular Gradle build variants and output identifiers for your `.apk` artifacts within the GitHub Actions CI pipeline.

Why do my GitHub Actions React Native artifact names and permissions need to be deterministic?

Deterministic artifact naming and permissions are required to reliably fetch React Native build artifacts via `gh run download` and GitHub REST API calls. Consistent naming ensures automated retrieval scripts locate the correct iOS simulator and Android emulator outputs without failure.