shamt-master-reviewer

Reviewing child-project pull requests for master repo governance involves evaluating read-only diffs to determine if changes are generic enough for all projects. The process enforces the separation rule, approves or requests changes, and ensures master-level consistency.

The separation rule for guides and scripts dictates that only universally applicable changes belong in the master repository. Project-specific modifications must be redirected to proposal docs, ensuring the master repo remains generic across all child projects.

You need to run a post-merge guide audit immediately after a pull request is merged into the master repository. This audit cycle triggers automatically to verify consistency across the entire guide ecosystem and catch integration issues.

To determine if a PR diff is generic enough for all child projects, analyze the file changes using read-only diffs. If the modifications apply universally without project-specific logic, they are safe for master import and approval.

Yes, the master PR reviewer handles proposal docs automatically. When the separation rule identifies project-specific changes, it guides contributors to proposal docs, ensuring non-generic modifications are routed correctly without manual intervention.

Yes, you can use read-only diffs to enforce pull request governance without write access. The reviewer assesses file changes safely to determine applicability, applies separation rules, and triggers post-merge audits without modifying the repository directly.