Build sh test sh shell script stdlib

Skill kjuhwa/skills-hub/skills/build/build-sh-test-sh-shell-script-stdlib

Each language subdirectory ships build.sh and test.sh with a shared color.sh helper, so CI calls the same scripts that developers run locally.From its SKILL.md

Install

npx -y skills add kjuhwa/skills-hub --skill build-sh-test-sh-shell-script-stdlib

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.7 KB, 292 tokens by cl100k_base, as published. Nobody here has run it

Build Sh Test Sh Shell Script Stdlib

Trigger: Multi-language monorepo where every CI workflow tends to grow ad-hoc inline scripts that drift from local dev commands.

Steps

Create a top-level color.sh exposing info(), warn(), error() with ANSI color (gated on TTY).
Per language subdir, ship build.sh and test.sh that source color.sh.
Use set -euo pipefail; fail loudly on first error.
CI workflows call ./rust/build.sh, ./python/test.sh — never inline complex bash blocks.
Use distinct exit codes (1 = test fail, 2 = build fail) for downstream automation.
Document supported shells and platforms (bash on macOS/Linux/WSL/Git Bash on Windows).

Counter / Caveats

Bash vs sh vs zsh portability bites; explicitly require bash if you use bash-isms.
Color output assumes ANSI; detect TTY and disable for redirected output.
Sourcing across directories needs absolute paths or relative-to-script ($(dirname ${BASH_SOURCE[0]})).
Windows users need WSL or Git Bash; document or provide a PowerShell variant.

Source

Extracted from magika (https://github.com/google/magika.git @ main).

Files of interest:

rust/cli/build.sh
rust/test.sh
rust/color.sh
rust/onnx/build.sh

What ships with it: 1 file

911 B alongside SKILL.md

content.md911 B