open-changed-files-review

graysurf's avatarfrom graysurf

Open files edited by the agent in VSCode after making changes, using the bundled open-changed-files script (silent no-op when unavailable).

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 11, 2026
[Developer Tools]

When & Why to Use This Skill

This Claude skill streamlines the development workflow by automatically opening files modified by the AI agent directly in Visual Studio Code. It bridges the gap between autonomous agent actions and human oversight, allowing developers to immediately review, test, and refine code changes within their local IDE environment.

Use Cases

  • Post-Refactoring Review: Automatically launch VSCode to inspect multiple files after the agent performs a large-scale code refactor or architectural change.
  • Bug Fix Verification: Instantly jump to the specific lines of code where the agent applied patches to verify the fix and run local debugging tools.
  • Documentation & Config Audit: Quickly review changes to README files, CI/CD configurations, or environment variables in a familiar editor to ensure project compliance.
  • Seamless Context Switching: Reduce manual navigation effort by having the agent present the exact working set of files for immediate human intervention.
nameopen-changed-files-review
descriptionOpen files edited by the agent in VSCode after making changes, using the bundled open-changed-files script (silent no-op when unavailable).

Open Changed Files Review

Contract

Prereqs:

  • zsh available on PATH.
  • Optional: VSCode CLI code (missing → script no-ops).
  • $AGENT_KIT_HOME/skills/open-changed-files-review/scripts/open-changed-files.zsh available.

Inputs:

  • File paths touched in the current run (preferred).
  • Optional: OPEN_CHANGED_FILES_MAX_FILES to cap opened files.

Outputs:

  • Opens the requested files in VSCode (best-effort).
  • If VSCode/tool unavailable: silent no-op (still provides a paste-ready command in chat when used manually).

Exit codes:

  • 0: success or no-op
  • non-zero: invalid usage or unexpected runtime failure

Failure modes:

  • VSCode CLI code not installed or not on PATH.
  • Input paths do not exist (script filters to existing files).

Use this skill when the agent has edited files and you want to immediately open the touched files in Visual Studio Code for human review.

Inputs

  • A list of file paths that were modified/added in this run (preferred; does not require git).

Workflow

  1. Build a de-duplicated list of existing files from the touched paths.
  2. Determine the cap:
    • Default: OPEN_CHANGED_FILES_MAX_FILES=50
    • If there are more files than the cap: open the first N and mention that it was truncated.
  3. Prefer running:
    • $AGENT_KIT_HOME/skills/open-changed-files-review/scripts/open-changed-files.zsh --max-files "$max" --workspace-mode pwd -- <files...>
  4. If VSCode CLI code (or the tool) is unavailable: silent no-op (exit 0, no errors), but still print a paste-ready manual command plus the file list for the user.

Paste-ready command template

$AGENT_KIT_HOME/skills/open-changed-files-review/scripts/open-changed-files.zsh --max-files "${OPEN_CHANGED_FILES_MAX_FILES:-50}" --workspace-mode pwd -- <files...>