mobile-checkpoint

Checkpoint your Android project by running a save command with a descriptive label before making risky edits. The checkpoint captures Git state, build configs, dependencies, and test results, letting you restore the exact state if something breaks during Gradle updates, manifest changes, or architecture migrations.

Yes. After a failed build or test, restore from a previous checkpoint to recover your Git state, build configs, dependencies, and test results. The skill provides restoration commands and diffs so you can see exactly what changed and quickly return to a working state.

A checkpoint captures Git state, Gradle build configs, dependency versions, and test results. This allows you to safely test architecture migrations, dependency updates, and manifest changes on Android and Kotlin Multiplatform projects, then restore everything if needed.

Export checkpoint milestones to create backups or share snapshots of your project state. The skill provides export and import capabilities so you can preserve key states across Android and Kotlin Multiplatform workflows and restore them later.

Yes. Checkpoints rely on Git to capture and restore project state, so your mobile project must be under Git version control. This is the foundation for tracking changes before and after risky operations like Gradle or architecture updates.