star-sync
Synchronize the local hub with every peer in state/peers.md via star-shaped pull-and-push.
- License 许可
- Apache-2.0
- 所属仓库
- usurobor/cnos
- 最近更新
- 2026-11-07
- Stars
- ★ 9
- Forks
- 0
01 前言 Front Matter
- name
- star-sync
- scope
- task-local
- triggers
- [ "sync", "star", "fetch", "push", "pull" ]
- description
- Synchronize the local hub with every peer in state/peers.md via star-shaped pull-and-push.
- governing_question
- How does the agent fan-out a sync across every peer without losing inbox messages or overwriting peer state?
02 资源文件 20
- 参考文档kata.md1.3 KB
- 脚本scripts/comment.sh469 B
- 脚本scripts/export-long-image.py8.0 KB
- 脚本scripts/export-long-image.sh493 B
- 脚本scripts/install-check.sh1.8 KB
- 脚本scripts/login.sh200 B
- 脚本scripts/mcp-call.sh3.2 KB
- 脚本scripts/post-detail.sh461 B
- 脚本scripts/recommend.sh130 B
- 脚本scripts/search.sh270 B
- 脚本scripts/start-mcp.sh4.6 KB
- 脚本scripts/status.sh132 B
- 脚本scripts/stop-mcp.sh697 B
- 脚本scripts/track-topic.py9.4 KB
- 脚本scripts/track-topic.sh129 B
- 脚本scripts/user-profile.sh458 B
- 脚本tools/xhs-downloader/batch_download.py1.3 KB
- 脚本tools/xhs-downloader/export_memory.py2.0 KB
- 脚本tools/xhs-downloader/export_to_workspace.py3.0 KB
- 参考文档tools/xhs-downloader/README.md2.5 KB
03 SKILL.md 正文
Star Sync
TERMS:
- The CN repo is hosted on GitHub and accessible via GitHub CLI
gh. state/peers.mdlists current peers with GitHub-backedhubURLs.
INPUTS:
- None (operates on the current peer list).
EFFECTS:
- For each peer in
state/peers.md:- Derives
OWNER/REPOfrom thehubURL when it points at GitHub. - Stars that repo via
gh repo star OWNER/REPO.
- Derives
- For any repo previously starred by this agent that is no longer listed in
state/peers.md:- Unstars the corresponding GitHub repo via
gh repo unstar OWNER/REPO.
- Unstars the corresponding GitHub repo via
This skill keeps GitHub stars aligned with the current peer list: peers are starred; non-peers are not.
04 同仓库更多 Skills
issues/triage
Issue triage doctrine pointer. Use when classifying a new issue, deciding dispatch eligibility, or deciding whether to close/supersede/defer.
issues/taxonomy
Issue label taxonomy pointer. Use when classifying an issue's kind/area/priority/effort/status/protocol/dispatch labels, or when the board needs to interpret them.
issues/map
Issue-board (Issue Pivot) generation domain. Use when reasoning about `cn issues map`'s fetch, taxonomy-parse, effort-computation, and render pipeline, or about the board's JSON/HTML output contract.
issues
cnos.issues package entrypoint. Use when reasoning about issue taxonomy, the Issue Pivot / issue-board (`cn issues map`), the read-only CDS issue-state evaluator (`cn issues fsm evaluate`), or the current command-dispatch disposition of issue tooling.
receipt-stream
Cross-cycle receipt-stream doctrine for protocol-iteration. Use when γ closes a cycle and writes the per-cycle iteration artifact (`cdd-iteration.md`), when γ updates the cross-cycle aggregator at `.cdd/iterations/INDEX.md`, when ε reads the receipt stream across cycles to surface protocol-gap patterns, when a finding's disposition lands a cross-repo patch and the cross-repo trace bundle attaches, or when a courtesy empty-findings stub is written for a `protocol_gap_count == 0` cycle.
mid-flight
Mid-flight γ→in-flight-α rescue channel. Use when γ needs to change a load-bearing fact (pinned axis, scope, AC, blocker) after α has begun coding, when γ edits the cycle's GitHub issue body mid-cycle, or when a spec change lands on origin/main while α/β polling sessions are in-flight.