syahiidkamil/Software-Engineer-AI-Agent-Atlas / .claude/skills/playwright-cli
playwright-cli
VerifiedAutomate browser interactions, test web pages and work with Playwright tests.
| File | Kind | Size |
|---|---|---|
| LICENSE | other | 11.1 KB |
| SKILL.md | skill md | 15.3 KB |
| references/element-attributes.md | markdown | 665 B |
| references/playwright-tests.md | markdown | 1.7 KB |
| references/pr-attachments.md | markdown | 2.8 KB |
| references/request-mocking.md | markdown | 2.1 KB |
| references/running-code.md | markdown | 5.8 KB |
| references/session-management.md | markdown | 5.8 KB |
| references/storage-state.md | markdown | 5.2 KB |
| references/test-generation.md | markdown | 15.7 KB |
| references/tracing.md | markdown | 3.5 KB |
| references/video-recording.md | markdown | 9.2 KB |
references/pr-attachments.md
View on GitHub# Attaching Screenshots and Videos to Pull Requests
`gh` 2.99+ uploads local images and videos with the repeatable `--attach` flag on `gh pr create`, `gh pr comment`, `gh pr edit`, `gh issue create`, `gh issue comment` and `gh issue edit`. PNG, JPEG, GIF, WebP, SVG, MP4, MOV and WebM are accepted, so `playwright-cli screenshot` and `video-start` output can be attached as is.
## When to attach
Attach visual evidence when it saves the reviewer a checkout: a screenshot of a UI fix, a before/after pair, a short video of a new user-facing flow, or the failure state when filing a bug. Skip it for refactors, backend-only changes and anything the diff already shows.
## From a local session
```bash
# capture the evidence
playwright-cli open http://localhost:3000/settings
playwright-cli screenshot --filename=settings-after.png
playwright-cli video-start settings-flow.webm
playwright-cli click e5
playwright-cli fill e7 "New name" --submit
playwright-cli video-stop
# attach when creating the PR; alt text goes after "#" (images only)
gh pr create --title "fix(settings): keep name after save" --body-file body.md \
--attach './settings-after.png#Settings page after saving' --attach ./settings-flow.webm
# or comment on an existing PR / issue
gh pr comment 123 --body "Recorded the new flow end to end." --attach ./settings-flow.webm
gh issue comment 456 --body "Failure state after submitting the form." --attach ./failure.png
```
Reference the file in the body as `` to place it inline and `gh` rewrites the path to the uploaded URL. Unreferenced attachments are appended at the end in flag order.
## Limits
- Images up to 10 MB, videos up to 10 MB on free plans and 100 MB on paid plans, so keep recordings short.
- Alt text is not supported on videos.
- Uploads need push access to the repository.
- Available on GitHub.com and GitHub Enterprise Cloud only.
## From CI
Attach the screenshots and videos Playwright Test already saves under `test-results` (`screenshot: 'only-on-failure'`, `video: 'retain-on-failure'`) with the same command:
```yaml
permissions:
pull-requests: write
steps:
- run: npx playwright test
- name: Attach failure screenshots and videos to the PR
if: failure() && github.event_name == 'pull_request'
env:
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: |
files=$(find test-results -name '*.png' -o -name '*.webm' | head -20)
if [ -n "$files" ]; then
gh pr comment ${{ github.event.pull_request.number }} \
--body "Failure screenshots and videos from run ${{ github.run_id }}." \
$(printf -- '--attach %s ' $files)
fi
```
For a polished walkthrough of a new feature, record a hero script as described in [video-recording.md](video-recording.md) and attach the resulting WebM the same way.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |