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.
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.mdstatus.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] ```
Deep analysis of code against project standards
API design patterns and conventions for this project. Covers RESTful URL naming, response format standards, error handling, and authentication requirements. Use when writing or reviewing API endpoints, designing new APIs, or making decisions about request/response formats.
Generate comprehensive API documentation by scanning Express route files.
Generate API documentation from code. Use when the user wants to document APIs, create API reference, generate endpoint documentation, or needs help with OpenAPI/Swagger specs.
Explore and analyze API-related code. Use when investigating endpoints, routing, or HTTP handling.
Generate API endpoint documentation from Express route files. Use when the user asks to generate, update, or review API docs for Express.js routes.
Explore and analyze authentication-related code. Use when investigating auth flows, session management, or security.
Analyze root cause of bugs after location is identified. Second step in bug investigation.