timofreiberg/jj
agents/skills/jj/SKILL.md
Version control with jj (Jujutsu)
$ install --global
skillsauthnpx skillsauth add timofreiberg/dotfiles jjInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 10, 2026, 3:44 AM146.7s2 files scanned
SKILL.md
- name:
- jj
- description:
- Version control with jj (Jujutsu)
jj Command Reference
For flags and syntax details, run jj <subcommand> --help.
See reference.md for advanced topics (rewriting history, splitting commits, revsets).
Key Concepts
- Working copy (
@): The current change, automatically tracks file modifications. - Changes vs commits: A change has a stable change ID (short, letters only); a commit has a commit ID (hex). Prefer change IDs in commands.
- Immutable revisions: Commits on bookmarked/tagged/remote branches are immutable by default. Use
jj newto create a mutable change on top.
Squashing
NEVER run jj squash without -m "msg" or --use-destination-message. Bare jj squash opens an interactive editor and will hang.
Splitting Commits
Do not use jj split — it is interactive and will hang. See the
agent-friendly splitting methods
in the advanced reference.
File Tracking
jj file untrack <paths> stops tracking paths in the working copy. Paths must already be in .gitignore. Useful when files were accidentally committed before being ignored.
Undoing Operations
If a command puts the wrong changes into the wrong commit (e.g. squash into the wrong parent), don't try to manually fix the commits — revert the operation instead:
- Check the commit log:
jj log - Check the operation log:
jj op log - Revert the bad operation:
jj op revert <op_id>(the op ID is shown injj op log)
Related Skills
timofreiberg/web-search
development
VerifiedTrustedCommunity
Quick internet research via a web-search-enabled model. Returns summaries with source URLs.
2SKILL.mdUpdated May 11, 2026
timofreiberg/jj-workspaces
data-ai
VerifiedTrustedCommunity
Use when you want to work in an isolated jj working copy — parallel task, experimental scratch, subagent with its own tree. Covers creating a workspace, working inside it from anywhere, and cleaning up without losing history.
2SKILL.mdUpdated May 11, 2026
timofreiberg/extend-pi
tools
VerifiedTrustedCommunity
Use when working on the pi coding agent harness or writing pi extensions.
2SKILL.mdUpdated May 5, 2026
timofreiberg/writing-skills
testing
VerifiedTrustedCommunity
Use when creating, editing, or reviewing a skill before it ships. Covers when to write a skill, file layout, the SKILL.md shape, and how to verify it before relying on it.
2SKILL.mdUpdated Apr 28, 2026