smithery.ai

update-jj

Updates the jj-lib and jj-cli dependencies. Use when asked to update the jj version.

First seen Mar 29, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,474 B
  • docs SUMMARY.md 101 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

<background-information> GG (this project) depends on multiple crates from the JJ project. gg is primarily an alternative to jj-cli, so it uses a lot of jj-lib code; however, it also uses jj-cli directly in a few cases </background-information>

Updating crate versions =======================

  1. Modify Cargo.toml to update both jj-lib and jj-cli to the required version. This will either be a published version like version = "0.37.0" or a branch name like git = "https://github.com/jj-vcs/jj.git";, branch = "main".
  2. Run cargo update, which will update Cargo.lock.
  3. Use /cargo-dedupe to match other dependencies' versions.

Fixing breaking changes ======================= It's likely that jj API changes will require modifications to gg code. Make any necessary modifications, maintaining gg's current behaviour. For examples of how to use modified jj APIs, consult the source code at https://github.com/jj-vcs/jj - the jj-cli code (cli/ directory) often makes use of jj-lib code (lib/ directory) in similar ways to gg.

Verifying the update ==================

  1. Run cargo check - there should be no warnings or errors.
  2. Run cargo test - all tests should pass.
  3. If API changes have affected message structs in src/messages, use cargo gen to regenerate Typescript types and then npm run check to verify them.