jj-lazyjj

Route version control operations through Jujutsu aliases when a .jj directory is detected.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/leodiegues/skills --skill jj-lazyjj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jj-lazyjj
Source: https://github.com/leodiegues/skills/tree/main/skills/jj-lazyjj
Command: npx skills add https://github.com/leodiegues/skills --skill jj-lazyjj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents broken workflows by ensuring version control in jj-managed repositories always goes through jj (never raw git) when a .jj directory is present.

Core Features & Use Cases

  • Enforced jj-only operations: A hard rule that forbids raw git commands (add/commit/push/pull/rebase/branch/checkout/stash/merge/status/diff/log/reset) when .jj exists, replacing them with correct jj or LazyJJ equivalents.
  • Deterministic workflow mapping: Clear “forbidden → replacement” guidance for common git intentions like committing, syncing, pushing, rebasing, diffing, and history inspection.
  • Workspace-first concurrency model: Directs non-trivial work into isolated jj workspaces (claude-start/stop/checkpoint) to avoid clobbering parallel agent sessions, including recovery for stale working copies.
  • Stack and forge-friendly pushing: Supports stacks (stack-start/sync/submit/gc) and pushes/bookmark patterns aligned with GitHub and GitLab forge workflows (including stacked PR patterns on GitHub).

Quick Start

Use the jj-lazyjj skill to perform a safe stacked push by running: jj stack-start, then make changes and finish with jj stack-submit.

Frequently Asked Questions about jj-lazyjj

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent using raw git commands in a jujutsu repository?

To prevent using raw git commands in a jujutsu repository, this skill enforces strict command substitution, automatically routing operations like committing, diffing, and rebasing through jj and LazyJJ aliases whenever a .jj directory is detected.

Can I use jj workspaces to isolate changes for parallel agent sessions?

Yes, you can use jj workspaces to isolate changes for parallel agent sessions. The skill directs non-trivial work into isolated workspaces using claude-start and claude-stop commands, preventing clobbering and includes recovery for stale working copies.

What is the best way to manage stacked PR workflows with jujutsu?

The best way to manage stacked PR workflows with jujutsu is using the built-in stack commands. The skill supports stack-start, sync, submit, and gc operations, aligning push and bookmark patterns directly with GitHub and GitLab forge workflows.

Does jujutsu still require git commands for remote syncing and pushing?

Jujutsu does not require raw git commands for remote syncing and pushing when using this skill. It strictly requires only jj git fetch, push, and remote commands for git interoperability, blocking standard git invocations like pull or branch.

How do I handle rebase and conflict resolution in jj without raw git?

To handle rebase and conflict resolution in jj without raw git, the skill provides deterministic workflow mapping. It replaces forbidden git intentions with correct jj or LazyJJ equivalents specifically for syncing, rebasing, and conflict handling.