NousResearch/hermes-agent

Skill update failures in background review fork

Cluster 95976. Data as of

Nothing open on GitHub. Fix merged in #115299 on 18 Sep 2026. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #115299. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #115299. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and fixes center on a bug where the background review fork cannot update skills, caused by conflicts between read-before-write guards and skill_view dedup stubs. Several related patches address seeding context and removing or correcting the dedup stub behavior in the fork.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #112196 fix(curator): consolidation pass can patch skills again (#111604, salvage #111605)

    merged to main

    files: agent/curator.py, tests/agent/test_curator.py

  • #115299 Background review fork can update skills again: no dedup stub in the fork (#95976, salvage #95975)

    merged to main

    files: contributors/emails/[redacted:email], tests/tools/test_file_read_guards.py, tests/tools/test_skill_view_dedup.py, tools/file_tools.py, tools/skills_tool.py

2 PRs closed without merging

From the close comments: superseded by another PR 2

  • #95993 fix(skills): the dedup stub must mark the read for the review fork guard · superseded by another PR → #115299, #95976, #95975
  • #107734 fix(curator): seed the review read-mark store in the fork's context · superseded by another PR → 8b58562, #112196
Closed issues · 1
  • Closed#95976Background review fork fails to update skills 100% of the time — read-before-write guard conflicts with skill_view repeat-view dedup
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.40: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Merged PRs
#112196, #115299
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
18 Sep 2026

For your agent

The same facts, typed.