build-sweep

Detect and fix failing Go builds and tests across multi-module workspaces.

2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/DojoGenesis/gateway --skill build-sweep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-sweep
Source: https://github.com/DojoGenesis/gateway/tree/main/plugins/system-health/skills/build-sweep
Command: npx skills add https://github.com/DojoGenesis/gateway --skill build-sweep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In large multi‑module Go workspaces, build and test failures can accumulate unnoticed, leading to integration issues and broken releases. This Skill continuously scans every module, identifies failures, and applies minimal fixes to keep the entire codebase healthy.

Core Features & Use Cases

  • Detect & Report: Finds all go.mod files, runs go build and go test, and produces a detailed markdown table of statuses.
  • Automated Fixing: Dispatches parallel agents to diagnose failures, apply minimal corrective changes, and verify each fix independently.
  • Commit & Summarize: Commits verified fixes per module and generates a consolidated report, ideal for nightly CI checks or pre‑release validation.

Quick Start

Run the build-sweep skill on your workspace directory to get a verified build and test status report with automatic fixes.

Frequently Asked Questions about build-sweep

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

FAQPage Schema
How do I automate Go workspace build and test health checks?

Automating Go workspace health checks involves sweeping all modules to run go build and go test, producing a markdown status table. It identifies failures and dispatches parallel agents to apply and verify minimal fixes for each module independently.

What is the best way to fix failing Go builds in a multi-module repository?

The best way to fix failing Go builds in a multi-module repository is to dispatch parallel agents that diagnose failures, apply minimal corrective changes, and verify each fix by re-running go build and go test before committing the changes.

Can I use this for nightly CI checks and pre-release validation in Go?

Yes, this approach works for nightly CI checks and pre-release validation. It continuously scans multi-module workspaces, identifies build and test failures, applies verified fixes, and generates a consolidated report to prevent integration issues and broken releases.

How does automated fixing work for failing Go tests?

Automated fixing for failing Go tests dispatches parallel agents to diagnose failures and apply minimal corrective changes. Each fix is verified by re-running build and test commands, ensuring the changes are committed only after successful validation.

What do I need to run a Go workspace build sweep?

Running a Go workspace build sweep requires a multi-module repository with go.mod files. The sweep automatically detects all modules, runs build and test commands, and applies verified fixes without requiring external dependencies.