Menu
Use when user wants to End-to-end scan failure pipeline - diagnose, identify root cause, fix, corpus replay, verify.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when user wants to Run the Arc Raiders AutoScrapper validation stack after edits. Use for linting, typing, tests, workflow checks, and broader repo validation.
Use when user wants to Update Metaforge snapshots and bundled default rules
Use when user wants to Validate OCR changes against failure corpus before shipping
Add a new OCR regression fixture from an ocr_debug image. Use when a scan misidentified an item and you want to lock in the correct result as a test case.
Use when user wants to Run full validation, push branch, and open a PR with appropriate context notes
Workflow for safely adding, removing, or renaming persisted config fields in config.py. Use whenever editing dataclass fields in src/autoscrapper/config.py. Covers incrementing CONFIG_VERSION, writing a migration function, and validating the round-trip.
| name | failure-to-fix |
| description | Use when user wants to End-to-end scan failure pipeline - diagnose, identify root cause, fix, corpus replay, verify. |
Use when a scan produces wrong actions, misread item names, or crashes. Chains diagnose → fix → validate without manual hand-offs.
uv run autoscrapper scan --dry-run 2>&1 | tee /tmp/scan-diag.txt
Debug images land in ocr_debug/. Key patterns:
*_infobox_detect_overlay.png: Green = detected, red = missed*_ctx_menu_processed.png: Text should be sharp and readable*_infobox_action_*_processed.png: Check binarization - text must be legibleRead /tmp/scan-diag.txt and route:
Garbled item names, low fuzzy score, Root cause=OCR preprocessing / threshold, Next step=Step 3a
infobox not found, timeout, wrong page state, Root cause=Geometry / detection, Next step=Step 3b
Wrong action (SELL when should KEEP), SKIP_UNLISTED, Root cause=Rules, Next step=Step 3c
CONFIG_VERSION, deserialization error, Root cause=Config schema, Next step=Step 3d
Use /triage-failures first if the failure corpus has relevant samples.
3a - OCR / threshold issue
ocr-reviewer agent with the log and relevant ocr_debug/ image timestamps.score_cutoff or binarization thresholds, use /threshold-change for safe before/after corpus replay./ocr-corpus-replay after the fix.3b - Geometry / detection issue
scan-validator agent with the log and page-state transitions./calibrate-vision if the context-menu crop constants need recalibration.3c - Rules issue
rules-reviewer agent with the item names that got wrong actions./add-rule to add or correct custom rules.3d - Config issue
config-reviewer agent with the config diff./config-bump to version-bump the schema change safely.Re-run dry-run and confirm the original failure is gone:
uv run autoscrapper scan --dry-run 2>&1 | tail -30
Then run the full suite:
uv run autoscrapper clean-debug 1
Then use /ci-promote to push the fix.