vscode
VS Code integration for viewing diffs and comparing files. Use when showing file differences to the user.
When & Why to Use This Skill
This Claude skill integrates VS Code's powerful diffing engine directly into the agentic workflow, enabling seamless side-by-side file comparisons and visual git diff analysis. By leveraging the VS Code CLI, it provides developers with a high-fidelity graphical interface to review code changes, identify regressions, and verify staged updates, significantly enhancing productivity and code quality during the development process.
Use Cases
- Visual Code Review: Effortlessly compare local file modifications against previous git commits or different branches to ensure logic accuracy and style consistency.
- Git History Analysis: Quickly visualize differences between specific historical versions of a file to track the evolution of a feature or debug regressions.
- Pre-commit Verification: Review staged changes side-by-side with the working directory version to prevent accidental code inclusions and maintain a clean repository state.
- Conflict Resolution: Use the visual interface to compare disparate versions of a file when resolving complex merge conflicts or manual code integrations.
| name | vscode |
|---|---|
| description | VS Code integration for viewing diffs and comparing files. Use when showing file differences to the user. |
VS Code CLI Tools
Tools for integrating with VS Code, primarily for viewing diffs.
Requirements
VS Code must be installed with the code CLI available in PATH.
Opening a Diff
Compare two files side by side in VS Code:
code -d <file1> <file2>
Git Diffs in VS Code
Simple Approach (no config needed)
Extract the old version to a temp file, then diff:
# Compare with previous commit
git show HEAD~1:path/to/file > /tmp/old && code -d /tmp/old path/to/file
# Compare with specific commit
git show abc123:path/to/file > /tmp/old && code -d /tmp/old path/to/file
# Compare staged version with working tree
git show :path/to/file > /tmp/staged && code -d /tmp/staged path/to/file
Gotchas
- File must exist and have changes between the compared revisions
- Use
git log --oneline -5 -- path/to/fileto verify file has history before diffing
When to Use
- Showing the user what changed in a file
- Comparing two versions of code
- Reviewing git changes visually