log
The log command displays recent Git commit history in a formatted table, extracting the commit hash, message, author, and timestamp. Use this to quickly review project activity and understand what work has been completed recently, with a configurable number of commits to display and a summary highlighting commit patterns and focus areas.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/huangjia2019/claude-code-engineering/HEAD/05-Commands/projects/01-basic-commands/.claude/commands/git/log.md -o ~/.claude/commands/log.mdlog.md
Show recent git commit history. Number of commits: $ARGUMENTS (default: 5 if not specified) ## Steps 1. Run `git log --oneline -n [count]` 2. Provide a brief summary ## Output Format ``` ## Recent Commits | Hash | Message | Author | Time | |------|---------|--------|------| | abc123 | feat: add login | John | 2h ago | | def456 | fix: null check | Jane | 5h ago | ... ### Summary - Total: [n] commits shown - Most active: [most frequent commit type] - Recent focus: [what recent work seems to be about] ``` Keep it concise and scannable.
Review code changes for quality, security, and best practices. Proactively use this after code modifications.
Run tests and report results concisely. Use this after code changes to verify everything works.
Analyze log files and extract actionable insights. Use when troubleshooting issues or investigating incidents.
Explore and analyze API-related code. Use when investigating endpoints, routing, or HTTP handling.
Explore and analyze authentication-related code. Use when investigating auth flows, session management, or security.
Explore and analyze database-related code. Use when investigating data models, queries, or persistence.
Analyze root cause of bugs after location is identified. Second step in bug investigation.
Implement bug fixes after analysis is complete. Third step in bug fix pipeline.