dev-learning-record

Generates structured learning records from Kotlin and Android code changes.

2|Updated May 12, 2026

Search Tags:#code review #kotlin #ui development #knowledge extraction #learning record #android architecture #room db

Ready to run

npx skills add https://github.com/youfengknight/Android-Code-Skills --skill dev-learning-record

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-learning-record
Source: https://github.com/youfengknight/Android-Code-Skills/tree/main/dev-learning-record
Command: npx skills add https://github.com/youfengknight/Android-Code-Skills --skill dev-learning-record

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of forgetting what you learned after adding features or refactoring Android/Kotlin code, and it turns those changes into reusable, structured knowledge.

Core Features & Use Cases

Knowledge extraction across layers: analyzes Kotlin syntax, Android architecture (e.g., MVVM, StateFlow), UI development (e.g., ViewBinding, RecyclerView), Room database usage (Entity/DAO/Flow, migrations), and networking concepts (e.g., OkHttp, interceptors, coroutines).
Structured learning record generation: produces a consistent document format that summarizes “what changed,” the related concepts, and practical suggestions.
Repeatable for multiple scenarios: supports code learning, implementation wrap-ups, and post-review retrospectives after modifications or reviews.

Quick Start

Ask the AI to generate a learning record for your latest feature by describing what you changed and the involved Kotlin/Android/DB/UI/network parts.

Frequently Asked Questions about dev-learning-record

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate structured learning records from Kotlin and Android code changes?▼

To generate structured learning records from Kotlin and Android code changes, describe your feature modifications across syntax, architecture, UI, Room, and networking to produce a consistent document with learning points, rationale, and practical recommendations.

What is the best way to document Android architecture concepts after a code review?▼

The best way to document Android architecture concepts after a code review is to perform a retrospective analysis of the modified code, extracting knowledge points about MVVM, StateFlow, and other detected implementation aspects into a structured summary.

Can I extract knowledge from Room database migrations and ViewBinding implementations?▼

Yes, you can extract knowledge from Room database migrations and ViewBinding implementations by analyzing these specific code segments to detect involved concepts and generate targeted summaries with practical suggestions.

Does this approach work for summarizing OkHttp interceptors and coroutine networking concepts?▼

Yes, this approach works for summarizing OkHttp interceptors and coroutine networking concepts by analyzing your networking code changes and producing structured documentation aligned to the detected implementation aspects.

How do I create a post-review retrospective for Android UI development modifications?▼

To create a post-review retrospective for Android UI development modifications, analyze the changed ViewBinding and RecyclerView code to generate a structured learning record summarizing what changed, related concepts, and practical suggestions.

What should I do if my generated learning record omits specific Kotlin syntax concepts?▼

If your generated learning record omits specific Kotlin syntax concepts, provide a more detailed description of your code changes explicitly mentioning the syntax elements to ensure the analysis detects all relevant implementation aspects.