mcpField
C
codex-pr-feedback-loop

codex-pr-feedback-loop

github.com/patinaprojectAgent workflows155 installsUpdated today
Repository

About codex-pr-feedback-loop

A task-specific workflow for Codex agents managing pull request feedback in a GitHub repository. It requires a post-push task automation, distinguishes bot-started review threads from human feedback, and includes readiness checks without merging the PR.

Key features

  1. 01Implement, review, and push changes
  2. 02Create task-scoped automation after push
  3. 03Handle bot and human review threads differently
  4. 04Reproduce reports of recurring bugs
  5. 05Run PR readiness checks

Use cases

  1. 01Manage feedback on a Codex task's pull request
  2. 02Automate follow-up work in the task worktree
  3. 03Prepare a pull request without merging it

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/patinaproject/skills --skill codex-pr-feedback-loop

After installing, type/codex-pr-feedback-loopin Claude Code to confirm it loaded.

Bundled filesworkflows/thread-automation.md

Details

From the project README

Pull request feedback loop

First use the repository's normal development process to implement, review, commit, push, and create or update the pull request. After the first successful push, read the task automation instructions and create the automation for the current Codex task.

The automation belongs to this task and worktree. It is not a GitHub webhook or CI job. The linked instructions define its name, schedule, prompt, fallback, and stop condition.

Follow these rules:

  • Work only in the current directory's default GitHub repository.
  • Use a task automation so later runs retain this conversation's context.
  • Reply to and resolve a review thread only when a bot or GitHub App started it. Fix code requested by a human reviewer, but leave their thread open for the reviewer or user to answer and resolve.
  • If a human says a previously fixed bug remains or returned, reproduce that report again before changing more code.
  • Before stopping, apply ready-pr's readiness checks.
  • Leave issue status unchanged.
  • Do not merge the pull request.

Comments

Markdown supported