// 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.
Use when user wants to Find and remove genuine dead code using deadcode + vulture. Filters known false positives (dataclass fields, protocol methods, dunder hooks). Run before a cleanup commit.
| name | lint-and-validate |
| description | 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. |
Choose the smallest validation set that matches the files you changed, then expand if failures suggest a wider regression.
uv run ruff check src/ tests/ scripts/ -> uv run basedpyright src/ -> uv run pytestuv run prek run --files .github/workflows/<name>.ymluv run prek run --all-filesOCR, scanner, interaction, or input changes also need
uv run autoscrapper scan --dry-run against a live Arc Raiders window.
Generated data or default-rule changes should come from
uv run python scripts/update_snapshot_and_defaults.py --dry-run first, then
the real update if the preview is correct.
Quality passes can use qlty check -a, qlty metrics -a, and
qlty smells -a.
Do not finish with failing Ruff, BasedPyright, or pytest results caused by
your change.
If unrelated failures already exist, call them out explicitly in your final
summary.
Do not claim end-to-end OCR validation unless you used a live game
window.