메뉴
Turn a bug (GitHub issue number or description) into a failing Playwright spec that reproduces it - POM-based, tagged @bug, linked to the issue, and marked test.fail() so CI stays green until a fix flips it red. Use to capture a known bug as a regression-first test.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Draft a high-quality GitHub bug report from a QA observation - dedup, fill the bug_report form fields. DRAFT ONLY: it never files the issue; it hands you a ready `gh issue create` command to run yourself. Use when QA finds a defect to report.
Draft a GitHub proposal (feature / enhancement / task) - dedup, classify the type, fill the proposal form fields. DRAFT ONLY: it never files the issue; it hands you a ready `gh issue create` command to run yourself. Use when proposing new capability, an improvement, or a unit of work (not a defect - that's /report-bug).
Draft a clear, reviewer-ready pull request description for the current branch (or an existing PR) - feature-first summary, motivation, test plan, linked issues - verified against the real diff. DRAFT ONLY: it never creates, edits, or pushes; it hands you a ready `gh pr create`/`gh pr edit` command to run yourself. Use when writing up a PR.
Scaffold a new backend HTTP endpoint / vertical slice in apps/backend (Zod schema + defineAction + service + mounter) following the slice conventions. Use when adding a backend endpoint, action, or resource.
Scaffold a new Tailor content extension - content element (ce), content container (cc), meta input (mi), or plugin (pl) - and wire it into the registry. Use when adding a new ce/cc/mi/pl extension to the platform.
Scaffold a Playwright Page Object plus a functional spec in tests/, following the POM conventions. Use when adding an end-to-end test for a feature or flow.
| name | repro-spec |
| description | Turn a bug (GitHub issue number or description) into a failing Playwright spec that reproduces it - POM-based, tagged @bug, linked to the issue, and marked test.fail() so CI stays green until a fix flips it red. Use to capture a known bug as a regression-first test. |
Builds on /new-e2e and tests/CLAUDE.md. The spec asserts the CORRECT
behaviour and is expected to fail while the bug is live.
Get context. Given an issue number, read it: gh issue view <n>.
Otherwise take the repro steps from the user.
Page Object. Identify the area and reuse/extend the POM in
tests/pom/<area>/ (never inline selectors). Use /new-e2e if a POM
must be created first.
Write the spec under tests/specs/functional/<area>/<name>.spec.ts.
Assert the expected (currently-failing) behaviour and mark it:
test('order total reflects discount', {
tag: '@bug',
annotation: { type: 'issue', description: '<issue url>' },
}, async ({ page }) => {
test.fail(); // remove with @bug when #<n> is fixed
// drive via the POM, then assert the CORRECT result
});
Keep it in the main suite. test.fail() runs in CI and stays green
(expected failure); do NOT exclude @bug with --grep-invert. Keep the
repro deterministic - a flaky test.fail() will randomly redden CI.
Confirm it reproduces.
cd tests && pnpm playwright test specs/functional/<area>/<name>.spec.ts --project=chrome-admin (setup-admin runs first). Expect an
"expected failure".
Lifecycle. When a dev fixes the bug the test passes, Playwright
reports "expected to fail but passed", and the build goes red - the
signal to delete test.fail() + @bug and close the issue. Use
test.fixme() instead only if the repro crashes/hangs.