Room Migration Audit
Testing & Qualityroom-migration-auditRoom Migration Audit is an Agent Skill for testing & quality published in the oxyroid/M3UAndroid repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Audit M3UAndroid Room schema and migration changes for versioning, schema artifacts, data preservation, indices, defaults, DAO compatibility, and migration validation.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/oxyroid/M3UAndroid/blob/HEAD/.claude/skills/room-migration-audit/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/room-migration-audit, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Room Migration Audit
Audit Room database changes for complete migration and data-preservation evidence.
When To Use
Use when a task changes or reviews:
- Room entities, DAOs, database versions, migrations, or schema JSON
- Persistence models or query behavior that changes stored data semantics
Required Context
Read first:
AGENTS.mddata/AGENTS.mddocs/ai/playbooks/room-migration.md- Relevant entity, DAO, database, migration, schema, and test files
Audit Checks
Verify with file evidence:
- Database version, migration code, and schema artifacts are updated together.
- Migration preserves existing user data or documents intentional loss.
- Added columns have defaults or nullable semantics compatible with existing rows.
- Indices, foreign keys, and constraints match entity/query expectations.
- DAO/repository behavior remains compatible with upper layers.
- Migration tests cover every affected version path when available.
Process
- Map changed entities, database version, migration objects, schema files, and tests.
- Compare old and new schema semantics.
- Trace how repositories and DAOs consume changed columns/tables.
- Check data preservation and default values.
- Cite file paths and line numbers for every finding.
Validation
Recommend:
./gradlew :data:testDebugUnitTest
If schema generation or migration tests are unavailable, state the remaining migration risk.
Output
Return a concise Markdown report with:
- Scope and affected versions
- Pass/fail table for each audit check
- Evidence-backed findings with file paths
- Required migration or test fixes
- Validation run or not run, with reason