What problem does it solve?
Gradle builds produce massive, noisy logs that flood an agent's context, leak credentials, and make repeated failures hard to track. This Skill wraps every Gradle invocation in a managed workflow that returns compact, redacted JSON summaries instead of raw build output.
Core Features & Use Cases
- Bounded diagnostics: Every run returns a JSON summary capped in size with failed tasks, warning and failure fingerprints, and short excerpts, while full logs stay in wrapper-owned files.
- Workflow lifecycle management: Create, run, and finish commands track a durable ledger of runs, detect repeated commands and repeated failure fingerprints, and clean up logs on finish.
- Credential redaction and safe interruption: Summaries and ledgers redact tokens, passwords, and authorization headers, and SIGINT/SIGTERM handling terminates the whole Gradle process group while preserving partial diagnostics.
- Use Case: While fixing a Kotlin compilation error, an agent runs
./gradlew :module:compileKotlin through the wrapper, receives a fingerprinted failure summary, and stops rebuilding when the same source fingerprint repeats.
Quick Start
Ask the agent to run your Gradle build or test task through the gradle-run wrapper and report the bounded diagnostic summary for each run.