メニュー
Bring a multi-package workspace fully in sync when moving between machines — commit (with approval), push, pull, verify clean. State-driven; dirty repos trigger the commit ritual first. Command syntax lives in the glittering skill.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Dart/Flutter workspace orchestrator (multi-package, git submodules). Use proactively when working in any multi-package workspace — run tests/analysis across packages (parallel, cached), commit submodule work (auto-push + parent ref sync), check workspace-wide git state (status/diff/push/pull/check). Not for single-file tests, git branch surgery, or single-package repos.
Official Dart/Flutter MCP server (tools appear as mcp__dart__*). Use for the live-app runtime loop (launch, hot reload, runtime errors, screenshots, widget tree + driver interaction), pub.dev search, and grepping/reading dependency source. NOT for workspace-wide test/analyze/git — glittering stays the default there. If a project lacks .mcp.json, symlink the canonical one (~/nixfiles/dotfiles/ai/mcp.json) — never write a copy.
Comprehensively review an implementation plan or design doc — grounds every claim against the real codebase, critiques across correctness/architecture/risk/completeness lenses, adversarially verifies flaws, and returns a prioritized verdict with concrete fixes. Use when the user asks to review, critique, sanity-check, or find flaws in a plan file (e.g. "review this plan", "critique my plan at <path>", "is this plan sound?"). After reporting, it asks which items to apply, revises the plan, and emits a cold-start handoff brief to implement the revised plan in a fresh session. SKIP for authoring a new plan (that's plan mode) or reviewing code/PRs (use code-review).
Run tests and/or analysis across Dart/Flutter workspace packages and fix failures
Multi-package project orchestrator — git (status, diff, commit, push, pull, check), Dart/Flutter test, analyze, stats, pub get/upgrade
| name | gitsync |
| description | Bring a multi-package workspace fully in sync when moving between machines — commit (with approval), push, pull, verify clean. State-driven; dirty repos trigger the commit ritual first. Command syntax lives in the glittering skill. |
| disable-model-invocation | true |
| effort | medium |
One ritual for switching machines: run it when leaving (commits + pushes + pulls) and when arriving (pulls). It is state-driven — the dirty check decides what's needed, not the direction of travel. Mechanics defer to the /glittering skill; commit policy (staging gates, confirmations) to the global guidelines.
/gitsync [status] — no argument runs the full flow; status is orientation only, no changes.
glittering git --path <root> (live fetch, so ahead/behind is accurate). Summarise dirty repos, ahead/behind remote, parent ref drift.git pull skips dirty submodules, so pulling first would skip exactly the repos that need syncing):
glittering git diff --filter <sub>; group related changes into commitsglittering git commit (prefer -f selective staging over --all; -F for related parent files)glittering git commit --parent-only -f <file> -m "msg"partial/left_uncommitted means parent files still uncommitted; on failure, follow the hint fieldglittering git pull --path <root> — pulls parent, inits new submodules, checks out tracking branches, pulls each sub. Declined-WIP subs are skipped with warnings (expected — surface them). Merge conflicts: stop and ask.glittering git check --path <root>. Submodules ahead of the parent ref mean the remote moved past what the parent recorded — bump with glittering git commit --parent-only. No repo left in detached HEAD.git check reports clean (apart from deliberately kept WIP) — safe to switch machines.statusglittering git --path <root> (add --cached for instant). Summarise per repo: branch, dirty/clean, ahead/behind remote, ahead/behind parent ref, latest commit.