gradle-dagp

Analyze Gradle dependency advice and plan incremental PR fixes.

1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/premex-ab/claude-marketplace --skill gradle-dagp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gradle-dagp
Source: https://github.com/premex-ab/claude-marketplace/tree/main/plugins/gradle-dagp/skills/gradle-dagp
Command: npx skills add https://github.com/premex-ab/claude-marketplace --skill gradle-dagp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Clean up Gradle module dependency declarations using DAGP guidance without blindly applying advice that could break builds or introduce worse architecture.

Core Features & Use Cases

  • Guided DAGP triage: classifies advice (unused/removal, misused-transitive add, api-like promotion risk, demotions, redundant plugins, Android/module-specific cases) and tells you when to investigate rather than apply.
  • Versioning and baselining: verifies the DAGP plugin is applied and suggests checking for a recent stable version before proceeding, then runs buildHealth (and optionally projectHealth) to generate structured advice.json reports.
  • Batched, reviewable fixes: helps you plan incremental PR batches and verify each batch with targeted compile/test and follow-up health checks, avoiding “mega-PR” changes.
  • When DAGP is wrong: supports diagnostics via :module:reason, explains common false-positive causes (KAPT/KSP, reflection, Android resources, generated sources), and outlines safe upstream reporting with explicit user approval.

Quick Start

Use the gradle-dagp skill to run buildHealth, interpret the resulting advice categories, and propose a safe batched PR plan before applying any dependency changes.

Frequently Asked Questions about gradle-dagp

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

FAQPage Schema
How do I safely fix Gradle dependency declarations using DAGP advice?

To safely fix Gradle dependency declarations using DAGP advice, run the buildHealth task to generate structured advice reports, classify the recommendations by risk, and propose incremental batched PR plans instead of executing a project-wide fixDependencies command.

Why does the dependency-analysis-gradle-plugin recommend removing a dependency that I know is used?

The dependency-analysis-gradle-plugin reports false positives for unused dependencies when code is invoked via KAPT/KSP annotation processors, runtime reflection, Android resources, or generated sources. Run the :module:reason Gradle task to investigate the specific dependency usage before ignoring the advice.

When should I promote a Gradle dependency from implementation to api?

Promote a Gradle dependency from implementation to api only when a module's public interface directly exposes types from that dependency. Treat api-like promotion cases as risky architectural decisions and investigate them via reason tasks to prevent leaking transitive dependencies.

What is the best way to batch Gradle dependency cleanup changes for code review?

The best way to batch Gradle dependency cleanup changes is to group DAGP advice into incremental PR batches. Verify each batch independently with targeted compile and test runs, followed by follow-up buildHealth checks, to avoid overwhelming reviewers with a mega-PR.

Can I use DAGP to fix misused-transitive dependencies in Android projects?

Yes, DAGP supports fixing misused-transitive dependencies in Android projects by identifying undeclared direct dependencies in your build reports. The triage process classifies Android module-specific cases and indicates when to investigate false positives rather than blindly applying the suggested adds.