一键导入
sync
Use when the user says "sync" or wants to commit, rebase, push, and converge this dotfiles repo. Uses just up as the public converge command.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when the user says "sync" or wants to commit, rebase, push, and converge this dotfiles repo. Uses just up as the public converge command.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | sync |
| description | Use when the user says "sync" or wants to commit, rebase, push, and converge this dotfiles repo. Uses just up as the public converge command. |
Full dotfiles sync: commit, rebase, converge with just up, then push.
Check for changes
git status
git diff
Commit if changes exist
Rebase onto remote
git pull --rebase
Resolve conflicts if any
git add <file>
git stash drop # if autostash conflict
Converge the machine
just up
Inspect post-converge drift
just up can capture intentional live config back into repo sourcegit status againPush
git push
git status
Relay sudo reminder if shown
sudo ./scripts/sync-sudo.sh, tell the user exactly thatjust up Doesjust up:
just status, just doctor, and just explain./scripts/sync-sudo.sh (user runs manually, only if needed):
just statusjust doctorjust explain <target>dotctl status / just statusjust edit <target>Use when a tool, library, or framework doesn't support what you need and official docs don't cover it — finding solutions off the happy path. Triggers on "how do I make X do Y", "X doesn't support Y", undocumented behavior, bleeding-edge tool limitations, workarounds for missing features, or when the mainstream answer is "you can't do that"
Iteratively review, refactor, verify, and commit toward less code by sharing primitives and improving functional composition. Use when the user asks for a strict refactor review loop, "get a review strictly for refactoring to less code", "repeat review/fix/commit until empty", or similar wording.
Poll, diagnose, and report on a GitHub PR's CI. Use this skill whenever you're about to watch a PR's CI to a terminal state — after pushing commits to a PR, after /git_sync, when the user says "is CI green", "wait for CI", "check the PR's checks", "monitor CI", "did CI pass", "watch the workflow", "fix CI failures", or any phrasing that asks whether a PR is ready to merge based on its checks. ALSO use proactively whenever you push a commit to a branch that has an open PR — never spin up an ad-hoc `gh pr checks --watch` or count-based poll. This skill is the only authority for PR CI status; ignore any older guidance suggesting otherwise.
Complete GitHub PR review-comment closeout. Use whenever the user asks to address, fix, handle, clear, close, resolve, respond to, or follow up on PR review comments, review threads, requested changes, bot findings, CodeRabbit, Greptile, or Devin review feedback. Addressing a review thread includes a written thread reply and resolving the thread after the fix or justification is pushed.
Orchestrate land-pr, gh-ci, and land-merged into one end-to-end landing pipeline. Use when the user asks to land complete, land and merge, merge on green, finish a PR end to end, or land without another confirmation loop.
Use after a GitHub pull request has already been merged to refresh the local develop worktree, remove the local git worktree that backed the merged PR, and delete the merged local branch. Trigger on requests like "land merged", "cleanup merged PR worktree", "sync develop and delete the PR worktree", or "PR is merged, clean up".