just-vibeGit · inspect by default
/git-status
Explain branches, staged changes, unstaged changes, and repository state
Use to explain repository state; git-diff explains actual content changes.
Make it your own.
In Claude Code, use the slash command and add your context. In Codex, select git-status from the just-vibe skill picker, then send the same brief.
Version 0.11.0 also supports /jv git-status, /just-vibe git-status and /jv:git-status in Claude. See shortcut setup and context examples.
/just-vibe:git-status Explain staged, unstaged, untracked, and interrupted-operation state here./just-vibe:git-status Explain a detached HEAD with an interrupted rebase and dirty files./just-vibe:git-status Inspect a directory that is not a Git repository; do not initialize it.What the agent does
- Read status --porcelain=v2 --branch and resolved refs with GIT_OPTIONAL_LOCKS=0 where supported; inspect worktrees and merge/rebase/bisect operation markers without changing them.
- Distinguish staged, unstaged and untracked changes and explain the relevant next action.
Inputs
- repository and optional concern such as divergence or interrupted operation.
Optional context: scope, references, constraints, successCriteria, environment, mode, budget.
Scope
- Reads
- HEAD, branches, worktrees, index, working tree, and known remote tracking state.
- Writes
- No source changes in inspect/plan. Save only requested planning artifacts. A separately requested repair uses the relevant implementation workflow.
- Mode
- Inspect; repository and optional concern such as divergence or interrupted operation.
- Prerequisites
- Git, exact repository/worktree, and readable refs/index. Record branch, HEAD, staged/unstaged/untracked state before mutation. Preserve unrelated edits and never default to broad staging, hard reset, clean, force push, or history rewriting.
Expected output
- Branch/HEAD, staged/unstaged/untracked state and any operation in progress, with explicit local-versus-last-fetched remote evidence and the safe next action.
How the work is checked
- A detached HEAD is explained; stale remote tracking refs are not described as live server status.
When to stop or clarify
- No fetch or cleanup implicitly. An unresolved repository path prevents mutation advice tied to a guessed repository.
Handling missing context
- Infer
- Read repository root, HEAD, branch, refs and staged/unstaged/untracked distinctions; use the configured human identity.
- Assume
- Limit an ambiguous inspection to the current repository and report that scope; preserve all existing changes.
- Ask
- Before mutation, resolve uncertain commit membership, destination ref or history-rewrite intent; do not ask again about already authorized exact actions.
Technical guidance
- Evidence
- Inspect HEAD, branch, porcelain status, index, worktree, untracked paths and merge/rebase state with optional locks disabled.
- Method
- Explain HEAD-to-index separately from index-to-worktree and use last-fetched refs explicitly.
- Pitfall
- Clean tracked files do not imply no untracked work; ahead/behind may use stale remote observations.
- Check
- Reconcile every reported change category with the correct tree comparison without fetching or modifying the index.
Situational decisions
When upstream tracking refs are stale or absent: Describe local facts and unknown remote state without fetching implicitly.
The coding agent follows this workflow using its available tools. Installation does not grant service access or guarantee an outcome. Read the compatibility notes.