What does the @ symbol mean in Jujutsu?

The @ symbol represents your current working copy commit. Unlike Git's HEAD, the working copy in jj is itself a commit that evolves as you make changes.

How do I see the history of my working copy?

You can use the 'jj evolog' command to see the evolution history of your current working copy commit (@), including all previous snapshots and amendments.

What is a Jujutsu working copy snapshot?

A snapshot is an automatic capture of your working directory state that Jujutsu performs before every command, ensuring your work is saved even if you haven't committed it.

Can I recover work I accidentally deleted?

Yes, because jj snapshots everything, you can use 'jj evolog --patch' to find the lost code and 'jj restore' to bring it back into your current workspace.

Jujutsu Working Copy Snapshots

Name: Jujutsu Working Copy Snapshots
Author: edmundmiller

byedmundmiller

•

Productividad y Flujo de Trabajo

Manages and recovers Jujutsu working copy snapshots to ensure data safety and track local development history.

Acerca de

This skill empowers Claude to navigate and manage Jujutsu's (jj) automatic snapshot system, providing a robust safety net for local development. It allows users to understand the '@' working copy commit, view the evolution of their changes through 'evolog', and recover lost work from previous operations. By leveraging Jujutsu's unique architecture, this skill helps developers manage unfinished work, configure auto-tracking patterns, and maintain a detailed history of their workspace without the need for manual intermediate commits.

Características Principales

Point-in-time recovery for uncommitted files and changes
Visualizing working copy history via evolution logs (evolog)
Configuration of auto-track patterns for specific file types
Seamless management of WIP (Work In Progress) across multiple commits
Automatic snapshot tracking for every jj command execution
40 GitHub stars

Casos de Uso

Configuring workspace rules to ignore scratch files while tracking source code
Recovering code deleted or overwritten during experimental development
Reviewing the step-by-step evolution of a feature before finalizing a commit

Acerca de

Características Principales

Point-in-time recovery for uncommitted files and changes
Visualizing working copy history via evolution logs (evolog)
Configuration of auto-track patterns for specific file types
Seamless management of WIP (Work In Progress) across multiple commits
Automatic snapshot tracking for every jj command execution
40 GitHub stars

Casos de Uso

Configuring workspace rules to ignore scratch files while tracking source code
Recovering code deleted or overwritten during experimental development
Reviewing the step-by-step evolution of a feature before finalizing a commit