Menu
Checkpoint workflow for mobile development safety. Save/restore Android project state at critical points.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Core Android development patterns for Kotlin, including coroutines, lifecycle management, and functional programming idioms.
Apple Combine framework for reactive programming. Publishers, subscribers, operators, and error handling.
Pattern extraction and skill generation for mobile development sessions. Automatically learns from your coding patterns.
Instinct-based learning system with confidence scoring for mobile patterns. Automatically extracts and evolves patterns.
Core Data for iOS persistence. Data models, fetch requests, background contexts, and SwiftData migration.
Kotlin Coroutines and Flow patterns for structured concurrency, error handling, and async operations.
| name | mobile-checkpoint |
| description | Checkpoint workflow for mobile development safety. Save/restore Android project state at critical points. |
Comprehensive checkpoint workflow for Android development safety and state recovery.
Before risky operations:
./gradlew wrapper, dependency upgrades)After milestones:
# Verify clean state
git status
./gradlew check
# Create checkpoint
/mobile-checkpoint save before-<operation>
# Make your changes
# ... edits, refactors, updates ...
# Verify build
./gradlew build
# If successful - create new checkpoint
/mobile-checkpoint save after-<operation>
# If failed - restore
/mobile-checkpoint restore before-<operation>
| Level | Content | Use Case |
|---|---|---|
| Quick | Git status, branch, recent files | Quick experiments |
| Standard | + Build config, tests | Default for most ops |
| Full | + Dependencies, manifest, instincts | Major refactors, releases |
/mobile-checkpoint restore <name>
# Agent will:
# 1. Show git diff to current state
# 2. Offer git reset --hard <commit>
# 3. Restore staged/unstaged changes
# Checkpoint includes:
# - build.gradle.kts files
# - gradle/wrapper/gradle-wrapper.properties
# - version catalog (libs.versions.toml)
# Agent provides diff for manual restoration
# Checkpoint shows:
# - Previous test results
# - Failing tests (if any)
# - Coverage metrics
# Run tests to verify state:
./gradlew test
The checkpoint system integrates with hooks:
// hooks/checkpoint-hooks.json
{
"trigger": "PreToolUse",
"matcher": "tool == \"Bash\" && command contains \"gradle\"",
"action": "Create quick checkpoint"
}
{
"trigger": "PostToolUse",
"matcher": "tool == \"Edit\" && file == \"AndroidManifest.xml\"",
"action": "Create standard checkpoint"
}
Use descriptive names with operation and context:
| Name Pattern | Example |
|---|---|
before-{operation} | before-mvi-migration |
after-{operation} | after-koin-refactor |
{feature}-complete | auth-flow-complete |
{version}-rc | v1.2.0-rc1 |
working-{date} | working-2026-02-03 |
Avoid: checkpoint1, save, temp
/mobile-checkpoint list
# Output:
# before-mvi-refactor 2 hours ago Standard
# auth-feature-done 1 day ago Full
# working-0203 2 days ago Quick
# Keep last 10
/mobile-checkpoint prune --keep 10
# Delete specific
/mobile-checkpoint delete working-0203
# Export to file
/mobile-checkpoint export release-ready > ~/backups/mobile-checkpoint.json
# Import from file
/mobile-checkpoint import ~/backups/mobile-checkpoint.json
Checkpoints preserve instinct learning:
{
"instincts": {
"version": "2.0",
"count": 47,
"highConfidence": 23,
"lastUpdated": "2026-02-03T10:30:00Z"
}
}
Restoring a checkpoint also restores your learned patterns.
git status/mobile-checkpoint verify <name>./gradlew --refresh-dependenciesRemember: A checkpoint is a safety net, not a time machine. It shows you what changed, not how to undo every change.