giga-workflow

Watch submodule changes and run tests, builds, or lint targets.

6|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/open-hax/opencode-skills --skill giga-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: giga-workflow
Source: https://github.com/open-hax/opencode-skills/tree/main/.opencode/skills/giga-workflow
Command: npx skills add https://github.com/open-hax/opencode-skills --skill giga-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Execute Giga system operations for workspace automation, including watching changes, running submodule tests, and propagating commits.

Core Features & Use Cases

  • Watch orgs/** for changes and automatically run affected tests/builds.
  • Run a specific target (test/build/typecheck/lint) in a submodule.
  • Propagate submodule changes to parent repositories.
  • Generate commit messages using Pantheon.

Quick Start

Use the giga-watch workflow to monitor orgs/**, automatically run affected tests/builds, and propagate submodule changes.

Frequently Asked Questions about giga-workflow

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

FAQPage Schema
How do I automate running tests and builds across git submodules?

Automate submodule tests and builds by watching changes across submodules and coordinating affected target execution. This workspace automation orchestrates end-to-end workflows by monitoring directories and automatically running specific targets like test, build, typecheck, or lint when changes are detected.

What is the best way to propagate submodule changes to parent repositories?

Propagating submodule changes to parent repositories is handled through commit propagation within the workspace automation workflow. It coordinates updating parent repositories with submodule changes and generates commit messages using Pantheon integration to maintain tag-based provenance.

How does watch mode work for multi-repo submodule workflows?

Watch mode for multi-repo submodule workflows monitors directories like orgs/** for file changes. Upon detecting changes, it automatically triggers affected tests, builds, typechecks, or lints in the specific submodule, coordinating end-to-end workspace automation with deterministic behavior and exit codes.

Can I run a specific target like typecheck or lint in a submodule automatically?

Running a specific target like typecheck or lint in a submodule is supported by executing targeted commands within the submodule workflow. The automation watches for changes and coordinates running the specified target, ensuring deterministic behavior and exit codes for multi-repo environments.

Does this workspace automation tool require Pantheon to generate commit messages?

Pantheon integration is used to generate commit messages for submodule changes propagated to parent repositories. The workspace automation leverages Pantheon to create these messages with tag-based provenance, ensuring deterministic commit history across multi-repo workflows.