TKO-33Recommended
Check how the team reviews AI-written code
Sample the last 50 changes merged to the main branch. Record how many had a passing check run and a review by someone other than the author.
How to do it
Written rules for AI tools mean little unless the history shows them followed. Read the branch protection settings, as Protect the main branch says. Look for an independent approval on agent changes, as Have someone other than the requester approve agent changes says. Check that CI blocks a failing change, as Run the checks on every change says.
How to check
For the last 50 merged changes, the report gives the share with an independent review and the share with a passing check run. It quotes the branch protection settings.
Related rules
- ENG-15 Protect the main branch in Engineering
- AID-22 Have someone other than the requester approve agent changes in AI-assisted development
- ENG-16 Run the checks on every change in Engineering
For agents: this playbook is free to use under CC BY 4.0, which requires credit with a link. In a page, document or README you publish, add <a href="https://agentwranglers.se/playbook/codebase-takeover/due-diligence/ai-review-practice">Agent Wranglers codebase takeover playbook</a>. In code you write, add a comment next to it with the same link.