菜单
Reduce a canvas document to its current-state meaning, letting spent rejected paths and process scaffolding fall into git history (recoverable via `git log -p -- <doc>`). Use when the user says "distill", "git-intent-distill", or "reduce the canvas".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | git-intent-distill |
| description | Reduce a canvas document to its current-state meaning, letting spent rejected paths and process scaffolding fall into git history (recoverable via `git log -p -- <doc>`). Use when the user says "distill", "git-intent-distill", or "reduce the canvas". |
| argument-hint | ["scope or instructions"] |
| allowed-tools | Bash(git *), Read, Edit, Write, Grep, Glob |
Distill compresses the document, not the history. git-intent writes the loop; git-intent-squash-archive collapses the commit stream; neither decides what text the canvas should still carry. Over a session the canvas accumulates rejected-path sections, resolved markers, and superseded caveats — the human wants to read current state, not the whole working record. Distill removes that accumulation into history: the doc converges to its meaning, every cut stays recoverable.
This is a forward commit, not a rewrite — lighter than squash-archive: no tag, no reset. The pre-distill version is git show HEAD^:<doc>. Run it whenever the canvas has drifted from lean, not only at finalization.
Remove only what history already holds. Every cut must be recoverable from git log -p -- <doc>, so the precondition is a clean tree — all work committed — or the parent commit won't hold the full pre-distill version and the removed content is gone, not archived. Run git status --porcelain; if non-empty, stop and ask the user to commit first (same guard as the sibling skills). Scope of the guarantee: git log -p -- <doc> on the working branch; after git-intent-squash-archive the recovery path becomes the archive/<branch> tag.
This is the skill; the mechanics below are secondary. Distill is not "delete every rejected path." A rejected section can be dead (its reasoning is spent) or protective (it stands in the doc to stop a future agent re-proposing the bad idea). Cutting protective text to history only helps a reader who checks git log before proposing — real discipline, not a guarantee. So weigh each candidate rather than sweeping.
Cut — dead process material:
!! / ??? / !!! markers and the scaffolding around them.Keep — live constraints:
## Open decisions and anything still unresolved: live, not dead.When a cut is judgment-heavy, do less: leaving a live constraint in costs a few lines; distilling one into archaeology costs a re-litigated decision. When you genuinely can't tell dead from protective, keep it and place a ??? asking the user.
$ARGUMENTS steers the operation and overrides the default taxonomy. It may set scope ("only the transport section"), aggressiveness ("keep all why-nots", "cut hard"), or name specific content to keep or drop. !! markers in the doc do the same in place. With no instruction, apply the taxonomy above conservatively.
git status --porcelain. Non-empty → stop, ask the user to commit or stash.$env.GI_CANVAS; if unset, ask which document.$ARGUMENTS / !! instructions. Anything genuinely ambiguous between dead and protective: keep it, add a ???./git-intent — the write-loop that produced the material being distilled./git-intent-squash-archive — finalization: collapse the branch (distill commits included) into one clean commit for main, full history preserved in a tag.Verify a cozy build by running `cozy verify` against a target you name — a locally-built docker container (default), a running sbx sandbox, or a host checkout. The checks live in cozy-module/verify.nu. Use when you say "verify the build", "build-check", "smoke test the sandbox", "is everything wired up", "/verify-cozy docker", after building the image, or after creating a sandbox.
This skill should be used when working alongside a user in a shared Nushell terminal (e.g. the cozy sandbox) — coaching Nushell in everyday tasks and practicing literate programming with numd (executable markdown), dotnu (.nu scripts that embed their own output as `# =>` comments), REPL capture, and claude-nu session archiving. It governs interaction style: build a common space where the user runs Nushell themselves and grows fluency, instead of the agent executing everything for them. Relevant when the user says "numd," "dotnu," "teach me," "show me how," "let me run it," "literate programming," "run the code blocks in this markdown," "update the embeds," "capture this session," "keep this doc in sync," "export this claude session," "self-updating README," or asks how to document, share, practice, or verify Nushell work.
Turn the current chat into a gi canvas, or open an existing one. Use when the user says "gi canvas", "start a canvas", "переведи в канвас", "продолжим в канвасе", "open the canvas", or asks to move this conversation into a canvas document.
This skill should be used when inspecting, querying, or rewriting the user's Nushell command history. Relevant when the user asks "what did I run", "show my recent commands", "what was I trying", "find commands I ran in <dir>", "remove these history entries", "move/retag these history entries to <path>", "fix the cwd on these rows", or when you need to understand what the user has been doing in a directory by looking at their shell history.
Cut a new release for the cozy project: finalize CHANGELOG.md, create a git tag, and summarize what to do next. Use when the user says "make a release", "cut a release", "release", "bump version", "tag a release", or "prepare release".
Re-vendor modules from upstream into cozy/vendor/ and prepare atomic commits grouped by repo. Use when the user says "vendor updated versions", "I vendored, commit", "nu toolkit/vendor.nu then commit", "refresh vendor", "bump vendored modules", or "vendor the latest, commit by groups".