Slash Command828 estrellas del repoactualizado 13d ago

status

The status command displays the current git repository state in a formatted summary showing the active branch, staged changes, unstaged modifications, untracked files, and suggested next actions. Use this to quickly understand what changes exist in your working directory without parsing raw git output, particularly when managing multiple file changes across a project.

Ver fuente Repositorio: claude-code-engineering

Instalar en Claude Code

Copiar

mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/huangjia2019/claude-code-engineering/HEAD/05-Commands/projects/01-basic-commands/.claude/commands/git/status.md -o ~/.claude/commands/status.md

Después abre una sesión nueva de Claude Code; el slash command carga automáticamente.

Definición

status.md

Show the current git status with helpful context.

## Steps

1. Run `git status`
2. Summarize the state in a friendly format

## Output Format

```
## Git Status

Branch: [branch name]
State: [clean / has changes / has conflicts]

### Staged Changes (ready to commit)
- [files]

### Unstaged Changes (not staged)
- [files]

### Untracked Files
- [files]

### Suggested Next Steps
- [what you might want to do next]
```

If the repo is clean, just say:
```
✓ Working tree clean on branch [name]
```

Del mismo repositorio

code-reviewerSubagent

Review code changes for quality, security, and best practices. Proactively use this after code modifications.

test-runnerSubagent

Run tests and report results concisely. Use this after code changes to verify everything works.

log-analyzerSubagent

Analyze log files and extract actionable insights. Use when troubleshooting issues or investigating incidents.

api-explorerSubagent

Explore and analyze API-related code. Use when investigating endpoints, routing, or HTTP handling.

auth-explorerSubagent

Explore and analyze authentication-related code. Use when investigating auth flows, session management, or security.

db-explorerSubagent

Explore and analyze database-related code. Use when investigating data models, queries, or persistence.

bug-analyzerSubagent

Analyze root cause of bugs after location is identified. Second step in bug investigation.

bug-fixerSubagent

Implement bug fixes after analysis is complete. Third step in bug fix pipeline.