vscode
/vscode
VS Code integration for viewing diffs and comparing files. Use when showing file differences to the user.
- Author
- badlogic ↗
- Repository
- pi-skills ↗
- Licence
- MIT
- Last repository change
- 06.06.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 06.06.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
VS Code integration for viewing diffs and comparing files. Use when showing file differences to the user.
Original author description
VS Code integration for viewing diffs and comparing files. Use when showing file differences to the user.
How it works
- Requirements
- Opening a Diff
- Git Diffs in VS Code
- When to Use
SKILL.md preview
--- 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: ```bash code -d <file1> <file2> ``` ## Git Diffs in VS Code ### Simple Approach (no config needed) Extract the old version to a temp file, then diff: ```bash # 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/file` to 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
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · badlogic/pi-skills | 100 | MIT |
| G1Joshi/Agent-Skills | 100 | MIT |
| clawic/skills | 90 | MIT |
Identical content appears in 3 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 4d194e23dfb9 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90arch-vscode
VSCode extension starter using reactive-vscode and tsdown. Use when scaffolding or maintaining a VSCode extension with reactive APIs, CJS build, and vscode-ext-gen. - 100vscode-dev-workbench
Use when the user wants to run the vscode.dev server locally and exercise the VS Code workbench or Agents window in the integrated browser against the local `microsoft/vscode` sources. Covers starting the dev server, the `vscode-quality=dev` URL, browser-driven interaction… - 95init-vscode
初始化或更新 VSCode 配置文件(.vscode/extensions.json 和 .vscode/settings.json), 治理扩展推荐的生命周期与已知替代关系,并在 JSONC 安全迁移、工作区/用户级 scope、 preflight/postflight 和可回滚验收之间建立明确边界;同时把 `files.eol` 收敛为 `"\n"`, 配合 `.gitattributes`、`.editorconfig`、Prettier 解决 Windows 上的 CRLF/LF 漂移与 git 幽灵修改问题, 并补齐大型 monorepo… - 100pr-review
Verify the technical accuracy of a vscode-docs pull request against the VS Code source code in microsoft/vscode and microsoft/vscode-copilot-chat. Use when reviewing a docs PR for factual correctness — setting names, command IDs, default values, API shapes, keybindings,… - 100vscode-settings
Configure a project's .vscode/settings.json - 2-space indent, no symlink following, and a per-project title bar/status bar color. Use when setting up VS Code for a project or changing its window color. - 100vscode-bookmarks
Create and manage VS Code Bookmarks extension labeled bookmarks in .vscode/bookmarks.json. Use when the user wants to add navigation bookmarks to a codebase, trace data flows through code, mark important code locations, or set up labeled waypoints for code walkthroughs. Also use…