# Context Review

> Use this skill to review code changes using semantic search to understand context and impact

- Skill: `jetbrains/context-review` (Agent Skill)
- Install (CLI): `npx skillmds@latest add jetbrains/context-review`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jetbrains/context-review/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: jetbrains (https://skillmd.com/u/jetbrains)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jetbrains/context-review

---


## When to Use

- Before committing changes to understand what you're about to commit
- Reviewing pull requests or branches
- Understanding the impact of changes on the rest of the codebase

## Review Workflow

### 1. Check Current Changes

First, see what's changed:

```bash
git status
git diff                    # Unstaged changes
git diff --staged           # Staged changes
git diff main...HEAD        # All changes on current branch
```

### 2. Understand Changed Code Context

For each significantly changed file, use semantic search to understand:

- **Similar patterns**: Find similar code elsewhere that might need the same change
- **Callers**: Find code that calls the modified functions
- **Dependencies**: Find code that the modified code depends on

```bash
# Find similar patterns
jbcontext search "<code chunk that was changed>"

# Find callers of a modified function
jbcontext search "calls to <function name> to understand impact"

# Find related test files in the "test/" directory (path must be relative to the project root)
jbcontext search -p test "tests for <feature being modified>"
```

### 3. Review Checklist

For each change, verify:

- [ ] The change is consistent with similar patterns in the codebase
- [ ] All callers of modified functions will still work correctly
- [ ] Related tests exist and cover the changes
- [ ] The change doesn't reintroduce previously fixed bugs

## Example Session

```bash
# See what's changed
git diff --staged

# For a change to auth middleware, find similar patterns
jbcontext search "authentication middleware pattern"

# Find what calls this middleware
jbcontext search "uses auth middleware to protect routes"

# Find related tests
jbcontext search -p test "auth middleware test"
```