// Review pull requests for the awesome-web-agents repository. Use when asked to validate a PR, assess whether a submission fits the repo, inspect README or ARCHIVE additions, check merge readiness, or apply the repository's web-agent-first contribution policy to a GitHub pull request.
| name | awesome-web-agents-pr-review |
| description | Review pull requests for the awesome-web-agents repository. Use when asked to validate a PR, assess whether a submission fits the repo, inspect README or ARCHIVE additions, check merge readiness, or apply the repository's web-agent-first contribution policy to a GitHub pull request. |
Review PRs in this repository by applying the local policy and checking the changed files. Treat CONTRIBUTING.md as the source of truth for acceptance criteria.
CONTRIBUTING.mdREADME.mdARCHIVE.md when the change might belong in the archivescripts/validate_contribution.py when you need structural validation detailsDo not restate repo policy from memory when those files are available. Quote or summarize the repository's own rules instead.
Use gh first:
gh pr view <number> --repo steel-dev/awesome-web-agents --json title,number,state,isDraft,author,baseRefName,headRefName,files,additions,deletions,mergeable,mergeStateStatus,labels,url,bodygh pr diff <number> --repo steel-dev/awesome-web-agents --patchgh pr checks <number> --repo steel-dev/awesome-web-agentsIf you need the exact branch locally, fetch it with:
git fetch origin refs/pull/<number>/head:pr-<number>Use CONTRIBUTING.md for the actual acceptance rubric. Use README.md and ARCHIVE.md only to judge section fit, duplicates, and whether a project belongs in the main list or archive.
When reviewing a local branch or checking CI behavior, run:
python3 scripts/validate_contribution.pyTreat the script as a structural check, not the decision-maker. Human review still decides repository fit.
Use a code-review mindset:
Accept, Request changes, or Close.Keep the final review compact: