# PR Review Loop

Enforce the Basic Machines GitHub PR review loop before merging.

- Repository: https://github.com/basicmachines-co/basic-memory (4440 stars)
- Category: Git and review
- License: AGPL-3.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add basicmachines-co/basic-memory --skill pr-review-loop -g -a claude-code -y`
Codex: `npx skills add basicmachines-co/basic-memory --skill pr-review-loop -g -a codex -y`
Cursor: `npx skills add basicmachines-co/basic-memory --skill pr-review-loop -g -a cursor -y`
Gemini CLI: `npx skills add basicmachines-co/basic-memory --skill pr-review-loop -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add basicmachines-co/basic-memory`

## Description

Enforce the Basic Machines GitHub PR review loop before merging. Use whenever Codex is preparing to merge, squash-merge, auto-merge, declare a PR ready, monitor Codex comments, address review feedback, or wait for Codex approval on a GitHub PR, especially when the user says "approved", "merge", "ship", "PR is ready", "monitor Codex comments", or "address Codex feedback".

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# PR Review Loop

## Hard Rule

Do not merge a PR merely because CI is green, the branch is mergeable, review threads are outdated, or no current Codex thread is visible.

Merge only when one of these is true:

- Codex has finished reviewing the latest head and left an explicit thumbs-up approval signal.
- The user explicitly overrides this gate with language like "merge without waiting for Codex approval" or "override Codex gate".

Codex often leaves that thumbs-up as a reaction on the PR description/body itself
(the GitHub Issue/PR object), not on its "Codex Review" issue comment. Do not
only inspect issue comments.

If Codex's newest fresh reaction on the PR body or a relevant comment is eyes,
it is reviewing. Wait and keep checking.

If Codex leaves a comment, review body, or inline thread containing substantive
feedback, the PR is not approved. Use judgement: fix the code when the comment
is right; reply with evidence when it is wrong or intentionally not worth
changing. A no-issue summary or boilerplate-only review body is not a blocker,
but it also does not replace the required thumbs-up.

## Signals

The rest: https://github.com/basicmachines-co/basic-memory/blob/HEAD/.agents/skills/pr-review-loop/SKILL.md