菜单
Use when operating SHAFT report generation, Allure/Extent artifacts, CI summaries, upload actions, or failure extraction.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when analyzing SHAFT Allure results, Doctor reports, trace evidence, healer output, flaky locator/wait/assertion failures, retries, or test-fix recommendations.
Use when creating, reviewing, refactoring, repairing, or generating SHAFT web/mobile locators, smart locators, ARIA locators, XPath/CSS replacements, or codegen element identifiers.
Use when recording browser, Playwright, mobile, Appium Inspector, or user-performed flows into SHAFT tests with MCP Capture, replay, code blocks, or codegen insertion.
Use when reviewing, previewing, applying, guardrail-checking, or verifying generated SHAFT Java before or after inserting it into a repository, especially the coding-partner diff/apply/verify loop from IntelliJ.
Use when writing, reviewing, or repairing SHAFT Java tests, page objects, API tests, mobile tests, CLI/DB tests, assertions, waits, or TestNG/JUnit/Cucumber scenarios.
Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).
| name | allure-extent-report-operator |
| description | Use when operating SHAFT report generation, Allure/Extent artifacts, CI summaries, upload actions, or failure extraction. |
Use for report generation and CI artifact behavior. Do not treat a generated summary as valid until raw result files are populated.
AllureManager, report properties/paths, .github/actions/post-test-report, .github/actions/consolidate-test-results, workflows, and scripts/ci/extract_allure_failures.py.allure-results directory and delete only its contents.*-result.json files before trusting Allure status or summary.json.python3 -m pytest tests/scripts/test_extract_allure_failures.py. For Java report internals, run the narrow affected Allure manager tests.Report producer/consumer impact, raw result count evidence, parser or Java tests run, artifact names, and remaining OS/path risk.