Intercept file changes and require per-file, per-hunk approval before writing.
npx skills add https://github.com/T0MMMMM/code-review-skill --skill code-review-t0mmmmm
Please help me install this Agent Skill. Skill: code-review Source: https://github.com/T0MMMMM/code-review-skill/tree/main/code-review Command: npx skills add https://github.com/T0MMMMM/code-review-skill --skill code-review-t0mmmmm
Intercepts all file changes Claude is about to make and presents a structured review before any write, preventing silent or unintended edits.
Ask Claude to intercept proposed file changes and present a structured review before saving to disk.
High-intent search queries and answers about installing and using this skill.
To intercept file changes before they are written, you need a pre-write check mechanism that halts operations like create, modify, rename, or delete actions. This skill enforces that review process, presenting a structured diff for every patch before any file is saved.
Yes, per-hunk review allows you to decide for each specific patch whether to accept, reject, or edit it. This granular approach ensures you apply file changes selectively rather than approving an entire modified file blindly.
The diff viewer supports both Claude.ai and Claude Code environments. It provides an interactive React diff viewer for Claude.ai and a formatted structured text diff list with numbered options for the Claude Code terminal interface.
A pre-write check is an enforced step that intercepts all file changes before they are applied to disk. It prevents unintended edits by requiring a structured review of every trivial or significant change, ensuring silent writes never occur without explicit approval.
You can stop automatic modifications by enforcing a pre-write check that intercepts file changes across code, configs, docs, and data. This requires an interactive review of the proposed diff before any write tool executes the operation.
The main limitation of enforcing file write approvals is that even trivial changes go through the review process. While this ensures safe defaults and prevents silent edits, it requires manual interaction for every file and hunk before applying changes to disk.
supermalangRead visual approval states for changed baseline images without modifying repository files.
IliyaBrookReview and simplify recently modified code for clarity and maintainability.
wangqianCAIGenerate interactive diff viewers and PNG or PDF diff artifacts for code changes.
MinhmiceInspect code diffs for security flaws, bugs, and maintainability issues.
