Review Local Changes
Skill Verified ActiveComprehensive review of local uncommitted changes using specialized agents with code improvement suggestions
To provide developers with a thorough, automated code review of their uncommitted changes before they are committed, ensuring higher code quality and identifying potential issues early in the development cycle.
Features
- Comprehensive review of local uncommitted changes
- Utilizes specialized agents for different review aspects
- Configurable impact filtering for issues
- Provides code improvement suggestions
- Supports both staged and unstaged changes
- Outputs results in markdown or JSON
Use Cases
- Reviewing code before committing to catch bugs and style issues.
- Ensuring adherence to project guidelines and best practices.
- Identifying potential security vulnerabilities in new code.
- Getting actionable suggestions for code simplification and refactoring.
Non-Goals
- Reviewing committed code or pull requests.
- Replacing automated CI/CD checks (e.g., linters, unit tests).
- Performing syntactic compilation or running the code.
- Enforcing project-specific rules not covered by general code quality principles.
Installation
First, add the marketplace
/plugin marketplace add NeoLabHQ/context-engineering-kit/plugin install review@context-engineering-kitQuality Score
VerifiedTrust Signals
Similar Extensions
Project Session Manager
100Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions
Oh My Claudecode
100Process-first advisor routing for Claude, Codex, or Gemini via `omc ask`, with artifact capture and no raw CLI assembly
ClawSweeper Skill
100Use for all ClawSweeper work: OpenClaw issue/PR sweep reports, commit-review reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed autofix/automerge, GitHub Actions monitoring, permissions, gates, and manual backfills.
Karpathy Coder
100Use when writing, reviewing, or committing code to enforce Karpathy's 4 coding principles — surface assumptions before coding, keep it simple, make surgical changes, define verifiable goals. Triggers on "review my diff", "check complexity", "am I overcomplicating this", "karpathy check", "before I commit", or any code quality concern where the LLM might be overcoding.
Create Pull Request
99Create and manage pull requests using GitHub CLI. Covers branch preparation, writing PR titles and descriptions, creating PRs, handling review feedback, and merge/cleanup workflows. Use when proposing changes from a feature or fix branch for review, merging completed work into the main branch, requesting code review from collaborators, or documenting the purpose and scope of a set of changes.
Git Commit
99Create a git commit with a good message. Use when the user says "commit", "save changes", "commit this", or asks to create a commit after making code changes.