retrieve-diff-from-commit
Retrieve Diff from Commit Skill
An input skill that retrieves code diff from local git commits. This is the entry point for reviewing local changes before they are pushed.
Role
- Extract: Get the diff content from a specific commit or range of commits
- Format: Prepare the diff in a format suitable for code review
- Context: Gather commit metadata (author, message, timestamp)
Inputs
| Input | Required | Description |
|---|---|---|
commit_sha |
Optional | Specific commit SHA to review (defaults to HEAD) |
commit_range |
Optional | Range of commits (e.g., main..HEAD, HEAD~3..HEAD) |
base_branch |
Optional | Compare current branch against base (e.g., main, develop) |
Outputs
More from xinbenlv/codereview-skills
codereview-architect
Deep codebase context analysis like Greptile. Analyzes blast radius of changes, dependency graphs, and architectural consistency. Use when reviewing changes to core utilities, shared libraries, or database models.
18codereview-correctness
Analyze code for logic bugs, error handling issues, and edge cases. Detects off-by-one errors, null handling, race conditions, and incorrect error paths. Use when reviewing core business logic or complex algorithms.
4codereview-api
Review API contracts, breaking changes, and interface consistency. Analyzes REST/RPC endpoints, event schemas, versioning, and backward compatibility. Use when reviewing public interfaces, API routes, or service contracts.
2general-codereview
Perform thorough code reviews following Google's 5-step methodology. Use when reviewing pull requests, change lists, or any code changes to ensure quality, correctness, and maintainability.
2codereview-testing
Review test coverage and quality. Analyzes unit tests, integration tests, determinism, and test design. Use when reviewing test files or code that should have tests.
2codereview-style
Review code style, maintainability, and documentation. Checks readability, naming, modularity, abstractions, and documentation accuracy. Use as a final pass on all files.
1