Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-08-06 09:26:52 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
bcquality/skills
History
Jesper Schulz-Wedde d994f2ad0e Require suggested-code or omission reason for mechanical findings 
BCQ now wins on coverage in the synthetic complex benchmark, but only
2 of 25 rendered comments carried GitHub suggestion blocks while the
AIRHack reviewer emitted suggestions for every finding. Tighten the
DO contract and leaf-skill instructions so suggested-code is no longer
a soft affordance for mechanical fixes.

Changes:
- Add optional findings[].suggested-code-omission-reason to the DO
  schema.
- Document suggested-code as expected for small, local, mechanical
  findings, with examples (delete unreachable code, Count() > 0 ->
  not IsEmpty(), move local Label, add missing ToolTip/OptionCaption,
  replace string-concatenated Error, change permission token, add an
  obvious else/guard branch).
- Require omission reasons when a mechanical-looking finding omits
  suggested-code.
- Update all AL leaf skills and al-code-review guidance with the same
  stronger contract.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
2026-05-28 15:00:10 +02:00
..
do.md Require suggested-code or omission reason for mechanical findings 2026-05-28 15:00:10 +02:00
entry.md fix: correct layer precedence to custom > community > microsoft in both entry.md and read.md 2026-05-22 09:55:35 +00:00
read.md fix: correct layer precedence to custom > community > microsoft in both entry.md and read.md 2026-05-22 09:55:35 +00:00
README.md Introduce the entry-point skill (skills/entry.md) 2026-04-17 14:01:09 +02:00
write.md Add [all] sentinel to bc-version; apply to version-agnostic knowledge 2026-04-23 16:00:03 +02:00

README.md

BCQuality global skills

This folder contains the skills that are not owned by any single layer. There are two kinds:

  • The entry-point skill — the first skill an agent invokes at runtime.
  • The three meta-skill contracts — stable references that define what the rest of BCQuality means.

The entry-point skill

File Role
entry.md ENTRY — Given a task context, returns a dispatch record naming the action skill(s) to invoke. The agent's first call when pointed at BCQuality.

Routing logic lives in Entry, not in the orchestrator. An agent that knows only "invoke /skills/entry.md first" has enough to drive the rest of the repo.

The meta-skill contracts

# File Role Who reads it
1 read.md READ — Schema + Use. How to read a knowledge file: frontmatter fields, section semantics, matching rules, layer precedence, conflict resolution. Any agent or action skill that consumes knowledge files.
2 do.md DO — Action Skill contract. The Source → Relevance → Worklist → Action template and the structured output every action skill produces. Includes super-skill composition. Any agent invoking an action skill; every action-skill author.
3 write.md WRITE — New Knowledge. Authoring rules for knowledge files. Defers to read.md for the schema. Contributors (human or agent) adding or editing knowledge files. Not used during consumption.

READ and DO are read on demand — typically by the first action skill the agent executes after dispatch. They are not prerequisites for invoking Entry. WRITE is only used when scaffolding new content.

These contracts are stable. Changes require a PR approved by both maintainers.

For the end-to-end flow — from orchestrator trigger through to findings integration — see ../agent-consumption.md. For the high-level project framing, see ../README.md.