xit_skill

Overview

This skill translates git-like intents into non-interactive xit CLI commands for repositories that use .xit. It prefers text-mode output (--cli) and avoids the xit TUI, providing safe mappings for status, diff, add, commit, branch, merge, cherry-pick, reset, and remote operations. It enforces preflight checks and explicit confirmations for destructive actions.

How this skill works

It first checks that the xit binary is available and that the current repository (or a parent) contains a .xit directory. For common git-style intents it emits equivalent xit commands, always using --cli for interactive commands that default to the TUI. It refuses to substitute git in a .xit repo unless the user explicitly asks and prompts before running destructive operations.

When to use it

• The repo contains a .xit/ directory (including parent directories).
• The user explicitly asks for xit or mentions ".xit" or “use xit”.
• You want non-interactive, agent-friendly command output (text mode).
• You need mappings for common git workflows but must avoid the TUI.

Best practices

• Always run command -v xit before executing; ask the user to install xit if missing.
• Prefer xit <cmd> --help when unsure whether a subcommand supports --cli.
• Never run bare xit (it opens the TUI). Use --cli for status, diff, diff-added, and log.
• Require explicit user confirmation for destructive commands (rm, restore, reset-dir, force push).
• Use xit untrack when user wants to stop tracking but keep files.

Example use cases

• Inspect changes: xit status --cli followed by xit diff --cli and xit diff-added --cli.
• Commit cycle: xit add <paths...>, xit diff-added --cli, xit commit -m "msg".
• Create or delete branches: xit branch add <name> and xit branch rm <name>.
• Merge or cherry-pick: xit merge <branch> or xit cherry-pick <oid>, then resolve conflicts, xit add <paths...>, xit merge --continue.
• Remote workflows: xit fetch <remote>, then xit merge refs/remotes/<remote>/<branch>; use xit push <remote> <branch> for upload.