mirror of
https://github.com/microsoft/BCQuality.git
synced 2026-08-06 17:36:53 +01:00
Make domain-skill knowledge discovery index-aware
The 6 AL domain review skills and read.md now enumerate candidate articles from the BCQuality knowledge index (knowledge-index.json) instead of opening every file under the domain folder to read its frontmatter. The worklist selection predicate is unchanged (keywords intersect diff tokens, or topic matches a changed object type) - only the discovery source changes, so the same articles are selected. Full article bodies are read only for worklisted entries. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
parent
b19889ec46
commit
bd89abf8a8
7 changed files with 13 additions and 13 deletions
|
|
@ -140,7 +140,7 @@ Consumers that surface sample code to an end user or agent SHOULD cite the sampl
|
|||
|
||||
The standard workflow for finding applicable files:
|
||||
|
||||
1. Collect candidates by path (typically by `domain` subfolder, across enabled layers).
|
||||
1. Collect candidates from the knowledge index (`knowledge-index.json`) when the consumer provides one: it lists every filtered article with the frontmatter, `keywords`, `title`, and `description` that steps 2-3 need, so candidates are enumerated without opening each file. Absent an index, collect candidates by path (typically by `domain` subfolder, across enabled layers).
|
||||
2. Filter by frontmatter using the matching rules above. Files that are not applicable are discarded.
|
||||
3. Rank or narrow by `keywords` relevance to the task.
|
||||
4. Resolve conflicts via layer precedence.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue