메뉴
Execute test suites and report results. Runs unit tests (yarn test) and E2E tests (yarn e2e) without modifying code. Use when asked to run tests, check if tests pass, or get a test report.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Drive the project's task list unattended — pick the next dependency-unblocked task, dispatch a task-worker subagent to complete it, self-verify the result, then loop. Use when the user wants to work through tasks.md sequentially without supervision (e.g. overnight runs). By default continues past isolated task failures (parks the failed work non-destructively, skips its dependents, keeps going) and trips a circuit breaker only on systemic failure; pass --strict for stop-on-first-failure.
Write end-to-end tests using Playwright. Test user behavior, not implementation details. Also useful for non-test Playwright scripting.
Migrate an npm package from long-lived NPM_TOKEN credentials to OIDC trusted publishing on GitHub Actions, with npm provenance attestations. Use this skill whenever the user mentions migrating to trusted publishing, eliminating NPM_TOKEN, setting up OIDC for npm, adding provenance attestations, publishing from CI without a token, or converting an existing release workflow to use a trusted publisher — even if they describe it in their own words like "get rid of the npm token" or "publish from GitHub Actions securely". Also use it proactively when reviewing a release workflow that still uses `NODE_AUTH_TOKEN`/`NPM_TOKEN` and the user is auditing CI secrets.
Write React components following idiomatic patterns, hooks best practices, and performance optimizations
Write React components designed to be easily tested with Playwright and Testing Library — semantic HTML, clear boundaries, no test-specific hacks
Write StyleX styles correctly — longhand properties, nested pseudo-classes/media queries, no shorthands
| name | test-runner |
| description | Execute test suites and report results. Runs unit tests (yarn test) and E2E tests (yarn e2e) without modifying code. Use when asked to run tests, check if tests pass, or get a test report. |
Run the project's test suites and report results. This is a read-only, execution-only skill — do not write, modify, or fix code.
| Request | Command | Fallback |
|---|---|---|
| Unit tests (default) | yarn test | yarn test:ci if tests hang |
| E2E tests (staging) | yarn e2e | — |
| E2E tests (local) | yarn e2e:local | — |
| All tests | Both unit and E2E | — |
Run whichever commands are requested. If no specific command is requested, run yarn test.
E2E tests running locally require a production build, not the dev server. HMR causes test flakiness with Playwright.
yarn dev-prod (builds then runs vite preview on port 8688)E2E_TESTING=true is set in .dev.varsyarn e2e:localDo NOT use yarn dev for E2E — the Vite HMR websocket interferes with Playwright's page lifecycle and causes flaky failures.
Always return results in this structure:
Commands Run: list each command executed
Overall Verdict: PASS or FAIL
Unit Tests:
E2E Tests (if run):
Failing Tests (if any):
Raw Output: include full command output as evidence
yarn test:ci)