fix-pr-issues

Resolves pull request feedback and failed checks, then re-runs the Codex review gate.

4.0k|282|Updated Dec 2, 2024
One-click install
npx skills add https://github.com/basicmachines-co/basic-memory --skill fix-pr-issues-basicmachines-co
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-pr-issues
Source: https://github.com/basicmachines-co/basic-memory/tree/main/.agents/skills/fix-pr-issues
Command: npx skills add https://github.com/basicmachines-co/basic-memory --skill fix-pr-issues-basicmachines-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Addressing pull request feedback, failed CI checks, and Codex review blockers is a fragmented, error-prone process where developers often miss unresolved threads or re-request reviews against stale commits. This Skill provides a disciplined loop for fixing PR issues and re-validating the latest head SHA. ## Core Features & Use Cases - Issue Ledger: Collects PR comments, inline review threads, failed GitHub Actions logs, and Codex review state into a structured ledger with source, problem, fix, and verification per item. - Guided Fix Loop: Enforces reading files fully before editing, keeping diffs narrow, running the smallest meaningful verification first, and committing with signed-off commits. - Latest-Head Review Gate: Re-applies the pr-review-loop after pushing, requiring current-head Codex approval and zero unresolved non-outdated threads before considering the PR ready. - Use Case: A reviewer leaves inline comments and a CI job fails on your Basic Memory PR. Use this Skill to triage each item, push targeted fixes, watch checks against the new head SHA, and reply to every thread with evidence. ## Quick Start Ask the assistant to use the fix-pr-issues skill to address all feedback and failed checks on the current pull request and re-run the Codex review gate on the latest head.

Frequently Asked Questions about fix-pr-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I address all feedback on a GitHub pull request systematically?▼

Build an issue ledger from PR comments, inline review threads, and failed Actions logs, then fix one item at a time with narrow diffs. After pushing, re-run the review gate against the new head SHA and reply to each thread with the fix commit and verification evidence.

How to re-run a Codex review after pushing new commits?▼

A prior Codex approval is stale after any code push, so you must re-apply the full review loop against the current head SHA. Require the current-head approval signal and confirm zero unresolved, non-outdated Codex threads before proceeding.

Does this skill merge the pull request after fixes?▼

No, the skill never merges a PR. It only resolves feedback, verifies checks against the latest head, and ensures the Codex review gate passes, leaving the merge decision to the user.

What should I do when a PR review comment is wrong or out of scope?▼

Reply with concise evidence explaining why the comment is wrong, stale, or not worth the tradeoff instead of forcing a code change. Resolve the thread only after the rationale is posted with supporting evidence.

Why do PR checks need to be watched against the new head SHA?▼

Checks triggered before your push run against the old commit and do not validate your fixes. Confirming checks run against the new headRefOid ensures the review gate evaluates the actual code you just pushed.