fix-pr-issues
Use when addressing Basic Memory pull request feedback, failed checks, or Codex review blockers, then re-running the latest-head review gate.
- Installs
- 120
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/basicmachines-co/basic-memory --skill fix-pr-issues- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads fix-pr-issues automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Fix Basic Memory PR Issues
Resolve PR feedback and failed checks, then apply pr-review-loop to the new
head SHA. This skill never merges a PR.
Gather
- Identify the live PR and latest head:
gh pr view --json number,url,headRefOid,mergeStateStatus,statusCheckRollup
- Collect the exact feedback:
- PR comments and review summaries
- inline review comments and unresolved review threads
- failed GitHub Actions jobs and relevant logs
- Codex reactions and latest-head review state described by
pr-review-loop
- Build a short issue ledger with the source, concrete problem, expected fix, and verification needed for each item.
Fix
- Address one ledger item at a time.
- Read each file in full before editing it.
- Keep diffs narrow and preserve unrelated user changes.
- Run the smallest meaningful verification first, then widen as needed.
- Commit changed code or documentation with
git commit -s.
If a comment is wrong, stale, intentionally out of scope, or not worth the tradeoff, reply with concise evidence instead of forcing a code change.
Push And Recheck
- Push the branch.
- Confirm checks are running against the new
headRefOidand watch them to completion. - Apply
pr-review-loopin full. A prior Codex approval is stale after a code push; require the current-head approval signal and zero unresolved, non-outdated Codex threads. - If new feedback appears, add it to the ledger and repeat the loop.
Reply
For each addressed comment or blocker, reply with the fix commit, verification run, and current Codex gate status. Resolve a substantive thread only after the fix or rationale is posted with evidence.
FAQ
What does the fix-pr-issues skill do?
Use when addressing Basic Memory pull request feedback, failed checks, or Codex review blockers, then re-running the latest-head review gate.
How do I install fix-pr-issues?
Run npx skills add https://github.com/basicmachines-co/basic-memory --skill fix-pr-issues in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/fix-pr-issues/ (personal) or .claude/skills/fix-pr-issues/ (project).
Which AI agents can use fix-pr-issues?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is fix-pr-issues safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains fix-pr-issues?
It is published by basicmachines-co in basicmachines-co/basic-memory. It has 120 recorded installs.
More from basicmachines-co/basic-memory
memory-notes
basicmachines-co/basic-memory
How to write well-structured Basic Memory notes: frontmatter, categorized observations, wiki-link relations, and knowledge-graph best practices. Use when creating or improving notes.
memory-continue
basicmachines-co/basic-memory
Resume prior work by rebuilding context from the Basic Memory graph via memory:// URLs, recent activity, and search. Use at session start or on 'continue with...', 'back to...', 'where were we?'
memory-capture
basicmachines-co/basic-memory
Capture a working thread's current state into one coherent Basic Memory note; on re-capture, rewrite it in place. Use mid- or end-of-thread when decisions, insights, or context are worth keeping.
memory-curate
basicmachines-co/basic-memory
Curate the Basic Memory graph: link orphan notes, propose typed relations, merge duplicates, audit tags and folders, build hub notes. Use to organize and connect a knowledge base as notes accumulate.
memory-reflect
basicmachines-co/basic-memory
Sleep-time reflection: review recent Basic Memory activity and fold lasting decisions, lessons, and facts into the notes they belong in. Run 1-2x daily, on a heartbeat, or when asked.
memory-metadata-search
basicmachines-co/basic-memory
Search Basic Memory notes by custom frontmatter fields with equality, range, array, and nested filters. Use when finding notes by status, priority, confidence, or any YAML field, not free text.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.