jj

Automate mainline-focused development workflows with jj for consistent commits and synchronization.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/mgreenly/ikigai --skill jj-mgreenly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jj
Source: https://github.com/mgreenly/ikigai/tree/main/.claude/library/jj
Command: npx skills add https://github.com/mgreenly/ikigai --skill jj-mgreenly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

jj provides a compact, deterministic set of commands and rules to manage a mainline-focused development workflow, eliminating ambiguity in how changes are introduced and synchronized across the team.

Core Features & Use Cases

  • Enforce mainline-oriented development with clear fetch/new/rebase flows
  • Quick, reproducible commits and pushes directly to main
  • Use Case: A solo developer or small team wants to ensure all changes land on main cleanly without feature branches

Quick Start

Initialize a fresh main workflow with jj and begin work according to the mainline rules.

Frequently Asked Questions about jj

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

FAQPage Schema
What is a mainline-focused development workflow without feature branches?

A mainline-focused development workflow routes all commits directly to the main branch, eliminating feature branches. It provides a deterministic set of commands to manage changes and synchronize remote state cleanly for solo or small team projects.

How do I commit and push changes directly to the main branch?

You can commit and push directly to main using a deterministic sequence of fetch, new, and rebase commands. This workflow automates local and remote synchronization to ensure changes land on the mainline cleanly.

Can I use jj for version control in a small team setting?

Yes, jj supports solo developers and small teams needing direct mainline commits. It enforces explicit rules and recovery steps to manage local and remote state across git-based repositories without feature branches.

Does this mainline workflow work with existing git repositories?

Yes, this workflow applies across git-based repositories. It automates mainline commits and synchronization using jj, providing consistent rules to manage local and remote state within your existing version control setup.

When should I avoid a direct mainline commit workflow?

You should avoid a direct mainline commit workflow if your project requires strict feature branch isolation for large scale changes. This approach is designed for solo projects or small teams that do not need feature branches.