OpenParable
Skip to content
← Back to skills

M3u Epg Data Audit

Testing & Quality
m3u-epg-data-audit

M3u Epg Data 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 M3U and EPG data flows for parser behavior, channel/programme matching, duplicate handling, fallback behavior, joins, and timezone/time-range correctness.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/oxyroid/M3UAndroid/blob/HEAD/.claude/skills/m3u-epg-data-audit/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/m3u-epg-data-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.

M3U and EPG Data Audit

Audit playlist and guide data behavior with concrete parser, repository, DAO, and test evidence.

When To Use

Use when a task changes or reviews:

  • M3U, XMLTV, EPG, or Xtream parsing
  • Channel-to-programme matching
  • Playlist-to-EPG association behavior
  • DAO queries or repositories that return channels/programmes
  • Empty, malformed, duplicate, timezone, or time-range behavior

Required Context

Read first:

  • AGENTS.md
  • data/AGENTS.md
  • docs/ai/playbooks/m3u-epg-data.md
  • Relevant parser, DAO, repository, model, fixture, and test files

Audit Checks

Verify with file evidence:

  • Channel/EPG matching uses stable IDs or documented fallback order.
  • Duplicate programmes are handled deterministically.
  • Playlist-to-EPG associations are preserved across refresh/import flows.
  • Empty EPG data has an explicit fallback path.
  • SQL joins do not accidentally exclude channels without programmes.
  • Time ranges, date parsing, and timezone conversion are explicit and tested where possible.
  • Parser errors follow existing Flow/error-handling conventions.

Process

  1. Map parser entry points, repositories, DAOs, and tests.
  2. Trace one normal playlist with EPG and one empty/malformed guide path.
  3. Inspect joins and filters that combine channels and programmes.
  4. Check fixtures or tests for duplicates, missing guide data, and timezone offsets.
  5. Cite file paths and line numbers for each finding.

Validation

Recommend:

./gradlew :data:testDebugUnitTest

Also recommend targeted parser or fixture tests when present. If unavailable, state the untested data risk.

Output

Return a concise Markdown report with:

  • Scope and confidence
  • Data-flow map
  • Pass/fail table for each audit check
  • Evidence-backed findings with file paths
  • Regression tests or fixtures to add
  • Validation run or not run, with reason