xit

Translate git-like intents into xit CLI commands for .xit repositories.

66|2|Updated Feb 18, 2015
One-click install
npx skills add https://github.com/tkersey/dotfiles --skill xit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: xit
Source: https://github.com/tkersey/dotfiles/tree/main/codex/skills/xit
Command: npx skills add https://github.com/tkersey/dotfiles --skill xit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Xit provides a CLI alternative for repositories that use a .xit directory, allowing you to perform version-control tasks without the Git TUI, and it maps git-like intents to xit commands.

Core Features & Use Cases

  • Git-to-xit mapping: Translate common git operations (status, diff, add, commit, branch, switch) to their xit equivalents.
  • Non-TUI by default: Always use CLI commands and avoid interactive TUI entrypoints.
  • Preflight and safety: Verify that xit is installed and the repository is configured for xit before executing commands.
  • Use cases: Migrating a .git workflow in repos that now rely on .xit, performing routine version-control tasks with a xit-centric workflow.

Quick Start

Run xit status --cli in a repository that contains a .xit directory to see the current status without launching a TUI.

Frequently Asked Questions about xit

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

FAQPage Schema
How do I map Git commands to xit for version-control tasks in a CLI workflow?▼

To map Git commands to xit, this Skill translates git-like intents such as status, diff, add, and commit into their xit CLI equivalents for repositories configured with a .xit directory.

Can I run xit commands without launching an interactive Git TUI?▼

Yes, you can run xit commands without an interactive TUI by enforcing non-interactive CLI defaults, allowing you to execute version-control tasks directly from the command line.

What prerequisites are needed to use xit for branch management instead of Git?▼

To use xit for branch management, you must verify that xit is installed and that your repository contains a .xit directory before executing non-interactive CLI workflows.

Does the xit CLI workflow require confirmation before running destructive operations?▼

Yes, the xit CLI workflow requires explicit confirmation before executing destructive actions, ensuring safety during branch management and other version-control tasks.

What is the best way to migrate a Git workflow to a xit-centric repository?▼

To migrate a Git workflow to xit, use this Skill to map common Git operations to xit equivalents and run non-interactive commands in repositories containing a .xit directory.