github-script

Write robust JavaScript for GitHub Actions using github-script best practices.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/maxfraieho/garden-seedling --skill github-script-maxfraieho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-script
Source: https://github.com/maxfraieho/garden-seedling/tree/main/gh-aw/skills/github-script
Command: npx skills add https://github.com/maxfraieho/garden-seedling --skill github-script-maxfraieho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing robust JavaScript for GitHub Actions can be error-prone without clear guidelines and consistent patterns. This skill consolidates best practices for using the github-script tool to drive automation reliably.

Core Features & Use Cases

  • Establishes standard logging, error handling, and output patterns with @actions/core and @actions/github.
  • Guides common use cases such as accessing inputs, setting outputs, and performing GitHub API calls within actions.
  • Useful for teams adopting github-script in CI workflows to reduce friction and improve maintainability.

Quick Start

Follow these guidelines to write clean, safe, and maintainable JavaScript for GitHub Actions using github-script.

Frequently Asked Questions about github-script

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

FAQPage Schema
What is the best way to write robust JavaScript for GitHub Actions automation?

Writing robust JavaScript for GitHub Actions requires applying github-script best practices. Consolidating usage guidelines for logging, API calls, and input handling ensures safety and maintainability in CI workflows.

How do I handle errors and logging when using github-script in CI workflows?

Handling errors and logging in github-script involves applying standard patterns with @actions/core and @actions/github. This approach specifies consistent error reporting and logging patterns to drive automation reliably.

How do I manage inputs and API calls within a GitHub Actions JavaScript script?

Managing inputs and API calls within a GitHub Actions JavaScript script follows github-script guidelines for accessing inputs, setting outputs, and performing GitHub API calls. This standardizes automation tasks to reduce friction.

Does github-script work for teams adopting standard CI workflow automation patterns?

github-script works well for teams adopting standard CI workflow automation patterns by establishing reliable logging, error handling, and output configurations. It reduces friction and improves maintainability for collaborative development.