jujutsulisted

Activates first on any git/VCS operation when Alyssa is in a Jujutsu (jj) repository — anywhere `.jj/` exists in the project tree. Use for commits, status, bookmarks, push, fetch, rebase, history rewriting, file tracking, and `.gitignore` changes. Especially trigger before creating new files, running builds, or editing `.gitignore`, since jj auto-snapshots everything and retroactive cleanup is expensive if not done right. Pinned to jj v0.43. Raw `git` commands in a non-colocated jj repo can corrupt state, so always reach for this skill first when she mentions jj, jujutsu, change IDs, revsets, bookmarks, or anything VCS-shaped in a jj repo — even if she just says "commit this" or "what's the status," because in a jj repo those words mean different operations.
alycda/dotfiles · ★ 1 · Code & Development · score 60

Install: claude install-skill alycda/dotfiles

# Jujutsu (jj) Skill Alyssa uses Jujutsu (jj) as her daily-driver VCS in colocated mode (both `.jj/` and `.git/` present). This skill teaches Claude to operate in jj repos without reaching for git muscle memory. **Pinned version:** jj v0.43. The canonical destination flag for `rebase`, `split`, and `revert` is `--onto`/`-o` (`--destination`/`-d` survives as an alias). Two flags older tutorials use are **gone** in v0.43: `jj git push --allow-new` (use `--named <name>=<rev>`) and `jj describe --edit`. See `references/version-notes.md` for the full delta. **Core principle:** jj's auto-snapshot behavior is a power tool. It captures every file in the working directory automatically — which means if Claude generates an artifact without checking `.gitignore` first, that artifact is now in version control. Retroactive cleanup is possible but expensive. The cheapest fix happens **before** the file gets tracked, not after. **Detection:** If `.jj/` exists in the project root (or any parent), this is a jj repo. Use jj commands. Do not fall back to `git` unless the repo is colocated AND you know what you're doing — see "Colocated Repos" below. --- ## Mental Model ### The working copy is a commit There is no staging area. There is no `jj add`. The working directory is always a commit, referenced as `@`. Every time Claude runs any jj command, jj snapshots the working copy first. New files appear automatically. Deleted files disappear automatically. There is no `git add`/`git rm` ste