Envy-7z

mobile-update-advisor

Mobile dependency and platform update advisor for Android and Flutter projects. Use when mapping project structure, evaluating SDK/dependency updates, prioritizing technical debt, identifying architecture hotspots, or creating a safe improvement roadmap.

Envy-7z 0 Updated 3mo ago

Resources

3
GitHub

Install

npx skillscat add envy-7z/mobile-agent-skillpack/mobile-update-advisor

Install via the SkillsCat registry.

SKILL.md

Mobile Update Advisor

Overview

Map the current mobile project, identify high-impact updates, and produce a prioritized improvement roadmap with risk-aware decisions.

Workflow

  1. Map project structure
  • Run scripts/mobile_project_snapshot.sh <repo_root> first.
  • Identify Android modules, Flutter packages/apps, CI files, and release/config files.
  1. Build dependency and platform snapshot
  • Capture Android build stack indicators (gradle-wrapper, AGP/Kotlin markers, SDK levels).
  • Capture Flutter/Dart indicators (environment, package dependencies, major plugins).
  • Keep findings evidence-based; quote exact file paths and lines when possible.
  1. Evaluate updates and improvements
  • Use references/update-decision-rubric.md to classify each candidate as update-now, schedule, or defer.
  • Prioritize security fixes, build-break risks, and deprecations first.
  • Balance impact, migration effort, and regression risk.
  1. Propose architecture/code quality improvements
  • Highlight duplication, oversized files, unstable boundaries, and weak test coverage.
  • Prefer incremental refactors with measurable outcomes.
  • Suggest compact code changes only when they reduce complexity or defect risk.
  1. Publish decision report
  • Return a ranked backlog with rationale, effort estimate, and risk score.
  • Separate mandatory updates from optional optimizations.

Output Format

Use this exact section structure in the final response:

# Mobile Update + Improvement Report

## Project Map
- Android modules:
- Flutter modules:
- CI/release files:

## Must-Do Updates
1. [item] - reason - risk if delayed

## Scheduled Updates
1. [item] - target window - migration notes

## Architecture/Code Improvements
1. [improvement] - expected gain - implementation scope

## Ranked Next Actions
1. ...
2. ...
3. ...

Guardrails

  • Preserve existing architecture unless the user asks for larger redesign.
  • Avoid speculative upgrades without explicit compatibility evidence.
  • Keep recommendations actionable and repository-specific.

References

  • Use references/update-decision-rubric.md to score update urgency and risk.