agentleFS
kvantatechkvantatech/RedLine/.github/skills/parse-playwright-summary/SKILL.md

parse-playwright-summary

Skill1 starsChanged 3 months agoMITView on GitHub

Type: skill (deterministic, no model call — thin wrapper over parse.mjs) · Used by: func-run-one, corroborate-2-sources · Status: LIVE (2026-07-08) You will normalize a raw Playwright JSON report. There is no judgment here — run the script: - Exit 0 → contract written; report the script's OK — … line. - Exit 1 → the run is FAILED. Report the script's FAILED — <reason> line and STOP. Fails-closed cases: missing/invalid JSON, missing stats (not a Playwright report), zero tests found.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Never hand-parse the report — the script is the parser.

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

parse-playwright-summary

Normalize a Playwright JSON report into the canonical functional contract shape.

Type: skill (deterministic, no model call — thin wrapper over parse.mjs) · Used by: func-run-one, corroborate-2-sources · Status: LIVE (2026-07-08)


Prompt

You will normalize a raw Playwright JSON report. There is no judgment here — run the script:

node .github/skills/parse-playwright-summary/parse.mjs reports/<run_id>/results.json <run_id> reports/<run_id>/contract.json
  • Exit 0 → contract written; report the script's OK — … line.
  • Exit 1 → the run is FAILED. Report the script's FAILED — <reason> line and STOP. Fails-closed cases: missing/invalid JSON, missing stats (not a Playwright report), zero tests found.

Contract shape (what the script writes)

{
  "run_id": "<string>", "suite": "functional",
  "started_at": "<ISO or empty>", "duration_s": <number>,
  "tests_total": <n>, "passed": <n>, "failed": <n>, "skipped": <n>,
  "failures": [ { "test": "<suite > spec title>", "file": "<spec file>", "error": "<first line>" } ]
}

flaky results count as failed (retries are 0 by convention — flake detection is corroborate-2-sources' job, never Playwright retries).


Tools

Bash (node), Read — no MCP, no model calls.

Data

  • Reads: reports/<run_id>/results.json
  • Writes: reports/<run_id>/contract.json

Hard rules

  1. Never hand-parse the report — the script is the parser; its fixtures live in tests/fixtures/functional/.
  2. Fails closed — a malformed report is a FAILED run, never an empty-green contract.
  3. Behavior check: powershell -File tests/func-contract-check.ps1.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.