run-script

Create and manage Bash task runner scripts with auto-discovered tasks.

6|1|Updated Dec 29, 2025
One-click install
npx skills add https://github.com/mgajewskik/opencode-config --skill run-script-mgajewskik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-script
Source: https://github.com/mgajewskik/opencode-config/tree/main/skills/run-script
Command: npx skills add https://github.com/mgajewskik/opencode-config --skill run-script-mgajewskik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and manage bash task runner scripts (Makefile alternative) to standardize and simplify project automation by turning ad-hoc commands into reusable tasks.

Core Features & Use Cases

  • Auto-discovery of tasks defined as Bash functions, enabling easy invocation from a single entry point.
  • Provides a template run script that lives at the repository root and is marked executable.
  • Supports optional helper directories (scripts/, references/, assets/) to extend capabilities as needed.

Quick Start

Create a file named run at the repository root, make it executable, and write your tasks as functions to be invoked by the run script.

Frequently Asked Questions about run-script

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

FAQPage Schema
How do I create a lightweight bash task runner as a Makefile alternative?

A bash task runner standardizes project automation by turning ad-hoc commands into reusable tasks. You create an executable script named run at the repository root and define tasks as Bash functions for auto-discovery and invocation.

What is auto-discovery for shell scripts and how does it work for task runners?

Auto-discovery for shell scripts identifies tasks defined as Bash functions within your run script. It allows developers to invoke any defined function automatically from a single entry point without manual registration or configuration.

Do I need any dependencies to set up a self-contained bash task runner?

No dependencies are required to set up a self-contained bash task runner. You only need a single executable script named run at the repository root, with optional scripts, references, and assets directories to extend behavior as needed.

What's the best way to organize routine automation scripts for a development project?

The best way to organize routine automation scripts is using a root-level run script for task functions, supplemented by optional scripts, references, and assets directories. This structure handles building, testing, and deploying through auto-discovered shell functions.

Can I use a bash task runner for deployment and testing automation without Make?

Yes, you can use a bash task runner for deployment and testing automation without Make. By defining your build, test, and deploy routines as shell functions in a root run script, you achieve lightweight project automation as a Makefile alternative.

When should I not use a shell function task runner for project automation?

You should not use a shell function task runner if your project requires complex dependency graphs or cross-platform compatibility beyond standard Bash. This approach is designed for lightweight, self-contained automation within a single repository root.