메뉴
Copy generated and healed test files from the plugin's output directory into the user's target repo. Honours the user's sync.config.json mappings. Use when the user says "sync the tests", "push generated tests to the app repo", or after /generate-tests.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Convert a JSON test plan into production-ready Playwright TypeScript files (spec, page object, fixtures). Reads the latest plan in <output_dir>/<app>/plans/ unless a specific PLAN path is given. Use after /plan-tests, or when the user says "generate the tests", "write the spec for plan X".
Diagnose and rewrite a failing Playwright spec. Reads the spec + a captured error log, classifies the root cause, and writes a fixed file plus a healing report. Use when the user says "heal this test", "fix the broken spec", or pastes Playwright failure output.
Generate a structured JSON test plan for one feature of the configured app. Reads the user's app profile and writes the plan to <output_dir>/<app>/plans/<feature>-<timestamp>.json. Use when the user asks to "plan tests for X", "draft test cases for X", or kicks off a new feature's QA work.
Run the full QA pipeline end-to-end for one feature — plan, generate, then sync. Use when the user says "run the full pipeline for X", "automate end-to-end QA for feature X", or wants one-shot test creation + sync.
SOC 직업 분류 기준
| name | sync-tests |
| description | Copy generated and healed test files from the plugin's output directory into the user's target repo. Honours the user's sync.config.json mappings. Use when the user says "sync the tests", "push generated tests to the app repo", or after /generate-tests. |
| argument-hint | ["--dry-run"] |
| allowed-tools | ["Read","Write","Bash","Glob"] |
Copy generated artifacts from ${user_config.output_dir}/${user_config.app_name}/ into ${user_config.target_repo} according to the user's sync.config.json.
${user_config.app_name} — slug${user_config.output_dir} — source base (default output/)${user_config.target_repo} — destination repo path${user_config.playwright_test_dir} — relative subdir in the target repo (default e2e/tests)$ARGUMENTS — pass --dry-run to preview without copying${user_config.output_dir}/../apps/${user_config.app_name}/sync.config.json, then ./sync.config.json at project root, then fall back to the default mapping below.${user_config.target_repo} doesn't exist, stop and tell the user.bash "${CLAUDE_PLUGIN_ROOT}/scripts/sync.sh" \
--source "${user_config.output_dir}/${user_config.app_name}" \
--target "${user_config.target_repo}" \
--tests-dir "${user_config.playwright_test_dir}" \
[--dry-run]
cp -R with the mappings below, respecting the dry-run flag.If no sync.config.json is found, use these defaults:
Source (under ${output_dir}/${app_name}/) | Destination (under ${target_repo}/) | Overwrite |
|---|---|---|
tests/ | ${user_config.playwright_test_dir} | no |
healed/ | ${user_config.playwright_test_dir} | yes |
plans/ | e2e/plans/ | no |
reports/ | e2e/reports/ | no |
healed/ overwrites because the whole point of healing is to replace the broken file. Always run with --dry-run first if the user has uncommitted changes in the target repo.
If the user supplies one, it looks like:
{
"app": "<app_name>",
"sourceOutputDir": "<output dir for this app>",
"targetRepo": "<absolute or relative path>",
"mappings": [
{ "from": "tests", "to": "e2e/tests", "description": "Generated specs" },
{ "from": "healed", "to": "e2e/tests", "description": "Healed specs", "overwrite": true },
{ "from": "plans", "to": "e2e/plans", "description": "Plans for review" },
{ "from": "reports", "to": "e2e/reports", "description": "Test reports" }
],
"createIfMissing": ["e2e", "e2e/tests", "e2e/plans", "e2e/reports", "e2e/fixtures"]
}
Mappings without overwrite: true skip files that already exist (and log them).