sync-versions

Compare Kotlin Multiplatform project dependency versions against a source of truth.

1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/oscardlfr/AndroidCommonDoc --skill sync-versions-oscardlfr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-versions
Source: https://github.com/oscardlfr/AndroidCommonDoc/tree/main/skills/sync-versions
Command: npx skills add https://github.com/oscardlfr/AndroidCommonDoc --skill sync-versions-oscardlfr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps maintain consistency in version catalogs across Kotlin Multiplatform projects, ensuring that dependencies match the source of truth.

Core Features & Use Cases

  • Version Catalog Alignment: Checks that project dependencies match the canonical versions defined in a source of truth.
  • Project Comparison: Compares version entries across multiple projects against the source of truth.
  • Remediation Suggestions: Provides suggestions for updating project versions or source of truth as needed.
  • Use Case: When you need to verify that all your KMP projects are using the correct versions of dependencies, such as libraries or frameworks.

Quick Start

Run the sync-versions skill with the source of truth and project paths: /sync-versions --source ../your-shared-libs --projects ../MyProject,../MyApp

Frequently Asked Questions about sync-versions

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

FAQPage Schema
How do I ensure version consistency across Kotlin Multiplatform projects?

Version consistency across Kotlin Multiplatform projects is maintained by comparing project dependency versions against a defined source of truth and generating remediation suggestions for misaligned entries.

What is the best way to align dependency versions with a source of truth in KMP?

Aligning dependency versions in KMP involves running a script that compares version catalogs from multiple projects against a canonical source, identifying discrepancies, and suggesting updates to either the projects or the source of truth.

How do I compare dependency versions across multiple projects against a shared library?

Comparing dependency versions across projects requires passing the source of truth path and project paths to a script, which then cross-references the version catalogs and outputs a report of mismatched dependencies.

Do I need Bash or PowerShell to run version catalog alignment checks for KMP?

Yes, Bash or PowerShell is required to execute the version catalog alignment checks, as the skill relies on scripts to perform the comparison logic between the Kotlin Multiplatform projects and the source of truth.

What should I do if my KMP project dependencies do not match the source of truth?

If KMP project dependencies do not match the source of truth, the skill provides specific remediation suggestions, indicating whether to update the project versions or adjust the canonical source of truth.

Are there limitations to using scripts for dependency version control in KMP?

Limitations include the necessity of a Bash or PowerShell execution environment and the requirement to explicitly define both the source of truth and all target project paths for accurate version comparison.