BD tdd-e2e-pr-workflow
TDD-driven E2E workflow with real Playwright browser screenshots as PR proof. Use when: (1) fix bugs or implement features with test-first approach, (2) create PRs with visual before/after proof from E2E tests, (3) generate Playwright E2E tests with BEFORE/AFTER screenshots from real browser, (4) post screenshot comparisons as PR comments on GitHub. Workflow: pick one open issue → write E2E test → implement fix → PR with screenshots. Process ONE issue at a time. Complete current PR before starting next. NEVER use page.setContent() — always test through the real application. Triggers: "tdd e2e", "screenshot pr", "before after screenshot", "visual pr proof", "e2e pr workflow", "issue to pr with screenshots", "playwright tdd".
TDD-driven E2E workflow with real Playwright browser screenshots as PR proof.
As a process D 37/100 · Unfinished process — References files that are not bundled: references/debugging-guide.md, <BEFORE-screenshot-url>, <AFTER-screenshot-url>
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/debugging-guide.md - warning
missing-refreference to a missing file: <BEFORE-screenshot-url> - warning
missing-refreference to a missing file: <AFTER-screenshot-url>
Process rating: all ten parameters 37/100
- 0Tools and files. 3 referenced file(s) missing: references/debugging-guide.md, <BEFORE-screenshot-url>, <AFTER-screenshot-url>
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 4 mutating operations with no state check
- 40Consistency. Frontmatter name (tdd-e2e-pr-workflow) differs from the folder (pr-proof-of-work)
- 50When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 24 steps, 1 vague phrases
- 100Execution cost. Instruction body is 1644 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +3Output format is not stated: the model decides each time
- -41 reference files, but SKILL.md never points to them: the model will not open them
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 733: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 24 items
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.