Menü
Map SHAFT_ENGINE before broad search.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | graphify |
| description | Map SHAFT_ENGINE before broad search. |
Resolve the shared cache first: python3 tools/repository-map/resolve_graph_out.py --check. If it prints a path, query that graph before broad Grep/Read sweeps. If absent, fall back to rg + .memory (do not block the session on a rebuild); refresh only from the main checkout per tools/repository-map/README.md. Never commit graphify-out.
Use when planning SHAFT test coverage by exploring an app, generating test flow specifications, and preparing automation scenarios.
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.
