Skip to content
Back to search

playwright-jira-creator

Claude Code skill: turn a Jira bug into a verified Playwright bug-recorder test

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/sharky412--playwright-jira-creator/badge.svg)](/listings/sharky412--playwright-jira-creator)

HTML

<a href="/listings/sharky412--playwright-jira-creator"><img src="/api/listings/sharky412--playwright-jira-creator/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Copy into your Playwright repo:

cp -r skills/playwright-jira-creator <repo>/.claude/skills/
cp commands/launch-playwright-jira-creator.md <repo>/.claude/commands/

Then fill in the project-specific references:

- `references/environments.md` - your environments, `.env` variable names, versions, sign-in flows - `references/repo-conventions.md` - test/data folders, fixtures (defaults: `tests/`, `data/`) - `references/ui-patterns.md` - proven locators for your app (grows as tests pass) - `scripts/api-cleanup.example.cjs` and `assets/spec-template.ts` - your API's login/delete endpoints

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 57 lines
  1. # playwright-jira-creator
  2. [![Claude Code skill](https://img.shields.io/badge/Claude%20Code-skill-D97757)](https://claude.com/claude-code)
  3. [![Playwright](https://img.shields.io/badge/Playwright-tests-2EAD33?logo=playwright&logoColor=white)](https://playwright.dev)
  4. [![Jira](https://img.shields.io/badge/Jira-bug%20recorder-0052CC?logo=jira&logoColor=white)](#use)
  5. [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
  6. A [Claude Code](https://claude.com/claude-code) skill that turns a Jira bug into a verified Playwright **bug recorder** test:
  7. a spec that asserts the bug's *current* behaviour, so it passes while the bug exists and fails once the fix ships.
  8. Workflow: read the ticket and its root cause, pick an environment that still has the bug, reproduce it interactively in a
  9. visible browser, write the spec and data file, run it in Chrome/Firefox until it passes because the bug reproduces,
  10. clean up all test data, and report.
  11. ## Install
  12. Copy into your Playwright repo:
  13. ```bash
  14. cp -r skills/playwright-jira-creator <repo>/.claude/skills/
  15. cp commands/launch-playwright-jira-creator.md <repo>/.claude/commands/
  16. ```
  17. Then fill in the project-specific references:
  18. - `references/environments.md` - your environments, `.env` variable names, versions, sign-in flows
  19. - `references/repo-conventions.md` - test/data folders, fixtures (defaults: `tests/`, `data/`)
  20. - `references/ui-patterns.md` - proven locators for your app (grows as tests pass)
  21. - `scripts/api-cleanup.example.cjs` and `assets/spec-template.ts` - your API's login/delete endpoints
  22. ## Requirements
  23. - Node + `@playwright/test`, `playwright`, `dotenv`, `@faker-js/faker` in the repo
  24. - Python 3 for `scripts/jira_fetch.py`
  25. - Jira access: `JIRA_URL` + `JIRA_PERSONAL_TOKEN` env vars, or a `jira` MCP server (mcp-atlassian) configured in Claude
  26. - `.env` with `BASE_URL`, `ADMIN_USERNAME`, `ADMIN_PASSWORD` (and `<ENV>_BASE_URL/_USERNAME/_PASSWORD` for other environments)
  27. ## Use
  28. ```
  29. /launch-playwright-jira-creator PROJ-12345
  30. ```
  31. or just ask Claude to "record PROJ-12345 as a Playwright bug test".
  32. ## Scripts
  33. | Script | Purpose |
  34. |---|---|
  35. | `scripts/jira_fetch.py <ID> [--attachments DIR]` | Print the issue (fields, comments, links) as Markdown; download attachments |
  36. | `scripts/explore/browser.cjs [url]` | Start a persistent visible Chrome with CDP on port 9333 |
  37. | `scripts/explore/step.cjs <step.js>` | Run one small exploration step against that browser |
  38. | `scripts/run-spec.sh <ID> [env] [args]` | Run one spec against an environment, log to `$TMPDIR` |
  39. | `scripts/api-cleanup.example.cjs` | Example REST helper for finding/deleting test data |
  40. ## License
  41. [MIT](LICENSE)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.