菜单
Recovering lost or overwritten files from the guardrails archive store. Use when the user says a file was deleted, overwritten, truncated, or "messed up", or asks to roll back to an earlier version or undo a recent file operation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
CRUA workflow for editing Office and proprietary documents (docx, xlsx, pptx, pdf) safely. Use when asked to modify, update, fill in, or rewrite a document file — checkout converts it to markdown/csv in _workspace/, you edit the copy, publish archives the old version and replaces the original. Never edit proprietary formats in place.
Handling Google Docs/Sheets/Slides files that appear in a Google Drive for desktop synced folder as .gdoc/.gsheet/.gslides files. Use when a task involves one of these extensions or when the user asks to edit a Google Doc from their local Drive folder.
Safety rules for working inside cloud-synced folders — OneDrive, SharePoint synced libraries, Google Drive for desktop, Dropbox. Use whenever a task touches files under a synced folder, before bulk operations, or when a file read returns empty/garbage content for a file that clearly should have data.
| name | restore |
| description | Recovering lost or overwritten files from the guardrails archive store. Use when the user says a file was deleted, overwritten, truncated, or "messed up", or asks to roll back to an earlier version or undo a recent file operation. |
Everything the guardrails touch is recoverable: every archive, every publish, and every native Write/Edit (a pre-image snapshot is taken automatically before the tool runs). Deletion is disabled, so "deleted" almost always means "archived" or "overwritten with a snapshot available".
agw log <path> # operations involving this path
agw log # recent operations, newest last
agw status # open checkouts
agw log --json gives structured entries with version numbers, timestamps,
hashes, and the archived copy's location.
agw restore <path> # latest archived version
agw restore <path> --version 3 # a specific version
agw undo # revert the single most recent archive/move
Restore is itself non-destructive: if a live file exists at the target path, it is archived first, then the requested version is put in place. You can restore back and forth between versions without losing anything.
| Symptom | Likely cause | Fix |
|---|---|---|
| "File is gone" | Archived (rm was redirected) or moved | agw log <path>, then agw restore or agw undo |
| "File has wrong/old content" | Overwritten by a Write/Edit | agw log <path> — pre-image snapshots appear as copy-mode archives; restore the version wanted |
| "Publish clobbered a colleague's edit" | Forced publish over a conflict | The pre-publish copy is archived; agw restore <path> --version N |
| "Whole folder is wrong" | Bulk operation | agw log for the folder's files; restore individually, or use a prior agw snapshot |
agw verbs only — never copy files out of
~/.agw/archive by hand (the manifest would no longer match reality).agw prune (permanent removal of old versions) is human-only. If the user
asks you to free space, point them at the command and its
--yes-i-am-a-human flag; do not run it for them.