Schpet Jjagent
- 26 repo stars
- Updated January 30, 2026
- schpet/jjagent
schpet-jjagent is a Claude Code plugin that hooks Claude Code sessions into jj-vcs so each run becomes trackable changes.
About
schpet-jjagent is a Claude Code plugin that connects interactive agent sessions to Jujutsu (jj) version control by recording work as jj changes. developers who already chose jj over classic git get a clearer ledger of what Claude changed in each session, which matters when agents batch edits across a repo. The catalog description is narrow—track Claude Code sessions as jj-vcs changes—with keywords around hooks and setup, signaling install-and-wire rather than a large skill library. That makes it phase-specific build tooling for project management and traceability, with payoff when you iterate or undo agent mistakes. Complexity is intermediate: you need jj fluency and Claude Code hook configuration. It does not replace code review or testing; it makes agent output easier to navigate in a modern VCS. Ideal when you treat each agent run like a mini branch you might squash, split, or abandon.
- Tracks Claude Code sessions as first-class jj-vcs changes
- Hooks-based integration (setup and jjagent keywords in catalog)
- 1 plugin in the schpet/jjagent repository
- Pairs agent-assisted coding with Jujutsu’s change-oriented history model
- Improves revert and inspect workflows when agents touch many files per session
Schpet Jjagent by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin install schpet-jjagent@schpet/jjagentAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 26 |
|---|---|
| Last updated | January 30, 2026 |
| Repository | schpet/jjagent ↗ |
What it does
Install when you use jj (Jujutsu) VCS and want every Claude Code session captured as reviewable, reversible changes instead of a messy working tree.
Who is it for?
Best when you're on Jujutsu and live in Claude Code and want session-level accountability without manual commits after every prompt.
Skip if: Skip if you're on git-only workflows with no jj adoption, or developers and do not use Claude Code hooks.
What you get
After setup, Claude Code sessions map into jj changes you can inspect, compare, and iterate on like normal development history.
- jjagent plugin wired via Claude Code hooks
- Per-session jj changes representing agent work
- Inspectable VCS history for undo and iteration on agent edits
By the numbers
- 1 plugin in the bundle (pluginCount: 1)
- Repository: schpet/jjagent
- 25 GitHub stars on the catalog snapshot
Recommended Plugins
0xbigboss Linear CliLinear CLI built with Zig1
15195999826 LomomarketplaceLomo's Claude Code Plugin Marketplace1
1broseidon MarketplaceCurated collection of Claude Code plugins for fullstack development teams1
4rgon4ut Cc Zig LspZig LSP plugin for Claude Code4
708u TwigSimplify git worktree and branch management with configurable symlinks, change carrying, and cleanup.22
8avalon8 AvalonclaudemarketAvalon 的 Claude Code 插件市场How it compares
jj session-tracking hooks plugin, not a testing skill or deployment MCP server.
FAQ
Who is Schpet Jjagent for?
It is for developers who use jj-vcs and Claude Code and want automatic session-to-change tracking instead of hand-rolling commits after agent runs.
When should I use Schpet Jjagent?
Use it during active build and iterate cycles whenever Claude Code edits your repo and you need jj history that reflects each session boundary.
How do I add Schpet Jjagent to my agent?
Install the schpet/jjagent Claude Code plugin, complete jjagent hook setup per the repository docs, and run Claude Code in a jj-managed workspace.