longhorn-build-system

Auto-generates Make targets from scripts/ files using Dapper containers in Longhorn repos.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/COLDTURNIP/longhorn-workspace --skill longhorn-build-system
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: longhorn-build-system
Source: https://github.com/COLDTURNIP/longhorn-workspace/tree/main/.opencode/skills/longhorn-build-system
Command: npx skills add https://github.com/COLDTURNIP/longhorn-workspace --skill longhorn-build-system

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill explains how Longhorn repositories auto-generate Make targets from the scripts/ folder files using Dapper containers.

Core Features & Use Cases

  • Script discovery: detect and map script filenames to Make targets automatically.
  • Deterministic builds: run inside Dapper containers to ensure reproducible results across machines.
  • Usage scenarios: adding new build tasks without editing Makefiles; debugging build issues; validating consistency across repos.

Quick Start

Inspect a repository with a scripts/ directory, then run make to see each script become a Make target executed inside the Dapper container.

Frequently Asked Questions about longhorn-build-system

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

FAQPage Schema
How does Longhorn auto-generate Make targets from scripts?

Longhorn auto-generates Make targets by discovering script filenames in the scripts/ directory and mapping them to Make targets executed inside Dapper containers.

How do I add a new build task to a Longhorn component repo without editing the Makefile?

To add a new build task, place a new script file into the scripts/ directory so Dapper can discover and map it to a Make target without manual Makefile editing.

Why are my Longhorn builds running inside a Dapper container?

Longhorn builds run inside Dapper containers to ensure deterministic, reproducible results across different machines by isolating the execution environment.

Does the Longhorn build system require Dapper for script discovery?

Dapper is required for the Longhorn build system because it executes the auto-generated Make targets, mapping scripts to the .dapper target and default ci behavior.

What is the .dapper target used for in Longhorn Makefiles?

The .dapper target in Longhorn Makefiles handles Dapper container execution, ensuring auto-generated scripts run inside the reproducible build environment.

Can I use Dapper to debug build issues in longhorn-manager and longhorn-engine?

Dapper can debug build issues in longhorn-manager and longhorn-engine by running the auto-generated Make targets inside the container to validate consistency.