detect-jujutsu

Detect Jujutsu or Git repositories and select the appropriate VCS workflow.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/lhohan/agentfiles --skill detect-jujutsu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: detect-jujutsu
Source: https://github.com/lhohan/agentfiles/tree/main/agents/dotagents/.agents/skills/detect-jujutsu
Command: npx skills add https://github.com/lhohan/agentfiles --skill detect-jujutsu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill guides agents to automatically detect whether the current repository uses Jujutsu (jj) or Git and choose the most appropriate VCS workflow for the session.

Core Features & Use Cases

  • Detection ladder checks for jj availability and repo state.
  • Authoritative fallback to Git when JJ is not suitable or detectable.
  • Invokes use-jujutsu guidance when JJ is confirmed to ensure JJ-based workflows are used.

Quick Start

Run the detect-jujutsu workflow at session start to determine whether JJ should be used for VCS.

Frequently Asked Questions about detect-jujutsu

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

FAQPage Schema
How do I detect if a repository uses Jujutsu or Git for version control?

To detect version control usage, the system checks for jj availability in PATH and the presence of a .jj directory, falling back to Git when Jujutsu is not found. This ensures the appropriate VCS workflow is selected for the session.

When should I run version control detection for my development workflow?

Version control detection should be run at session start or before executing VCS actions. This timing allows the system to identify the repository state and guide whether Jujutsu or Git workflows should be applied across mixed-workflow environments.

Does the detection workflow fall back to Git if Jujutsu is not available?

Yes, the detection workflow authoritatively falls back to Git when Jujutsu is not suitable or detectable. It relies on PATH checks for jj and the presence of a .jj directory before defaulting to standard Git version control operations.

What happens when Jujutsu is detected in a repository?

When Jujutsu is detected, the workflow communicates a recommended action via the 'use-jujutsu' instruction. This ensures that jj-based version control workflows are utilized for subsequent development operations within that specific repository.

Can I use this detection logic in mixed-workflow environments with multiple repositories?

Yes, the detection logic is specifically designed to guide version-control usage across development projects and mixed-workflow environments. It evaluates each repository individually to determine the correct VCS workflow selection.