status · carlrannaberg — Claude Code command: what it does, how to install
status evaluates repository state via Git, categorizes modified files by type, and suggests actions before commits or rebases.
MIT ★ 763 updated 2026-03-31
.claude/commands/git-status.mdWhat status does
The command bundles multiple Git queries into a single chained Bash execution separated by --- markers. It collects git status, git diff --stat, upstream branch tracking data, the latest commit summary, and cached diffs in one step.
Output appears directly without conversational filler. Changes get organized into categories like code, docs, tests, and configuration. The summary highlights uncommitted work, remote tracking drift, and stashed edits. When merge conflicts or complex repository states appear, the command directs the agent to invoke the git-expert subagent using the Task tool.
Execution fails if the environment denies permission for Bash(git:*).
What it helps with
- group uncommitted files into code, tests, docs, and configs
- verify synchronization against the upstream tracking branch
- check whether working tree state is clean enough for a rebase
- spot edits that should be split across distinct commits
Example prompts for the agent
- Run
/git-statusto inspect pending changes - Use
/git-statusbefore staging files for a commit
How to install status
Manually: put the files in place
.claude/commands/git-status.mdThe built-in /status overrides a file with the same name, so the file is renamed. Call it with /git-status. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/status.mdCall it with /prompts:status. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/status.prompt.mdManually: put the files in place
.gemini/commands/status.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about status
How to install status in Claude Code?
Save the command prompt file at .claude/commands/git-status.md.
What does the status command do?
It runs git inspection commands in a single batch call, sorting modified files by role and suggesting commit strategies without chatty preamble.
When does the command call the git-expert subagent?
It routes merge conflicts and repository anomalies to the git-expert subagent via the Task tool.
Source text
status.md · MIT
--- description: Intelligently analyze git status and provide insights about current project state category: workflow allowed-tools: Bash(git:*), Task --- Analyze the current git status and provide an intelligent summary of what's happening in the project. ## Git Expert Integration For complex git analysis scenarios (merge conflicts, complex branch states, repository issues), consider using the Task tool with `git-expert` subagent for specialized git expertise. ## Efficiency Note: Be concise. Skip verbose explanations of what commands you're running. Focus on the actual status results. ## Instructions for Claude: 1. Run all git commands in a single bash call for speed: !git status --porcelain=v1 && echo "---" && git diff --stat 2>/dev/null && echo "---" && git branch -vv | grep "^\*" && echo "---" && git log --oneline -1 && echo "---" && git diff --cached --stat 2>/dev/null Note: The output will be separated by "---" markers. Parse each section accordingly. 3. Provide results directly without explaining the process: - **Summary**: Brief overview of the current state - **Modified Files**: Group by type (docs, code, tests, config) - **Uncommitted Changes**: What's been changed and why it might matter - **Branch Status**: Relationship to remote branch - **Suggestions**: What actions might be appropriate Provide insights about: - Whether changes appear related or should be separate commits - If any critical files are modified (package.json, config files, etc.) - Whether the working directory is clean for operations like rebasing - Any patterns in the modifications (e.g., all test files, all docs, etc.) - If there are stashed changes that might be forgotten Make the output concise but informative, focusing on what matters most to the developer. Example of concise output: - Skip: "I'll analyze the current git status for you." - Skip: "Let me gather the details efficiently:" - Skip: "I see there are changes. Let me gather the details:" - Just show the results directly
© carlrannaberg · MIT · carlrannaberg/claudekit
Similar slash commands
All slash commands for Git and GitHub →status by other authors comes first.