Fix Pr Issues
- 107 installs
- 3.6k repo stars
- Updated August 5, 2026
- basicmachines-co/basic-memory
fix-pr-issues is a Claude skill that resolves Basic Memory pull-request feedback and failed checks, then waits for BM Bossbot approval on the new head SHA.
About
This skill addresses pull request feedback, failed GitHub Actions checks, and BM Bossbot blockers for Basic Memory. It builds a short issue ledger, fixes items one at a time with narrow diffs, pushes, and waits for the BM Bossbot Approval status on the new head SHA. It never merges the PR itself.
- Resolves PR feedback, failed checks, and BM Bossbot blockers one ledger item at a time
- Pushes fixes then waits for the BM Bossbot Approval status on the exact new head SHA
- Never merges the PR and never dismisses substantive feedback without evidence
Fix Pr Issues by the numbers
- 107 all-time installs (skills.sh)
- Ranked #220 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
fix-pr-issues capabilities & compatibility
- Capabilities
- pr review · ci fix · check triage
- Works with
- github
- Use cases
- code review · ci cd · testing
What fix-pr-issues says it does
Resolve PR feedback and failed checks, then wait for BM Bossbot to approve the new head SHA. This skill never merges a PR.
If BM Bossbot reviews an older SHA, treat the approval as stale and keep waiting for the current one.
npx skills add https://github.com/basicmachines-co/basic-memory --skill fix-pr-issuesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 107 |
|---|---|
| repo stars | ★ 3.6k |
| Last updated | August 5, 2026 |
| Repository | basicmachines-co/basic-memory ↗ |
What it does
Resolve Basic Memory PR feedback and failed checks, then wait for BM Bossbot approval.
Who is it for?
Working through PR review comments, failed CI jobs, and BM Bossbot blockers until the current SHA passes.
Skip if: Merging the PR, or dismissing substantive feedback without evidence.
When should I use this skill?
Addressing Basic Memory PR feedback, failed checks, or BM Bossbot blockers from Codex.
What you get
Fixed PR with a passing BM Bossbot Approval status on the current head SHA and replies documenting each fix.
- fixed commits
- PR replies with verification and Bossbot status
By the numbers
- 4-field issue ledger (source, problem, fix, verification)
Files
Fix Basic Memory PR Issues
Resolve PR feedback and failed checks, then wait for BM Bossbot to approve the new head SHA. This skill never merges a PR.
Gather
1. Identify the PR:
gh pr view --json number,url,headRefOid,mergeStateStatus,statusCheckRollup
2. Collect feedback:
- PR comments and review summaries
- inline review comments and unresolved review threads
- failed GitHub Actions jobs and relevant logs
- the managed
BM_BOSSBOT_SUMMARYblock in the PR body
3. Build a short issue ledger:
- source
- concrete problem
- expected fix
- verification needed
Fix
1. Address one ledger item at a time. 2. Read each file in full before editing it. 3. Keep diffs narrow and preserve unrelated user changes. 4. Run the smallest meaningful verification first, then widen as needed. 5. Commit with git commit -s when code or docs changed.
Push And Recheck
1. Push the branch. 2. Watch checks for the new headRefOid. 3. Wait for the required BM Bossbot Approval status to pass on that exact SHA. 4. If BM Bossbot reviews an older SHA, treat the approval as stale and keep waiting for the current one.
Reply
For each addressed comment or blocker, reply with the fix commit, verification run, and current BM Bossbot status. Do not resolve or dismiss substantive feedback without evidence.
interface:
display_name: "Fix PR Issues"
short_description: "Address PR feedback and BM Bossbot blockers"
icon_small: "./assets/icon.svg"
icon_large: "./assets/icon.svg"
brand_color: "#2563EB"
default_prompt: "Use $fix-pr-issues to address PR feedback and wait for BM Bossbot Approval on the latest head SHA."
<svg xmlns="http://www.w3.org/2000/svg" width="128" height="128" viewBox="0 0 24 24" fill="none" stroke="#111827" stroke-width="1.8" stroke-linecap="round" stroke-linejoin="round">
<path d="M3 12h4l2-6 4 12 2-6h6"/>
<path d="M4 20h16"/>
</svg>
Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148FAQ
Does this skill merge the PR?
No. It resolves feedback and waits for approval but never merges the PR.
How does it treat a stale approval?
If BM Bossbot reviews an older SHA it treats the approval as stale and keeps waiting for the current one.