Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-10-07 07:36:54 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

Add machine-readable review contracts

Browse source 
Generate a deterministic action-skill index from frontmatter, publish structural schemas for orchestration and findings, and validate flat review composition in CI.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 76eb42c4-2acd-4f9c-a898-f4a44f9d46f7
This commit is contained in:
dayland 2026-09-11 13:55:03 +01:00
parent 51597068b1
commit 25accf021e
8 changed files with 803 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

12
skills/do.md
View file

@ -106,6 +106,12 @@ Every action skill MUST contain these five sections, in order:
Every action skill emits a single JSON document that conforms to this schema:
The machine-readable structural schema is
[`schemas/findings-report.schema.json`](../schemas/findings-report.schema.json).
The rules below remain authoritative for semantic checks that JSON Schema
cannot perform by itself, including summary arithmetic, reference existence,
source-scope locations, and article-body retrieval.
```json
{
"skill": { "id": "string", "version": 1 },
@ -314,6 +320,12 @@ the declared worklist order, and wait for every invocation to finish before
performing any super-skill self-review or final rollup. Scheduling MUST NOT
change relevance, coverage, failure, reference-integrity, or output semantics.
Orchestrators SHOULD generate `skill-index.json` with
`tools/Build-SkillIndex.ps1` and consume the super-skill's ordered `subSkills`
from that index instead of parsing Markdown. Action-skill frontmatter remains
the source of truth; the generated index conforms to
`schemas/skill-index.schema.json`.
### Section interpretation for super-skills
The five required sections still apply. Their meaning shifts from knowledge files to sub-skills: