Agent skill · chrisbanes
gradle-run
Use when planning to execute Gradle through `gradle`, `./gradlew`, or a custom `gradlew*` wrapper script, or diagnosing a Gradle build, compact workflow ledger, repeated failure fingerprint, check, test, lint, warning, or failure even when no new Gradle run is appropriate.
What it needs
About 3k tokens when loaded.
What this skill does
Gradle run Core principle Treat complete Gradle output as a temporary, sensitive artifact. Every agent-initiated Gradle command runs through the compact-output wrapper; never stream, tee, paste, or reopen a full build log. Every create, run, and finish invocation is the entire shell command for that tool call. Prefixes, assignments, conditionals, pipes, command chains, and follow-up inspection invalidate lifecycle evidence even when Gradle succeeds. Procedure 1. Classify the request. Reuse a current successful result when unchanged source and inputs already answer the question. A focused task that validates another change is incidental; build/check/warning/failure work is a Gradle-centered workflow. 2. Resolve this skill directory and confirm python3 plus scripts/gradlerun.py. If either is unavailable, stop and report that prerequisite; never run Gradle directly as a fallback. 3. Create one workflow before its first command and retain its opaque ID: Run create, each run, and finish as standalone shell commands. Do not combine one with test, variable setup, git, rg, &&, ;, a pipe, or a newline containing another command. If create fails, retry a fresh standalone create before any run. Use the wrapper exclusively; it supplies --console=plain and --no-scan unless console behavior was selected or the user authorized --scan. Add --warning-mode all only for warning discovery or an explicit request. A workflow is busy result is an ownership violation: wait for the owner or correct ownership; do not start or finish concurrently. 4. For incidental validation, stay in the current agent and run the narrowest task that answers a non-empty verification question: Do not substitute compilation for requested fixture tests. Read only the bounded JSON summary; report both the managed wrapper and nested Gradle task, the question, and its bounded answer. 5. For Gradle-centered work, create one fresh persistent Solver diagnostic owner with read-only repository access. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills chrisbanes/gradle-run