Clarify baseline build guidance for update-os-coverage skill

[richlander]

Note

This PR description was generated with GitHub Copilot.

Summary

• add a Prerequisites section to update-os-coverage
• clarify that repo-wide baseline builds are not required for YAML/docs-only Helix queue and image reference updates
• point readers back to copilot-instructions.md only when the task expands into product code changes

Testing

• not run (documentation-only change)

[Copilot]

Pull request overview

This PR clarifies operational guidance for the update-os-coverage skill by adding a prerequisites note that distinguishes YAML/docs-style Helix queue/image reference updates from product code changes, and points readers to the baseline build workflow only when build/test validation becomes relevant.

Changes:

• Add a new Prerequisites section to update-os-coverage skill documentation.
• Clarify that the repo-wide baseline build workflow is not required for queue/image metadata-only updates, unless the task expands into product code changes.

[github-actions]

🤖 Copilot Code Review — PR #126523

Holistic Assessment

Motivation: Justified. The repo-wide baseline build takes ~40 minutes and is mandatory per copilot-instructions.md. The update-os-coverage skill only modifies YAML pipeline definitions and docs, so requiring a baseline build is a significant waste of agent time. This note prevents that.

Approach: Correct. Adding a Prerequisites section with a blockquote callout is the right mechanism and matches the pattern used by sibling skills (e.g., vmr-codeflow-status/SKILL.md also has a ## Prerequisites section at the same location). The note clearly delineates when builds are needed (task expands into code changes) vs. when they are not.

Summary: ✅ LGTM. Single-file documentation-only change that is well-scoped, correctly placed, and consistent with existing skill conventions. No issues found.

---

Detailed Findings

✅ Content & Accuracy

The guidance is accurate — the update-os-coverage skill modifies files like eng/pipelines/helix-platforms.yml and eng/pipelines/*/helix-queues-setup.yml, which are YAML pipeline definitions. These do not require a product build to validate. The note correctly redirects to copilot-instructions.md only when the scope expands to code changes.

✅ Consistency with Sibling Skills

The ## Prerequisites section placement (between the intro paragraph and ## When to use) follows the same structure as vmr-codeflow-status/SKILL.md. The blockquote callout format is appropriate for an important-but-brief note.

✅ Link Validity

The relative link /.github/copilot-instructions.md resolves correctly — the target file exists at that path.

✅ Markdown Formatting

No trailing whitespace. No formatting issues. The blockquote with bold lead-in (> **Baseline build not required:**) is clear and scannable.

---

Note

This review was generated by Copilot and may not cover all aspects a human reviewer would evaluate.

Generated by Code Review for issue #126523 · ◷