be-build

Diagnoses and fixes Gradle build failures with up to three automated retry attempts.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/ohmyhotelco/hare-cc-plugins --skill be-build-ohmyhotelco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: be-build
Source: https://github.com/ohmyhotelco/hare-cc-plugins/tree/main/backend-webflux-plugin/skills/be-build
Command: npx skills add https://github.com/ohmyhotelco/hare-cc-plugins --skill be-build-ohmyhotelco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Build failures in Spring WebFlux projects require manual diagnosis of compilation errors, test failures, checkstyle violations, dependency issues, and configuration problems, which interrupts development flow and consumes debugging time. ## Core Features & Use Cases - Automated Build Diagnosis: Runs the project build and classifies failures into five categories (compilation, test, checkstyle, dependency, configuration) with targeted fix strategies per category. - Retry with Revert Safety: Applies fixes across up to 3 attempts, reverting changes that make no progress so each retry starts from a clean state. - Pipeline State Awareness: Demotes feature progress records whose code was modified by build fixes, forcing re-verification before commit. - Use Case: A Gradle build fails with a 'cannot find symbol' compilation error after refactoring; the skill locates the missing factory method, adds it, and reports the exact file changed with test counts from the passing rerun. ## Quick Start Ask the assistant to run the build and automatically fix any compile errors or test failures that come up.

Frequently Asked Questions about be-build

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

FAQPage Schema
How do I automatically fix Gradle build failures?▼

Invoke the build command and a build-doctor agent runs the Gradle build, diagnoses the failure category, applies a targeted fix, and retries up to 3 times. It reports the exit code, error evidence, and every file changed during the attempts.

What types of build errors can be auto-fixed?▼

Five categories are handled: compilation errors, test failures, checkstyle violations, dependency problems, and configuration issues. Each category has its own indicators and fix strategy applied by the build-doctor agent.

Does auto-fix modify or skip failing tests?▼

No. The skill never modifies test expectations unless the implementation is clearly correct, never skips or disables failing tests, and never comments out problematic code or adds @SuppressWarnings to silence issues.

What happens if the build still fails after retries?▼

After 3 failed attempts, you get a report with the last exit code, actual error output, the diagnosed category and root cause, which changes were kept versus reverted, and a concrete suggestion for the manual fix.

Why does a fix get reverted during build retries?▼

A progress check evaluates each attempt; if a fix does not move the build forward, it is reverted so the next attempt starts from a clean state. Reverted changes are listed in the final failure report.