What problem does it solve? Teams struggle to enforce clear accountability for who reviews and approves changes to different parts of a codebase, leading to unreviewed critical changes and unclear responsibility boundaries. ## Core Features & Use Cases - CODEOWNERS Configuration: Create CODEOWNERS files mapping directories and modules to owning teams, including multi-team approval for critical paths like authentication and payments. - Reviewer Assignment Automation: Define rules that automatically route pull requests to the correct teams based on affected file paths. - Stewardship Patterns: Implement module steward classes that track ownership, gate PR approvals, and coordinate breaking changes. - Use Case: A platform team needs security review on all auth changes. Use this Skill to write a CODEOWNERS file requiring both @security-team and @backend-team approval for anything under /src/auth/. ## Quick Start Ask the agent to create a CODEOWNERS file that assigns the backend team to /src/ and requires security team approval for the auth module.
