file-review_skill

Overview

This skill provides a unified file-review entry point that routes requests to Install, Review, or Process workflows. It launches the GUI, parses review comments embedded in files, and helps apply or acknowledge feedback with simple prompts. Use it to streamline local file reviews and to automate handling of embedded review markers.

How this skill works

The skill detects user intent and chooses one of three workflows: Install (installs the CLI/app), Review a File (verifies path, launches the GUI, returns review output), or Process Comments (parses embedded HTML review markers and guides edits). When reviewing, it runs the file-review CLI with optional flags and waits for comment output. When processing, it extracts inline and line comments via regex, summarizes them, and walks the user through applying, acknowledging, or skipping each comment.

When to use it

• You want to open or launch the file-review GUI for a specific file.
• You need to parse and act on review comments embedded in a file.
• file-review is missing and must be installed or verified.
• You mentioned reviewing files, leaving comments, or processing review feedback.
• You need to batch-apply or remove review markers after a GUI session.

Best practices

• If no path is provided, offer recently created or modified markdown or plan files as candidates.
• Verify the file exists and is readable before launching the GUI or parsing comments.
• Prefer 'Acknowledge' for praise or FYI comments; reserve 'Apply edit' for actionable feedback.
• Keep ~/.local/bin in PATH after manual installs so the file-review command is discoverable.
• Confirm proposed edits with the user before writing changes and always summarize results.

Example use cases

• User says "review this file": verify path, launch GUI, then return review comments for processing.
• User says "process comments": parse the file for review markers, summarize comments, and walk through apply/acknowledge/skip options.
• User reports "file-review not found": run the Install workflow with Homebrew or manual steps and verify with which file-review.
• After a GUI review session, collect stdout comment output and proceed to automated comment extraction and processing.
• Handle special cases like empty or unclear feedback by prompting the user for clarification before editing.