菜单
Reconcile Silk Linear issues with repository, OpenSpec, branch, and GitHub PR reality, applying only unambiguous status corrections and reporting uncertain drift. Use only when Julia explicitly invokes $silk-sync or asks to sync the Silk queue.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/julia-script/silk --skill silk-sync命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | silk-sync |
| description | Reconcile Silk Linear issues with repository, OpenSpec, branch, and GitHub PR reality, applying only unambiguous status corrections and reporting uncertain drift. Use only when Julia explicitly invokes $silk-sync or asks to sync the Silk queue. |
Read ../../silk-manager/WORKFLOW.md and ../../silk-manager/LINEAR.md completely before acting.
This skill performs periodic reconciliation. It may update existing Linear issues. It must not edit repository source, switch branches, delete worktrees, clean files, push, merge, close PRs, or create new maintenance issues.
Fetch the canonical Linear project by ID from LINEAR.md and verify its team. Never resolve or
recreate it by display name. Read its nonterminal issues. If it cannot be resolved, stop before
writing.
Inspect the current checkout, local and remote branch information already available, active and
archived OpenSpec changes, and GitHub PRs for julia-script/silk. Do not fetch unless Julia asks.
Match by explicit Linear link, Linear-generated branch identifier, or an unambiguous issue identifier in a branch or PR. Never match by title alone when more than one issue is plausible.
Apply high-confidence corrections directly:
## Gate -> remove Blocked and keep or return to Todo;Re-read every issue before and after mutation. Preserve priority, estimate, relations, and specification unless the observed transition requires a focused note.
Report but do not automatically reset ambiguous stale In Progress work, In Review issues without a PR, possible overlaps, unresolved gates, dirty worktrees, or branches that may belong to a live Codex task. Give the evidence and the smallest next decision.
Report applied transitions, unresolved drift, queue head, and coverage. A fully consistent sync is a useful result; do not invent cleanup.
Obvious reconciliation does not need a separate proposal/apply ceremony because invocation of this skill is the scoped authorization. Ambiguous or destructive action still requires Julia's decision.