Repository navigation
[replaces #1106] chore(skills): remove cross-node-sync skill - #1108
Conversation
Per owner direction (2026-05-25): drop the rsync-based memory/notes propagation skill from upstream. The setup-rsync-sync.sh script had accumulated 62+ stuck wrapper processes on at least one node due to lockless re-firing, and the skill's per-fleet scope (Susan's Studio↔MacBook only) made it a poor fit for a public-product surface. Removes skills/cross-node-sync/ entirely + the README.md verified-skills table row. No code elsewhere imports from this skill — verified via grep across .py/.ts/.sh/.json/.md. Closes sonichi#1044 (which proposed making the sync scope configurable per-operator — moot now that the skill is being removed). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
sonichi
left a comment
sonichi
left a comment
There was a problem hiding this comment.
LGTM — carries forward identically from my #1106 cold review (closed minutes before this fresh PR). Same 8 files / 961 deletions / 0 additions. The independent grep I did on the #1106 branch confirmed no active code refs remain (only notes.legacy-backup/ archival entries from 2026-04-18..05-04, intentionally historical).
Rationale unchanged: 62-stuck-procs (lockless rsync, no flock guard) is the hard signal that the skill ships broken on a real cron schedule; per-fleet 2-node scope was never the right shape for the public surface; closes #1044 cleanly.
Owner merge call. (CI showing UNSTABLE = newly opened, awaiting checks.)
liususan091219
changed the title
bassilkhilo-ag2
left a comment
bassilkhilo-ag2
left a comment
There was a problem hiding this comment.
LGTM — same content as #1106 (replaces it; fork briefly deleted+recreated). Skill stays in private repo per owner direction. Cron for cross-node-sync was already deleted proactively this session.
VasiliyRad
left a comment
VasiliyRad
left a comment
There was a problem hiding this comment.
LGTM — clean removal. The cron entries that invoke this script already no-op gracefully (file-not-found exit). Skill preserved in private repo per owner direction.
Per owner direction (2026-05-25): drop the rsync-based memory/notes propagation skill from upstream. The setup-rsync-sync.sh script had accumulated 62+ stuck wrapper processes on at least one node due to lockless re-firing, and the skill's per-fleet scope (Susan's Studio↔MacBook only) made it a poor fit for a public-product surface. Removes skills/cross-node-sync/ entirely + the README.md verified-skills table row. No code elsewhere imports from this skill — verified via grep across .py/.ts/.sh/.json/.md. Closes sonichi#1044 (which proposed making the sync scope configurable per-operator — moot now that the skill is being removed). Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: Chi Wang <4250911+sonichi@users.noreply.github.com>
Re-opening — original #1106 auto-closed when the source fork was deleted. Same content. Pushed from recreated
liususan091219/sutando-fork.Removes
skills/cross-node-sync/entirely + the README.md capability-table row. Per owner direction 2026-05-25. Supersedes #1044 (already closed).Skill stays in
liususan091219/sutando-private:mainper owner direction.— Lucy