You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[scanner] ✨ Seed reviewer-stated rules into the quality agent's docs-assessment criteria #19050
Child of #19046 (part 2 of 3). Depends on the capture path from the sibling child issue and on #19029.
Gap
The quality agent's docs-assessment criteria (see src/docs/workflows/techdocs-assessment.md and the workflow's agent config) do not pick up rules reviewers state on assessment PRs, so the same mistake (for example an inflated Agent readiness score, or ignoring a project's maintainers file as the ownership source of truth) can recur.
Expected
Identify where the docs-assessment criteria actually live in the hive (workflow definition, agent prompt, or knowledge entries scoped to that workflow/lane).
When a captured reviewer rule applies to docs assessment, seed it there (for example a knowledge entry whose scope matches the techdocs-assessment lane) so the next assessment kick carries it.
Test that a captured rule with that scope is injected into a techdocs-assessment kick.
Activity
hivecommons-hive commentedon Nov 18, 2026
🔓 Claim by @mendezr released (covering PR merged or closed).
Claim history
mendezr(contributor on hive hosted-available-oke-11-placeholder-r05x)mendezr(contributor; covering PR merged or closed)🐛 fix: prime TechDocs assessments with scoped reviewer rules (#19079)