← ClaudeAtlas

vr-plannerlisted

Plans how to verify changes to an os-autoinst-distri-opensuse (OSADO) checkout. Use this skill when the user asks "how do I test my change", "what verification run (VR) should I do", "which openQA job should I clone", or "what's affected by my edit". Determines required unit tests, affected test modules, YAML schedules, and openqa-clone-job commands.
mpagot/os-autoinst-distri-opensuse-gemini · ★ 1 · Testing & QA · score 58
Install: claude install-skill mpagot/os-autoinst-distri-opensuse-gemini
<instructions> You help an OSADO developer figure out how to verify their changes to `os-autoinst-distri-opensuse`. Use the Perl helpers in `scripts/` to do the work. Never duplicate their logic in shell or in your own reasoning. Script paths below are relative to this skill's installed directory. ## Pipeline overview ``` classify_changes.pl (orchestrator — call first) ├── tests/ → find_test_schedule.pl ├── lib/ → find_unit_test.pl + find_affected_tests.pl ├── data/ → find_data_consumers.pl └── schedule/ → find_openqa_job.pl (NETWORK — confirm host first) ``` All scripts accept `--repo /path/to/osado`, `--json`, `--verbose`, and `--help`. ## Process ### Phase 1 — Classify and produce the testing plan 1. **Identify the OSADO repo path.** If the user did not state it, ask them. Verify it exists and contains both `lib/` and `tests/`. Most of the time it should be the current folder. 2. **Identify the change set.** By default `classify_changes.pl` reads `git diff --cached` (staged). Honour the user if they ask for a different source: * unstaged working tree → `--git-diff` * a specific commit → `--git-commit <hash>` * an explicit list → pass file paths as positional args 3. **Run the orchestrator with all helpers chained:** ```bash perl scripts/classify_changes.pl \ --repo /path/to/osado --helpers ``` This single call also runs `find_test_schedule.pl`, `find_unit_test.pl`, `find_affected_