Schpet Jjagent
schpet-jjagent is a Claude Code plugin for the Build phase that hooks Claude Code sessions into jj-vcs so each run becomes trackable changes.
by schpet · github.com/schpet/jjagent
Install when you use jj (Jujutsu) VCS and want every Claude Code session captured as reviewable, reversible changes instead of a messy working tree.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install schpet-jjagent@schpet/jjagentBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:schpet/jjagent") and the paste-ready config with skillselion.get_install_config("plugin:schpet/jjagent").
What it does
schpet-jjagent is a Claude Code plugin that connects interactive agent sessions to Jujutsu (jj) version control by recording work as jj changes. Solo builders 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.
Highlights
- 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
Why builders use it
Agent sessions rewrite lots of files at once, and without VCS structure you cannot see what changed per session or roll back safely.
After setup, Claude Code sessions map into jj changes you can inspect, compare, and iterate on like normal development history.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 25 stars, 0 votes.
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.
Comments
Share how you use schpet-jjagent, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.