What problem does it solve? Dakota pull requests cannot be trusted to GitHub Actions status alone because the repository's CI and merge-queue path is known to fail for unrelated reasons, leaving maintainers without reliable merge evidence. This Skill provides a lab-backed admission process that ties every merge decision to fresh build and test results from the exact PR head SHA. ## Core Features & Use Cases - Lab-backed PR validation: Dispatch the distributed dakota-build-pipeline for the exact PR head SHA, then run dakota-container-qa-pipeline smoke checks and full BDD/GUI suites against the resulting image. - Merge gating and triage: Classify infrastructure failures (BuildBarn storage, worker DNS, semaphore contention) separately from source/test failures, and merge directly only after a clean pass on the current head. - Repair loop: Fix localized PR defects in place, push to the contributor branch without rewriting history, and revalidate from the new head SHA. - Use Case: A maintainer has three open Dakota PRs with failing GitHub checks. Use this Skill to queue serialized BST builds, run container QA per PR, and merge only the PRs whose exact head SHA passed lab validation. ## Quick Start Review Dakota PR number 42 by dispatching the distributed build pipeline for its head SHA and running the container QA suite before deciding whether to merge.
