krutikjain/android-agent-skills55 installs
android-rxjava-to-coroutines-migration
Migrate Android RxJava code to Kotlin coroutines and Flow with safe lifecycle-aware replacements.
How do I install this agent skill?
npx skills add https://github.com/krutikjain/android-agent-skills --skill android-rxjava-to-coroutines-migrationIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill provides safe tools and patterns for migrating Android RxJava code to Kotlin Coroutines. It includes static analysis scripts to inventory legacy RxJava usage and references official documentation from Google and Kotlin.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
- ZeroLeakspass
Score: 93/100 · 2 sections analyzed
What does this agent skill do?
Android RxJava To Coroutines Migration
When To Use
- Use this skill when the request is about: rxjava to coroutines android, observable to flow android, replace composite disposable android.
- Primary outcome: Migrate Android RxJava code to Kotlin coroutines and Flow with safe lifecycle-aware replacements.
- Reach for this skill when the codebase still exposes
Single,Observable, schedulers, or disposables and the goal is to move tosuspend,Flow,StateFlow, orSharedFlow. - Read
references/patterns.mdfor the type-mapping matrix and operator red-flag checklist. - Read
references/scenarios.mdfor staged migration and inventory-first workflows. - Handoff skills when the scope expands:
android-modernization-upgradeandroid-coroutines-flow
Workflow
- Scan the codebase for RxJava imports, base types, subjects, and scheduler usage before changing any API surface.
- Classify each usage as one-shot work, stream work, hot state, hot events, callback bridging, or backpressure-sensitive work.
- Replace repository and domain APIs first, then move UI-layer subscriptions to lifecycle-aware collection.
- Rewrite scheduler and disposable management as dispatcher, scope, structured-concurrency ownership, and lifecycle-aware collection such as
repeatOnLifecycle. - Leave a checklist for ambiguous operators or custom bridges instead of pretending every chain can be auto-converted safely.
Guardrails
- Prefer
suspendfunctions for one-shot work andFlowfor streams; do not force everything intoFlow. - Preserve lifecycle ownership when replacing
CompositeDisposableand manual subscription chains. - Call out operator semantics that need human review, especially
flatMap,switchMap, replay, and threading assumptions. - Preserve hot-state and replay semantics explicitly with
StateFlow,SharedFlow,shareIn, orstateIninstead of assuming coldFlowis equivalent. - Treat migration as behavior-preserving refactor work, not a chance to redesign unrelated business logic.
Anti-Patterns
- Converting every Rx type to
Floweven when asuspendfunction is the better match. - Dropping replay, buffering, or hot-stream semantics during subject migration.
- Leaving
observeOnandsubscribeOnassumptions undocumented after moving to dispatchers. - Rewriting repository, ViewModel, and UI layers all at once with no staged verification.
Review Focus
- Type mapping:
Single,Maybe,Completable,Observable,Flowable, and Subjects. - Hot vs cold semantics, replay behavior, and backpressure expectations.
- Dispatcher ownership,
viewModelScope, and lifecycle collection. - Testing fallout for coroutine timing, cancellation, and stream assertions.
Examples
Happy path
- Scenario: Scan a legacy RxJava sample and generate a migration checklist for repositories, ViewModels, and UI subscriptions.
- Command:
bash skills/android-rxjava-to-coroutines-migration/scripts/run_examples.sh
Edge case
- Scenario: Inventory subjects, disposables, and scheduler usage before converting state or one-off events.
- Command:
python3 skills/android-rxjava-to-coroutines-migration/scripts/scan_rxjava_usage.py examples/fixtures/rxjava-legacy-sample --json
Failure recovery
- Scenario: Produce a deterministic checklist when parts of the chain still need manual operator review.
- Command:
python3 skills/android-rxjava-to-coroutines-migration/scripts/generate_migration_checklist.py examples/fixtures/rxjava-legacy-sample
Done Checklist
- RxJava types and operators were inventoried before code changes were proposed.
- One-shot APIs, streams, hot state, and hot events are mapped to the right coroutine primitives.
- Lifecycle ownership and dispatcher assumptions are explicit.
- Ambiguous operators or bridging cases are recorded as manual follow-up work.
Official References
- https://developer.android.com/kotlin/coroutines
- https://developer.android.com/kotlin/flow
- https://developer.android.com/kotlin/coroutines/coroutines-best-practices
- https://developer.android.com/topic/libraries/architecture/coroutines
- https://developer.android.com/kotlin/flow/stateflow-and-sharedflow
- https://kotlinlang.org/docs/flow.html
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/krutikjain/android-agent-skills/android-rxjava-to-coroutines-migration">View android-rxjava-to-coroutines-migration on skillZs</a>