From issue

Skill Diegocortes15/playwright-ia-automation-framework-saucedemo/.claude/skills/from-issue

An end-to-end test framework where a Jira ticket becomes a reviewed, TCMS-mirrored Playwright pull request — authored by AI agents, gated by deterministic CI. Built on saucedemo as both a reusable template and a portfolio piece.

Install

npx -y skills add Diegocortes15/playwright-ia-automation-framework-saucedemo --skill from-issue

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Generate Playwright tests from a Jira ticket (read via the Atlassian MCP), composing /scaffold-page-object when a target Page Object doesn't yet exist, and open a GitHub PR with the generated tests for review.

SKILL.md

3.6 KB, as published. Nobody here has run it

from-issue

Given a Jira issue key (e.g. SW-123), this skill reads the ticket via the Atlassian MCP, normalizes its requirement in whatever form it was written (narrative, Given/When/Then, bullet ACs, prose, or mixed), generates a set of Playwright tests, runs them locally, and opens a GitHub PR with a structured description. The PR is the review gate, and the GitHub-for-Jira app auto-links it onto the ticket. See ADR-0011.

How to use it

Tell Claude what you want:

Use the from-issue skill on SW-123.

Or for experimentation (skip push/PR):

Use the from-issue skill on SW-123 with dry-run.

If the ticket's feature already has a generated spec, the skill augments that file (adds the new tests, and adds/modifies the Page Object as needed) instead of creating a new file — see ADR-0010. Re-running any ticket that already contributed to the file refuses. To force a separate file instead of augmenting:

Use the from-issue skill on SW-123 with --new-file.

Workflow

The full procedural workflow is in references/workflow.md. Read that file before executing the skill.

Setup note: the Atlassian MCP must be connected (OAuth) for the Step 2 ticket read — defined at project scope in .mcp.json. Its read tools (mcp__atlassian__getAccessibleAtlassianResources, mcp__atlassian__getJiraIssue) are pre-authorized in allowed-tools above so reads don't prompt each run. If a future Atlassian MCP build renames those tools, update the allowed-tools line to match.

References

references/workflow.md — the procedural workflow
references/test-template.md — canonical test-file template
references/pr-description-template.md — structured PR body template
references/bucket-classification.md — Positive/Negative/Edge bucket definitions + worked examples (C.2.b)
references/smoke-policy.md — @smoke selection criteria + worked examples (C.2.c)
references/qa-analysis.md — Senior QA SDET judgment: when to merge/split/skip ACs (D.1)
references/test-principles.md — F.I.R.S.T. principles for generated tests (D.1)
references/playwright-conventions.md — Playwright best practices the skill follows (D.1)
references/data-placement.md — inline vs. externalized (data/) test data decision rule (D.1.4)
references/harness.md — data-driven config + autonomous harness growth (Phase H / ADR-0014)

Composition

This skill invokes /scaffold-page-object (C.1) when a Page Object inferred from the AC text has no matching file in src/pages/.