Git Jev Stage

---
name: git-jev-stage
description: Stage Git changes selected by a plain-language description, with git jev-stage. Use when asked to commit or stage part of the working tree ("commit just the auth fix", "stage only the tests", "leave the debug logging out").
allowed-tools: Bash(git jev-stage *) Bash(git-jev-stage *) Bash(git status *) Bash(git diff *) Bash(git commit *) Bash(git add *)
---

`git jev-stage "<sentence>"` asks Jev to classify unstaged hunks that fit the token budget. In interactive mode, it stages selected hunks after confirmation, with separate questions for `mixed` decisions. With `--yes`, it stages accepted `include` decisions and leaves `mixed` hunks unstaged. It only stages: working files stay untouched, and the commit and its message are left to the caller.

Jev selection requires a TypeSafe early-access waitlist key. Get one at [typesafe.ai](https://typesafe.ai).

## Steps

1. Run the plan in machine mode:

   ```
   git jev-stage "<what to stage>" --json --yes
   ```

   Pair `--yes` with `--json` so the result is machine-readable and the `include` hunks are staged; without `--yes`, `--json` returns the plan with `applied: false` and stages nothing.

   Add `--exclude "<what to leave out>"` to give Jev explicit out-of-scope context. Verify those changes remain unstaged.

2. Read the JSON. `applied: true` means the `include` hunks are now in the index. `mixedHunkIds` lists hunks the tool did not stage because Jev chose `mixed`, confidence was below the threshold, an answer was missing or malformed, or a hunk was too large to send.

3. If `mixedHunkIds` is non-empty, decide each one: read the hunk under `files[].hunks[]` (its `header` and `text`), then stage the whole hunk with `git add -p` if it belongs, or leave it. Never edit the working tree to split a hunk.

4. Confirm with `git diff --cached --stat`, then commit.

## Failure modes

- Exit 1 with `missing-api-key`: `TYPESAFE_API_KEY` is not set. `--yes` and `--json` need a key. An interactive run without one asks about every hunk, and `--dry-run` by itself marks every hunk as `mixed` and prints no patch. In an agent session, fall back to `git add -p`.
- Exit 3 with `stale-snapshot` or `index-locked`: the tracked working-tree diff, index, or HEAD changed while planning, or another git process holds the index. Nothing was staged. Run the command again.
- Exit 1 with `unsupported-entry`: binary, symlink, or submodule changes are present. Stage those by path with `git add` first, or stash them, then rerun.
- Paths printed as `skipped` are mode-only or empty-file changes. They cannot be staged by hunk; stage them with `git add`.

## Do not

- Do not run `--json` without `--yes` when the intent is to stage. Nothing is staged.
- Do not describe the whole diff. Describe the wanted change in one sentence, then verify `git diff --cached` before committing.