mirror of
https://github.com/microsoft/BCQuality.git
synced 2026-08-06 17:36:53 +01:00
f91fc1602f
Drop the specific pattern checklist (architecture-level smells, error- handling gaps, magic constants, privacy/telemetry surface, resource lifecycle - with concrete code patterns under each). It baked case- study findings into the skill contract and aged badly. Replace with a domain-level framing: walk by the domains the sub-skills already cover (performance, security, privacy, style, upgrade, UI) plus the cross- cutting concerns (architecture, error handling, resource lifecycle). The domains are anchors for completeness, not a script. The structural rule - do an explicit self-review pass after the leaves - is what carries the value. The content of the pass belongs in the agent's general AL judgement and in the knowledge layer. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| review | ||
| .gitkeep | ||