Menú
Multi-package project orchestrator — git (status, diff, commit, push, pull, check), Dart/Flutter test, analyze, stats, pub get/upgrade
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional 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).
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.
Run tests and/or analysis across Dart/Flutter workspace packages and fix failures
| name | glittering |
| description | Multi-package project orchestrator — git (status, diff, commit, push, pull, check), Dart/Flutter test, analyze, stats, pub get/upgrade |
Go binary for multi-package Dart/Flutter workspaces — git operations across parent + submodules, test/analyze, dependency management. JSON to stdout, logs to stderr. Quiet by default; add --verbose/-v for progress output.
Source: ~/nixfiles/scripts/glitter/
glittering status --path <root> [--filter <names>] # package list (type, tests, deps)
glittering test --path <root> [--filter <names>] [--timeout 60] # run tests (parallel, cached)
glittering analyze --path <root> [--filter <names>] # dart analyze (parallel, cached)
glittering stats --path <root> [--filter <names>] [--threshold 200] # file/line counts, oversized detection (cached)
glittering get --path <root> [--filter <names>] # pub get all packages
glittering upgrade --path <root> [--filter <names>] # pub upgrade all packages
glittering clean # remove old session dirs
glittering git --path <root> [--filter <names>] # fetch + status
glittering git --path <root> --skip-fetch [--filter <names>] # status without fetching
glittering git --path <root> --cached [--filter <names>] # read cached status (instant)
glittering git check --path <root> [--cached] [--filter <names>] # verify committed/pushed
glittering git push --path <root> [--filter <names>] # push repos with unpushed
glittering git diff --path <root> [--staged] [--filter <names>] # diff summary
glittering git commit <sub>... -m "msg" --path <root> [--all | -f file | --staged] [--no-parent] [--parent-only] [--parent-message "msg"]
# Stage with --all (all changes), -f <file> (specific files), or --staged (use the index as-is).
# One of these is required unless something is already staged — a bare commit with no flag
# and an empty index errors with "nothing staged in <sub>".
glittering git pull --path <root> [--filter <names>] # pull parent + subs
--path (e.g. --path /Users/jimmyff/Projects/foo/workspace). Relative paths like --path . can resolve incorrectly across repeated tool invocations due to CWD shifts--filter uses substring matching: --filter blog matches packages/bloggit commit auto-resolves short names: git_dart → packages/git_dartgit commit over raw git commit / git push — it auto-pushes and keeps parent refs in sync--no-parent to skip parent update, --parent-only for parent-only modegit push --filter <sub> and bump the parent ref with git commit --parent-only. --filter skips the parent-dirty pre-flight, so a pending parent ref bump won't block the submodule push--cached for instant reads from last live runhead/tail/truncate glittering output — it's already summarised JSON; truncating breaks parsingglittering <command> --help for flag details{ packages: [{ path, status, details_file, ... }], summary } — read details_file for details{ threshold, packages: [{ path, source_files, source_lines, test_files, test_lines, oversized_count, details_file }], summary }{ repo: { branch, dirty, ahead_remote, ... }, submodules: [{ ..., ahead_parent, behind_parent }] }{ clean: bool, issues: [{ repo, severity, type, message, fix }], summary }{ repos: [{ path, staged, unstaged, untracked_files, details_file }], summary }{ success, submodules: [{ path, ref, pushed }], parent: { ref, staged, pushed, warnings } }{ branch, submodules: [{ path, new_commits, was_dirty }], warnings }dart test path/to/test.dartdart fix/format/run, flutter build/create/runglitter)Human-friendly formatted tables. Same commands plus glitter overview and glitter recache.
/glitterfix — automated test/analysis fixing workflow/submodules — git submodule commit/sync/verify workflows