DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to add an advisory AI review to pull request workflows with OSS PR Reviewer

Post a bounded review summary to each pull request job without blocking merges.

Short answer: Create a workflow file with a pull_request trigger for opened, synchronize, and reopened events; then set permissions to contents: read and pull-requests: read for summary-only mode; use uses: vuphongle/[email protected] with github-token and openai-api-key set from repository secrets. All steps.

Credentials. Keep the OpenAI key in repository secrets; fork pull requests normally cannot access them under pull_request.

Who it is forA repository maintainer who wants every new or updated pull request to get a consistent advisory review in GitHub Actions.

The problemMaintainers often repeat the same context-gathering work on every pull request, and reviewers need the output close to the code.

The outcomeA workflow run that appends the Markdown report to the job summary and, optionally, one updated PR comment that includes the reviewed head SHA.

What you need first

  • Node.js 20 LTS or newer
  • A checkout of the vuphongle/oss-pr-reviewer repository
  • An OpenAI API key set as OPENAI_API_KEY (required for live reviews)
  • A GITHUB_TOKEN is recommended to avoid anonymous GitHub API rate limits
  • Network access to GitHub and OpenAI

Steps

  1. Create a workflow file with a pull_request trigger for opened, synchronize, and reopened events.
  2. Set permissions to contents: read and pull-requests: read for summary-only mode.
  3. Use uses: vuphongle/[email protected] with github-token and openai-api-key set from repository secrets.
  4. Add post-comment: true only if you also grant pull-requests: write.
  5. Check the job summary after a pull request run and treat the report as advisory.

Prompt for your agent

Add a GitHub Actions workflow to the target repository that uses vuphongle/[email protected] on pull_request events with summary-only permissions. Confirm the workflow YAML parses and that openai-api-key is read from secrets. Do not add pull_request_target or enable comment posting without asking.

Caveat. The Action does not create annotations or enforce a merge policy, and comment publication is best-effort under concurrent runs.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for vuphongle/oss-pr-reviewer and "Add an advisory AI review to pull request workflows"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer