Token导航 LogoToken导航TokenDH.com
中转站排行榜
开发需要联网github未标认证来源可访问许可证需确认审计通过

android-rxjava-to-coroutines-migration（android rxjava 到协程的迁移）

Agent Skill

用于辅助 Java 项目开发、面向对象设计、Spring 生态、Maven 或 Gradle 依赖和后端工程实践。它适合让 Agent 分析类结构、设计接口、整理服务分层、生成测试或检查常见代码坏味道。使用时需要结合项目已有架构、包结构和依赖版本，不应只按通用教程改代码；涉及数据库、事务、并发或框架配置时，应先确认运行环境和回归测试范围。

总安装

194

周安装

8

GitHub Stars

5

下载量

63
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息，不托管安装包，也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手，先确认命令和权限，再让它执行。

请帮我安装这个 Agent Skill：android-rxjava-to-coroutines-migration（android rxjava 到协程的迁移）
来源仓库：https://github.com/krutikjain/android-agent-skills
仓库路径：skills/android-rxjava-to-coroutines-migration
安装命令：
npx skills add https://github.com/krutikjain/android-agent-skills --skill android-rxjava-to-coroutines-migration
安装前请先检查当前环境是否支持对应 CLI，并向我确认将要执行的命令、安装目录、联网范围和文件读写权限；确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill；本站只展示命令，不托管安装包，也不自动执行。

skills.shnpx skills
npx skills add https://github.com/krutikjain/android-agent-skills --skill android-rxjava-to-coroutines-migration

简介

该技能用于将 Android RxJava 代码迁移至 Kotlin 协程和 Flow 架构。

  • 适用于需要替换 Observable/Single 类型并实现生命周期感知的场景。
  • 提供类型映射矩阵和操作符转换指南，支持 StateFlow 和 SharedFlow 集成。
  • 迁移前应评估代码覆盖率，确保关键路径有回归测试保护。
  • android-rxjava-to-coroutines-migration 属于开发类 Skill，可作为该场景下的辅助能力补充。

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

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明，方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用；具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35.11%
按下载量换算22

Claude

29.12%
按下载量换算18

Cursor

17.67%
按下载量换算11

Gemini CLI

9.18%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API；具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息，不托管安装包，不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源，正式发布前建议补源仓库或其他目录站核验。

来源信息

GitHub 仓库

github.com

/krutikjain/android-agent-skills

SKILL.md 来源

github.com

/krutikjain/android-agent-skills/tree/main/skills/android-rxjava-to-coroutines-migration

skills-sh

skills.sh

/krutikjain/android-agent-skills/android-rxjava-to-coroutines-migration

继续浏览同类 Skills

更多开发 Skills（21,746）返回 Skills 目录

上一个 Skill

android-room-database（Android 房间数据库）

用于辅助数据库表结构、查询语句、迁移脚本和数据维护任务。它适合让 Agent 分析 schema、编写 SQL、排查查询问题、整理索引或生成迁移建议。使用时需要明确数据库类型、连接环境和目标表，区分只读分析与写入变更；涉及删除、更新、迁移和批量导入时，应优先 dry-run、备份或事务保护，避免误操作。

下一个 Skill

android-serialization-offline-sync（android 序列化离线同步）

android-serialization-offline-sync 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。