#182 Add machine-readable review orchestration contract
BCQuality now generates a deterministic, machine-readable skill index from review frontmatter and validates review composition through schemas and CI checks.
- 8files
- 2AL files
- 0objects
Pull request · merged into main on 2026-09-15 by dayland · 8 files (+803 -3), 2 AL · feature · tier official · reviewed (checked by Opus)
What changed
- Generates versioned skill index from action-skill frontmatter for stable review orchestration
- Adds JSON schemas for skill index and findings reports to define the review contract
- Validates flat review structure including leaf IDs, paths, ordering, and output contracts in CI
- Includes generator tests and repository validation without modifying review knowledge
- Enables BC-ALAgents to consume a stable, mechanically-owned orchestration contract
AL objects touched
microsoft/skills/review/al-code-review.md: modified, not in the BC? snapshotskills/do.md: modified, not in the BC? snapshot
Context
- Systems: development, copilot
- From the description: “BC-ALAgents needs a stable contract that defines exactly which review leaves exist and their required order.”
Source: metadata of a merged pull request in microsoft/BCQuality (bcquality): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).