Is fix-pr-issues safe to install?

SaferSkills independently audited fix-pr-issues (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

.agents/skills/fix-pr-issues/SKILL.md · 1 file

.agents/skills/fix-pr-issues/SKILL.md1.5 KB · Markdown

name: fix-pr-issues

description: Use when addressing Basic Memory pull request feedback, failed checks, or BM Bossbot blockers from Codex.

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

Identify the PR:

gh pr view --json number,url,headRefOid,mergeStateStatus,statusCheckRollup

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_SUMMARY block in the PR body

Build a short issue ledger:

source
concrete problem
expected fix
verification needed

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 with git commit -s when code or docs changed.

Push And Recheck

Push the branch.
Watch checks for the new headRefOid.
Wait for the required BM Bossbot Approval status to pass on that exact SHA.
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.

fix-pr-issues— agent skill

Is fix-pr-issues safe to install?

Fix Basic Memory PR Issues

Gather

Fix

Push And Recheck

Reply

Audit the pieces. Scan the whole. Decide.