메뉴
Use when working in a jj (Jujutsu) repository. Covers the core workflow, workspace management, and common operations. jj is a newer VCS — do not assume git commands work here.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Almanac reference for dates, holidays, time zones, business days, and astronomical events. Use when checking if a date is a business day, calculating date differences, converting time zones, looking up holidays, or checking for astronomical events like solstices, equinoxes, and moon phases. Also for seasonal calculations, workday schedules, and calendar arithmetic.
Toyota Production System (TPS) and Toyota Way for software engineering — lean thinking, waste elimination, root cause analysis, and continuous improvement. Use when identifying waste (muda/muri/mura), running blameless postmortems, doing 5 Whys, writing A3 problem statements, or connecting lean philosophy to TRIZ contradiction resolution.
Local multilingual translation via Ollama — 119 languages, no API key, no network, no data leaves the machine. Use when translating to/from Japanese, Chinese, Korean, French, Spanish, German, Portuguese, Russian, Arabic, or any other language. Also for localization, i18n text, and roundtrip validation. Qwen3:32b on Apple Silicon — faster and cheaper than cloud APIs.
TRIZ contradiction matrix oracle for software and systems design. Use when improving one quality worsens another — speed vs correctness, isolation vs sharing, autonomy vs control, simplicity vs completeness. Trigger phrases: "tradeoff", "tension between", "can't have both", "worsens when", "at the cost of", "faster but less reliable", "more isolated but harder to share". Not for bugs, merge conflicts, or tool choices. Prerequisite: triz binary must be installed (run `triz doctor` to verify).
Deploy and manage software on Linux/BSD fleet hosts (Pis, NAS, workstations) via Ansible. Use when user mentions deploy, ansible, fleet, hosts, inventory, or deployment.
Use when operating, debugging, or deploying the elixir-gastown Elixir/BEAM fleet — cluster federation, release builds, worker deploys, seccomp fixes, sname/name distribution issues, rate limiter, or any gastown service on Pi workers or coordinator nodes.
| name | jj |
| description | Use when working in a jj (Jujutsu) repository. Covers the core workflow, workspace management, and common operations. jj is a newer VCS — do not assume git commands work here. |
jj is a Git-compatible VCS with a different mental model. Every change is always
a commit — there is no staging area. The working copy IS a commit (@).
| git concept | jj equivalent |
|---|---|
| staged changes | doesn't exist — edits are auto-tracked |
git commit | jj describe -m "msg" + jj new |
git status | jj status |
git log | jj log |
git diff | jj diff |
git checkout <branch> | jj edit <rev> |
git branch | jj branch list |
| worktree | jj workspace |
# See what changed
jj status
jj diff
# Commit the current working copy change
jj describe -m "feat: add shell completions"
jj new # creates a new empty change on top
# One-liner equivalent
jj commit -m "feat: add shell completions"
# View history
jj log
jj log -r '::@' # ancestors of current change
jj workspaces are like git worktrees but tracked in .jj/:
# List workspaces
jj workspace list
# Add a workspace (creates a directory with its own working copy)
jj workspace add ../my-feature-workspace
# Forget (remove) a workspace when done
jj workspace forget my-feature-workspace
jj log -r 'main..@' # commits between main and current
jj log -r '@-' # parent of current
jj log -r 'description("fix")' # commits containing "fix"
No staging area. All file changes in the working directory are automatically part of the current change (@).
Commits are mutable. jj describe edits the current commit's message without creating a new one.
jj new moves forward. After describing a change, jj new creates a new empty commit on top. This is the equivalent of "I'm done with this commit, start a new one."
@ is always a commit. The working copy is always represented as a commit, even when empty.
Branches are optional. jj uses anonymous commits; branches are just named pointers.
When running as a dispatched agent in a jj workspace:
# Check you're in the right workspace
jj workspace list
# Make your changes (edit files normally)
# Then commit:
jj describe -m "feat: what I implemented"
jj new
# Verify your commit is recorded
jj log -r 'main..@-'
The merge-gate will squash and push your changes to main via jj squash.
Do NOT try to push to origin yourself.
git add && git commit — doesn't work, changes won't be recorded as jj commitsgit push — use jj git push if needed, but the merge-gate handles thisjj squash before done — squash flattens into parent, reserve for cleanupjj status to see current statejj describe -m "..." + jj new to commit and move on