jj
Skill1 starsChanged 50 days agoMITView on GitHub
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.
- Commits and pushes
In this repository113 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ac-ideateSkill
- ac-listSkill
- ac-roadmapSkill
- agentbridge-mcpSkill
- almanacSkill
- almquist-shellSkill
- ansible-fleetSkill
- apfsSkill
- apple-siliconSkill
- arena-actorsSkill
- asustor-nasSkill
- a-teamSkill
- atem-miniSkill
- at-tuiSkill
- autoresearchSkill
- babysitSkill
- bonzibuddySkill
- bop-brainstormSkill
- bop-catalogSkill
- bop-onSkill
- bop-teamSkill
- bop-workflowSkill
- bsd-portabilitySkill
- code-refactoringSkill
- codex-personasSkill
- context-graphSkill
- councilSkill
- datadog-backupSkill
- dd-tagsSkill
- delegateSkill
- deming-pdsaSkill
- deterministic-replaySkill
- dispatch-nuSkill
- durable-commitSkill
- elixir-gastown-opsSkill
- ergo-ircSkill
- esp32-tang-bridgeSkill
- fleet-evalSkill
- fleet-ircSkill
- freebsd-build-vmSkill
- freebsd-piSkill
- freebsdSkill
- ganttSkill
- gastown-opsSkill
- gastown-slingSkill
- gh-authSkill
- gitea-releaseSkill
- gitea-runnerSkill
- henshuSkill
- irclaw-cluster-opsSkill
- irclaw-research-teamSkill
- irc-taskSkill
- jail-factorySkill
- jobcard-systemSkill
- kubernetesSkill
- leptosSkill
- loreSkill
- lower-bound-reviewSkill
- macvlan-netSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 68
No staging area: All file changes in the working directory are automatically part of the current change (@).
- Very specific: line 72
jj newmoves forward: After describing a change, jj new creates a new empty commit on top. - Distinctive: line 80
When running as a dispatched agent in a jj workspace:
- Distinctive: line 96
Do NOT try to push to origin yourself.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
jj (Jujutsu) VCS Cheatsheet
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 (@).
Core Concepts
| 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 |
Daily Workflow
# 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 changeWorkspaces (multi-agent isolation)
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-workspaceRevsets (query language)
jj log -r 'main..@' # commits between main and current
jj log -r '@-' # parent of current
jj log -r 'description("fix")' # commits containing "fix"Key Differences from Git
- No staging area. All file changes in the working directory are automatically part of the current change (
@). - Commits are mutable.
jj describeedits the current commit's message without creating a new one. jj newmoves forward. After describing a change,jj newcreates 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.
In the bop context
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.
Common Mistakes
- ❌
git add && git commit— doesn't work, changes won't be recorded as jj commits - ❌
git push— usejj git pushif needed, but the merge-gate handles this - ❌
jj squashbefore done — squash flattens into parent, reserve for cleanup - ✅
jj statusto see current state - ✅
jj describe -m "..."+jj newto commit and move on
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.