Description
#421 introduces an agent which checks all our docs for drift
It'd be awesome to run this as part of our PR automation to check that changes do not introduce such drift.
Motivation
Check that changes do not introduce drift in docs.
Suggested Implementation
Need to consider:
- github workflow triggered on PR
- minimal AWS creds (if possible to use with kiro cli)
- comment back on PR with findings as bot user
Contribute to feature