gradle-run

Run Gradle builds through a wrapper producing bounded JSON diagnostics and managed logs.

1.0k|46|Updated May 12, 2026
One-click install
npx skills add https://github.com/chrisbanes/skills --skill gradle-run
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gradle-run
Source: https://github.com/chrisbanes/skills/tree/main/skills/gradle-run
Command: npx skills add https://github.com/chrisbanes/skills --skill gradle-run

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

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.

Frequently Asked Questions about gradle-run

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

FAQPage Schema
How do I run a Gradle build without flooding the agent context with logs?

Run the build through the gradle_run.py wrapper using create, run, and finish commands. Each run returns a bounded JSON summary with failed tasks, fingerprints, and excerpts, while the full log stays in a wrapper-owned file.

How do I diagnose repeated Gradle build failures?

The wrapper fingerprints warnings and failures and flags repeated primary failure fingerprints across runs. When the same source or compiler fingerprint repeats, stop rebuilding and inspect the cited source line before revising the diagnosis.

Does the Gradle wrapper support custom gradlew scripts?

Yes, any launcher named gradle or starting with gradlew is accepted, including custom wrapper scripts. The wrapper adds --console=plain and --no-scan defaults unless you explicitly choose console behavior or authorize --scan.

Are credentials safe in Gradle build output?

Summaries and ledgers redact authorization headers, passwords, tokens, and URL-embedded credentials before anything reaches model-visible context. Full logs are still treated as sensitive and are never streamed or reopened.

What happens when a Gradle run is interrupted?

On SIGINT or SIGTERM the wrapper terminates the entire Gradle process group, records the interrupted run with its signal in the ledger, and preserves partial diagnostics gathered before interruption.