agentleFS
Sign inStart free
krutikJainkrutikJain/android-agent-skills/.github/skills/android-rxjava-to-coroutines-migration/SKILL.md

android-rxjava-to-coroutines-migration

Skill14 starsChanged 8 months agoMITView on GitHub

Migrate Android RxJava code to Kotlin coroutines and Flow with safe lifecycle-aware replacements.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the request is about: rxjava to coroutines android, observable to flow android, replace composite disposable android.

    line 17
  2. Very specific:

    Read references/patterns.md for the type-mapping matrix and operator red-flag checklist.

    line 20
  3. Very specific:

    Read references/scenarios.md for staged migration and inventory-first workflows.

    line 21
  4. Distinctive:

    Leave a checklist for ambiguous operators or custom bridges instead of pretending every chain can be auto-converted safely.

    line 31
  5. Very specific:

    Prefer suspend functions for one-shot work and Flow for streams.

    line 34
  6. Very specific:

    Call out operator semantics that need human review, especially flatMap, switchMap, replay, and threading assumptions.

    line 36
  7. Distinctive:

    Treat migration as behavior-preserving refactor work, not a chance to redesign unrelated business logic.

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 to suspend, Flow, StateFlow, or SharedFlow.
  • Read references/patterns.md for the type-mapping matrix and operator red-flag checklist.
  • Read references/scenarios.md for staged migration and inventory-first workflows.
  • Handoff skills when the scope expands:
  • android-modernization-upgrade
  • android-coroutines-flow

Workflow

  1. Scan the codebase for RxJava imports, base types, subjects, and scheduler usage before changing any API surface.
  2. Classify each usage as one-shot work, stream work, hot state, hot events, callback bridging, or backpressure-sensitive work.
  3. Replace repository and domain APIs first, then move UI-layer subscriptions to lifecycle-aware collection.
  4. Rewrite scheduler and disposable management as dispatcher, scope, structured-concurrency ownership, and lifecycle-aware collection such as repeatOnLifecycle.
  5. Leave a checklist for ambiguous operators or custom bridges instead of pretending every chain can be auto-converted safely.

Guardrails

  • Prefer suspend functions for one-shot work and Flow for streams; do not force everything into Flow.
  • Preserve lifecycle ownership when replacing CompositeDisposable and 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, or stateIn instead of assuming cold Flow is equivalent.
  • Treat migration as behavior-preserving refactor work, not a chance to redesign unrelated business logic.

Anti-Patterns

  • Converting every Rx type to Flow even when a suspend function is the better match.
  • Dropping replay, buffering, or hot-stream semantics during subject migration.
  • Leaving observeOn and subscribeOn assumptions 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free