nimblepros Playwright Issue Repro and Reporting Skill
Purpose
Provide a repeatable workflow for:
- Translating a GitHub issue into a reproducible Playwright scenario.
- Capturing evidence artifacts (
failure.png,trace.zip,video/). - Posting a structured issue comment with repro details and links.
Use This Skill When
- A UI bug in GitHub needs reliable repro steps.
- You need shareable evidence (screenshots, video, trace).
- You want a consistent issue comment format across triage sessions.
Required Inputs
- Issue URL or issue number.
- Expected behavior and observed behavior from the issue.
- App URL and environment context.
- Repro preconditions (user role, seed data, feature flags).
Workflow
- Build context from the issue:
- Extract expected behavior, observed behavior, and acceptance clues.
- Convert narrative to deterministic steps.
- Draft or adapt a Playwright repro test:
- Prefer semantic locators.
- Keep assertions user-visible.
- Avoid hard sleeps and implementation-detail assertions.
- Run repro and capture artifacts:
- Use existing project artifact flow under
TestResults/PlaywrightArtifacts/. - Collect screenshot, trace, and video paths.
- Publish an issue comment:
- Summarize repro result.
- Include environment, exact steps, and evidence links.
- Add short risk/impact notes and suggested next action.
Output Contract
Return:
- Repro script/test snippet (or reference to updated test).
- Artifact paths and what each artifact proves. Call out specific evidence for each assertion.
- Ready-to-post issue comment body.
Reusable Assets
- Workflow details: references/WORKFLOW.md
- Repro prompt template: templates/issue-repro-prompt.md
- Issue comment template: templates/issue-comment-template.md
Guardrails
- Do not claim reproduction unless assertion and artifacts agree.
- Do not include secrets or sensitive environment values in issue comments.
- Always distinguish "reproduced" vs "not reproduced" vs "inconclusive".