菜单
Split unrelated changes within a single file into separate jj (Jujutsu) commits. Use only when the user explicitly asks — git is the default workflow. Trigger on "split this file into commits with jj", "/jj-split-file-for-commit <file>". Argument: the file to split.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | jj-split-file-for-commit |
| description | Split unrelated changes within a single file into separate jj (Jujutsu) commits. Use only when the user explicitly asks — git is the default workflow. Trigger on "split this file into commits with jj", "/jj-split-file-for-commit <file>". Argument: the file to split. |
| version | 0.1.0 |
| allowed-tools | Bash(jj status:*), Bash(jj diff:*), Bash(jj restore:*), Bash(jj commit:*), Bash(jj describe:*), Bash(jj log:*), Read, Edit |
jj status first.Split unrelated changes in one file into separate logical commits.
Analyze the changes
jj diff --git <file> to see all changes in the fileSave the target state
For each logical group:
jj restore --from @- <file> - reset file to parent versionjj commit -m '<type>: <description>' - commit this groupVerify final state
File has: typo fix + new function + reformatting
# Step 1: See changes
jj diff --git src/utils.ts
# Step 2: Save current content (using Read tool)
# Step 3a: First commit - typo fix
jj restore --from @- src/utils.ts
# Edit: apply only typo fix
jj commit -m 'fix: correct typo in error message'
# Step 3b: Second commit - new function
jj restore --from @- src/utils.ts
# Edit: apply only new function
jj commit -m 'feat: add validateInput helper'
# Step 3c: Third commit - reformatting
jj restore --from @- src/utils.ts
# Edit: apply reformatting
jj commit -m 'refactor: reformat utils module'
# Step 4: Verify final content matches saved target
jj undo to revert and try againfeat:, fix:, refactor:, etc.)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.
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".
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".