Tests to Code Coverage

Analyze the project's tests — manual markdown cases and automated e2e tests — and its source code. Produce coverage.tests.yml — a map from source files (or globs) to test identifiers: suite IDs, test IDs, tags. Testomat.io keeps manual and automated tests in one project, so one coverage file serves both. @testomatio/reporter consumes it to run only the tests affected by a diff (Step 6).

Critical Constraints

• Map the tests that exist — manual markdown cases, automated e2e tests, or both. No unit tests. Do not suggest creating new tests.
• You may write to exactly three places, nothing else:
  • the coverage file — default coverage.tests.yml, or the path the user gave;
  • the .testeiya/ cache dir — clone automated test repos, pull manual cases from Testomat.io (Step 1);
  • .gitignore — add a .testeiya/ line if it is missing.
• Never modify a source or test file.
• Never pull or clone tests into a tracked folder — only into the gitignored .testeiya/.
• Everything in the coverage file must come from this project: file keys from its source tree, identifiers from the Step 2 inventory. Never copy a path or ID from this skill's docs — they are placeholders.
• No ad-hoc scripts, no parsers, never Python. File reads and grep only; the single exception is the bundled checker (Step 5); beyond that a one-line node -e '…' is the limit.
• Be proactive — never stop at a representative sample. A few entries per domain is a failed run. Keep mapping without asking permission to continue until the completion criterion in Step 4 is met.
• Stop if you cannot write the output file, or no tests are found and the user declines every option in Step 1.

Workflow