reviewed-edit

Route vault file edits outside the writable workspace through human approval.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/artislismanis/obsidian-agent-sandbox --skill reviewed-edit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewed-edit
Source: https://github.com/artislismanis/obsidian-agent-sandbox/tree/main/workspace/.claude/skills/reviewed-edit
Command: npx skills add https://github.com/artislismanis/obsidian-agent-sandbox --skill reviewed-edit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Make safe edits to vault files outside the writable workspace directory using human-in-the-loop review. Use when the user asks to edit an existing note that lives outside $PKM_WRITE_DIR, or explicitly says "review before applying".

Core Features & Use Cases

  • Route edits to non-workspace notes through a strict reviewed workflow to require approval before changes are saved.
  • Support common operations (rename, move, delete, or content edits) with per-file review modals and clear audit trails.
  • Ensure safety with tiered tooling and explicit path confirmation to prevent accidental writes outside the workspace.

Quick Start

Edit a non-workspace file and trigger the review workflow before applying changes.

Frequently Asked Questions about reviewed-edit

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

FAQPage Schema
How do I safely edit Obsidian vault files outside my writable workspace?

To safely edit vault files outside your writable workspace, changes are routed through a human-in-the-loop review workflow that requires explicit user approval before applying any modifications.

What vault operations are supported by the human-in-the-loop review workflow?

The human-in-the-loop review workflow supports renaming, moving, deleting, and editing content of non-workspace vault files, generating per-file review modals and clear audit trails for each operation.

Does the reviewed edit workflow require a specific write permission tier?

Yes, the reviewed edit workflow requires the writeReviewed tier to be enabled, along with path resolution via vault_file_info and the appropriate _reviewed tools for each specific file operation.

When should I use a reviewed edit instead of a direct vault modification?

Use a reviewed edit when modifying existing notes that live outside your PKM_WRITE_DIR or when you explicitly request to review changes before applying them to ensure strict human-in-the-loop safety.

Can I batch edit multiple non-workspace vault files without individual approval?

No, batch edits are not supported without approval. The workflow enforces strict per-file review modals to require explicit user confirmation before saving changes to each non-workspace file.

Why do my workspace edits trigger a diff modal before saving?

Edits trigger a diff modal because the file resides outside the writable workspace directory, activating the reviewed edit workflow to prevent accidental writes by requiring explicit path confirmation.