General-purpose coding policy for Baruch's AI agents
91
93%
Does it follow best practices?
Impact
91%
1.15xAverage score across 12 eval scenarios
Advisory
Suggest reviewing before use
Your team uses GitHub pull requests as the primary gate for shipping code. Once a PR is open, the developer needs to wait for two independent signals before they can act: the CI pipeline (which runs tests, linters, and security checks) and an automated code reviewer that inspects the diff and leaves inline comments. Today, team members check these manually by visiting the GitHub UI and refreshing, which means they often miss feedback or start fixing things before the review is complete.
You have been asked to write a shell script that a developer can run after opening a PR to monitor both CI and the automated review status from their terminal. The script should tell the developer when both are finished and surface the review feedback — specifically the review decision state and any inline comments — so the developer knows what they need to address before they can merge.
Produce a shell script named monitor_pr.sh that accepts a PR number as its first argument (e.g. ./monitor_pr.sh 42). The script should be written for a repository whose GitHub owner and repo name are configurable (either hardcoded placeholders or environment variables — your choice). The script should:
Also produce a README.md explaining how to use the script and what each output section means.