vscode-review

Review VS Code extension activation, commands, views, and LSP-client integration changes.

4.4k|154|Updated Mar 17, 2026

Search Tags:#activation #LSP #VSCode #editor integration #Code review #extension review

One-click install

npx skills add https://github.com/fallow-rs/fallow --skill vscode-review

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: vscode-review
Source: https://github.com/fallow-rs/fallow/tree/main/.agents/skills/vscode-review
Command: npx skills add https://github.com/fallow-rs/fallow --skill vscode-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Changes to a VS Code extension can silently break activation behavior, command wiring, or editor integration, and manual review of these areas is easy to skip. This Skill provides a structured review workflow for fallow's VS Code extension so every change under editors/vscode gets consistent scrutiny.

Core Features & Use Cases

Extension Behavior Review: Examines activation behavior, command wiring, views, and downloads for correctness and UX quality.
LSP-Client Integration Checks: Verifies the language server client integration works as expected inside the editor.
Structured Verdicts: Ends each review with a clear APPROVE, CONCERN, or BLOCK decision.
Use Case: After modifying files under editors/vscode in the fallow repository, run this review to confirm activation events, contributed commands, and editor integration still behave correctly before merging.

Quick Start

Review the recent changes to the VS Code extension under editors/vscode and give me an APPROVE, CONCERN, or BLOCK verdict.

Frequently Asked Questions about vscode-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I review VS Code extension changes before merging?▼

Use this review workflow to inspect activation behavior, command wiring, views, and LSP-client integration for any change under editors/vscode. It ends with a clear APPROVE, CONCERN, or BLOCK verdict so reviewers can act on the result.

What does a VS Code extension review check?▼

The review focuses on extension UX, activation events, contributed commands, views, downloads, and the language server client integration. It follows the guidance in the vscode-reviewer agent file and the vscode-extension rules.

When should I run the VS Code extension review?▼

Run it whenever changes touch the editors/vscode directory of the fallow repository. It is designed specifically for that scope and is not intended for unrelated parts of the codebase.

What are the possible outcomes of the extension review?▼

Every review concludes with one of three verdicts: APPROVE when the changes are sound, CONCERN when issues need attention, or BLOCK when the changes must not merge as-is.