gradle-dependency-checker

Executes Gradle dependency check commands, retrieves and analyzes dependency trees, and extracts version information for key dependencies such as kotlin/kotlinx/skiko/androidx. Use when users need to check Gradle project dependency versions or analyze dependency relationships.

16 stars

Best use case

gradle-dependency-checker is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Executes Gradle dependency check commands, retrieves and analyzes dependency trees, and extracts version information for key dependencies such as kotlin/kotlinx/skiko/androidx. Use when users need to check Gradle project dependency versions or analyze dependency relationships.

Teams using gradle-dependency-checker should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/gradle-dependency-checker/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/development/gradle-dependency-checker/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/gradle-dependency-checker/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How gradle-dependency-checker Compares

Feature / Agentgradle-dependency-checkerStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Executes Gradle dependency check commands, retrieves and analyzes dependency trees, and extracts version information for key dependencies such as kotlin/kotlinx/skiko/androidx. Use when users need to check Gradle project dependency versions or analyze dependency relationships.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Gradle Dependency Checker

**Path Note**: This document uses `{SKILL_ROOT}` as a placeholder for the skill root directory. The AI assistant should dynamically determine the absolute path of the skill root directory based on the currently open file path when executing commands. For example, if the current workspace path is `/Users/username/.cursor/skills/gradle-dependency-checker`, then `{SKILL_ROOT}` should be replaced with that path.

## Overview

This skill is used to execute Gradle dependency check commands, retrieve project dependency trees, and extract version information for key dependencies, specifically:

- `kotlin` - Kotlin standard library version
- `kotlinx.*` - Kotlin extension libraries (e.g., kotlinx-coroutines, kotlinx-serialization, etc.)
- `skiko` - Skia binding library version
- `androidx.*` - AndroidX library versions

## Usage

### View Dependency Reports

First check if the report file `{SKILL_ROOT}/references/compose-multiplatform-dependencies-{VERSION}.md` exists. If the report file does not exist, you need to execute the script to generate the dependency tree first.

### One-Click Script (Recommended)

**It is recommended to use the one-click script**, which automatically completes both steps of dependency tree generation and report generation:

```bash
# Process a single version
{SKILL_ROOT}/scripts/compose-multiplatform-check-and-parse.sh 1.10.0

# Process multiple versions (executed sequentially)
{SKILL_ROOT}/scripts/compose-multiplatform-check-and-parse.sh 1.9.3 1.10.0 1.8.2
```

**Script Description**:

- Script path: `{SKILL_ROOT}/scripts/compose-multiplatform-check-and-parse.sh`
- Supports single or multiple version number parameters
- Automatically completes two steps:
  1. Generate dependency tree (if it doesn't exist or is empty)
  2. Generate Markdown report
- Output files:
  - Dependency tree: `{SKILL_ROOT}/assets/dependency-checker/compose-multiplatform-checker/results/compose-multiplatform-dependencies-{VERSION}.txt`
  - Report: `{SKILL_ROOT}/references/compose-multiplatform-dependencies-{VERSION}.md`
- If the dependency tree file already exists and is not empty, the generation step will be skipped
- Multiple versions are processed sequentially, waiting for each version to complete before executing the next

## Workflow

**Important Note**: The AI assistant **must NOT** directly execute scripts or generate dependency tree/report files. All scripts must be manually executed by the user.

### Step 1: Check Report File

1. **Check report file**: First check if `{SKILL_ROOT}/references/compose-multiplatform-dependencies-{VERSION}.md` exists (the AI needs to dynamically determine the absolute path of `{SKILL_ROOT}` based on the current workspace path)
2. **If the report file exists**: Directly read and display the report content
3. **If the report file does not exist**: **Prompt the user** to execute the following command to generate the dependency tree and report (the AI must not directly execute, but needs to replace `{SKILL_ROOT}` with the actual absolute path)

### Step 2: Generate Dependency Tree and Report (if needed)

**Recommended method (one-click)**: The AI should prompt the user to execute the one-click script (need to replace `{SKILL_ROOT}` with the actual absolute path):

```bash
{SKILL_ROOT}/scripts/compose-multiplatform-check-and-parse.sh {VERSION}
```

One-click script description:

- Automatically completes both steps of dependency tree generation and report generation
- If the dependency tree file already exists and is not empty, the generation step will be skipped
- Supports passing multiple versions, the script will process them sequentially, waiting for completion before executing the next

## Output Format

Analysis results must strictly follow the following format (generated using the `{SKILL_ROOT}/scripts/compose-multiplatform-parse-dependencies.py` script):

```markdown
# Compose Multiplatform 1.10.0 Dependencies

## Kotlin

- `org.jetbrains.kotlin:kotlin-stdlib`: **2.2.20**

## Kotlinx

- `org.jetbrains.kotlinx:atomicfu`: **0.27.0**
- `org.jetbrains.kotlinx:kotlinx-coroutines-core`: **1.9.0**
- `org.jetbrains.kotlinx:kotlinx-serialization-core`: **1.7.3**

## Skiko

- `org.jetbrains.skiko:skiko`: **0.9.37.3**

## Compose Multiplatform

- `org.jetbrains.compose.animation:animation`: **1.10.0**
- `org.jetbrains.compose.foundation:foundation`: **1.10.0**
- `org.jetbrains.compose.runtime:runtime`: **1.10.0**
- `org.jetbrains.compose.ui:ui`: **1.10.0**

## JetBrains AndroidX Lifecycle

- `org.jetbrains.androidx.lifecycle:lifecycle-common`: **2.9.6**
- `org.jetbrains.androidx.lifecycle:lifecycle-runtime-compose`: **2.9.6**

## JetBrains AndroidX SavedState

- `org.jetbrains.androidx.savedstate:savedstate`: **1.3.6**

## AndroidX

- `androidx.compose.runtime:runtime`: **1.10.0**
- `androidx.collection:collection`: **1.5.0**
- `androidx.annotation:annotation`: **1.9.1**
- `androidx.lifecycle:lifecycle-common`: **2.9.4**
```

### Output Format Description

- Title format: `# Compose Multiplatform {VERSION} Dependencies`
- Dependency format: Use backticks to wrap the complete dependency coordinate, version number in bold
- Version information: Display the final resolved version (in bold), automatically handle version upgrade markers `->`
- Categorization: Organize by Kotlin, Kotlinx, Skiko, Compose Multiplatform, JetBrains AndroidX Lifecycle, JetBrains AndroidX SavedState, AndroidX
- Empty lines before and after titles and lists (compliant with MD022 and MD032 standards)
- Empty value handling: If a category has no dependencies, that category can be omitted

## Important Notes

- **AI assistant must NOT directly execute scripts or generate files**: All dependency tree and report generation must be completed by the user manually executing scripts
- **Path handling**: When the AI assistant executes commands or checks files, it needs to dynamically determine the absolute path of `{SKILL_ROOT}` based on the current workspace path and replace it in all paths and commands
- **Recommended to use one-click script**: `{SKILL_ROOT}/scripts/compose-multiplatform-check-and-parse.sh` will automatically complete dependency tree generation and report generation
- Only get dependencies from the `commonMainResolvableDependenciesMetadata` configuration
- Output files are saved at `{SKILL_ROOT}/assets/dependency-checker/compose-multiplatform-checker/results/compose-multiplatform-dependencies-{VERSION}.txt`
- Dependency reports are saved at `{SKILL_ROOT}/references/compose-multiplatform-dependencies-{VERSION}.md`
- **If the output file is empty, the script will automatically re-execute the Gradle command**
- Multiple versions are processed sequentially, cannot be executed in parallel
- Dependency tree output has been filtered to remove build information, only contains dependency tree content
- Dependencies managed by BOM need to identify the actually resolved version
- Output format must strictly follow the specifications in the "Output Format" section
- Use the `{SKILL_ROOT}/scripts/compose-multiplatform-parse-dependencies.py` script to parse the dependency tree and generate Markdown reports

Related Skills

dependency-upgrade

16
from diegosouzapw/awesome-omni-skill

Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing brea...

async-await-checker

16
from diegosouzapw/awesome-omni-skill

Automatically applies when writing Python functions that call async operations. Ensures proper async/await pattern usage (not asyncio.run) to prevent event loop errors.

android-gradle

16
from diegosouzapw/awesome-omni-skill

Automate Gradle tasks for Android projects - build, test, coverage, clean. Use when building APKs, running unit tests, generating coverage reports, or checking dependencies.

asyncredux-dependency-injection

16
from diegosouzapw/awesome-omni-skill

Inject dependencies into actions using the environment pattern. Covers creating an Environment class, passing it to the Store, accessing `env` from actions, and using dependency injection for testability.

accessibility-design-checker

16
from diegosouzapw/awesome-omni-skill

Ensures designs meet accessibility requirements including WCAG compliance, color contrast, keyboard navigation, screen reader support, and focus management. Reviews designs for accessibility issues and provides recommendations.

composer-dependency-management

16
from diegosouzapw/awesome-omni-skill

Rules pertaining to Composer dependency management, promoting best practices for declaring and updating dependencies.

analyze-copper-stock-resilience-dependency

16
from diegosouzapw/awesome-omni-skill

用跨資產訊號(全球股市韌性 + 中國利率環境)評估銅價能否突破關卡或進入「回補/回踩」到支撐的機率與路徑。

ai-content-quality-checker

16
from diegosouzapw/awesome-omni-skill

AI生成コンテンツの総合品質チェックスキル。読みやすさ、正確性、関連性、独自性、SEO、アクセシビリティ、エンゲージメント、文法・スタイルを多角的に評価。

api-contract-checker

16
from diegosouzapw/awesome-omni-skill

Validate API changes against an expected contract. Use when a mid-level developer needs to detect breaking changes.

agentic-jumpstart-dependency-management

16
from diegosouzapw/awesome-omni-skill

Dependency management guidelines for Jarvy - crate selection criteria, feature flag best practices, version management, security auditing with cargo-audit and cargo-deny.

bgo

10
from diegosouzapw/awesome-omni-skill

Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.

Coding & Development

nextjs-shadcn-builder

16
from diegosouzapw/awesome-omni-skill

Build new Next.js applications or migrate existing frontends (React, Vue, Angular, vanilla JS, etc.) to Next.js + shadcn/ui with systematic analysis and conversion. Enforces shadcn design principles - CSS variables for theming, standard UI components, no hardcoded values, consistent typography/colors. Use for creating Next.js apps, migrating frontends, adopting shadcn/ui, or standardizing component libraries. Includes MCP integration for shadcn documentation and automated codebase analysis.