Skip to content

feat(bg-review): add bundled/pinned skill protection to review prompts (#27644)#27992

Closed
zccyman wants to merge 1 commit into
NousResearch:mainfrom
atyou2happy:feat/bg-review-skill-filter-27644
Closed

feat(bg-review): add bundled/pinned skill protection to review prompts (#27644)#27992
zccyman wants to merge 1 commit into
NousResearch:mainfrom
atyou2happy:feat/bg-review-skill-filter-27644

Conversation

@zccyman

@zccyman zccyman commented May 18, 2026

Copy link
Copy Markdown
Contributor

Summary

Two writer systems govern the same skill files with inconsistent rules:

Writer Filters bundled? Filters pinned?
7-day curator ✅ Yes ✅ Yes
bg-review (per-session) ❌ No ❌ No

Users discovering pin via hermes curator pin reasonably expect protection from automated edits — but bg-review ignored it.

Changes

  • Add "Protected skills" section to _SKILL_REVIEW_PROMPT and _COMBINED_REVIEW_PROMPT in agent/background_review.py
  • Lists three categories: bundled (shipped with Hermes), hub-installed (via hermes skills install), and pinned (via hermes curator pin)
  • When only protected skills need updating, the review agent says "Nothing to save." and stops
  • Aligns bg-review policy with curator's existing protection at curator.py L345/350

Testing

  • 4/4 existing test_background_review.py tests pass (zero regression)
  • Prompt text change only — no code logic modified

Fixes #27644

…prompts (NousResearch#27644)

The background review prompts (_SKILL_REVIEW_PROMPT and
_COMBINED_REVIEW_PROMPT) now include explicit protection rules
for bundled, hub-installed, and pinned skills — aligning with
the curator's existing policy at curator.py L345/350.

Before this change, bg-review could freely rewrite bundled skills
like 'hermes-agent' or pinned skills, while the 7-day curator
explicitly skips them.

The review agent now sees:
  • Bundled skills (shipped with Hermes)
  • Hub-installed skills (installed via hermes skills install)
  • Pinned skills (marked via hermes curator pin)
If only protected skills need updating, the review says
'Nothing to save.' and stops.

Fixes NousResearch#27644
@BoardJames-Bot

Copy link
Copy Markdown

BoardJames triage: I do not see a branch-local failure in the background-review prompt change. All non-test checks are green (lint/nix/e2e/builds/attribution/history/supply-chain), and the only blocker is the full Tests / test job ending after ~20m with no failed-log details, matching the current shared full-suite cancellation/timeout pattern on main and neighboring PRs. Local smoke on this branch passed: python -m py_compile agent/background_review.py. Next action is maintainer/shared-CI unblock/rerun (not a branch change here).

@alt-glitch alt-glitch added type/feature New feature or request P3 Low — cosmetic, nice to have comp/agent Core agent loop, run_agent.py, prompt builder tool/skills Skills system (list, view, manage) labels May 18, 2026
@teknium1

Copy link
Copy Markdown
Contributor

Merged via PR #28338 (cherry-picked onto current main with your authorship preserved via rebase-merge — commit af78449). Thanks for the contribution!

@teknium1 teknium1 closed this May 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

comp/agent Core agent loop, run_agent.py, prompt builder P3 Low — cosmetic, nice to have tool/skills Skills system (list, view, manage) type/feature New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature]: Align bg-review's bundled/pinned skill handling with the curator

4 participants