What GitHub already does
Branch protection can require reviews, passing checks, signed commits, and a linear history, and it can block force pushes. Pull request authors cannot approve their own pull requests. Code owners can be required for paths you list.
What it leaves open
The questions most standards actually ask are outside that list:
- Is the pull request linked to a Linear issue, a Jira work item, or a GitHub issue?
- Is that work item assigned, and is it still active?
- Did the pull request stay within a size you set?
- Did a human review it within the time you set, and was the approval a person rather than a bot?
- Was a production deployment approved by someone other than the person who requested it?
Where Warestack fits
Warestack is a GitHub app. A rule is a sentence from the standard you already wrote, turned into checks you can read before you turn them on. The result is a check on the pull request. It reports until you require that check in branch protection. It does not replace branch protection, and it does not read file contents, diffs, or commits.
Turn a standard into a check
Install on a few repositories. Rules report until you require the Warestack check.