Xit (xit)

Rule (when to trigger)

Use xit instead of git when either is true:

• A .xit/ directory exists in this repo (including in a parent directory).
• The user explicitly asks for xit (e.g. “use xit”, “.xit repo”, “xit status”).

If the repo is not a xit repo and the user didn’t ask for xit, do not force this skill.

Non-interactive defaults

• Never run bare xit (it launches the TUI).
• Always use --cli for status, diff, diff-added, and log (their default is TUI).
• Avoid TUI entrypoints (e.g. xit config); use xit config list|add|rm ... instead.
• Prefer --cli whenever it’s available; check xit <cmd> --help if unsure.

Preflight

1. Confirm xit is available: command -v xit.
   • If missing, ask the user to install/provide xit.
   • If they decline, do not attempt to “fake it” with git; ask how they want to proceed.