file_ops_log

Logs file moves, renames, copies, and trash operations with paths and SHA-256 hashes.

Updated Jun 15, 2026
One-click install
npx skills add https://github.com/kmjy98-sketch/khulaw --skill file-ops-log-kmjy98-sketch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: file_ops_log
Source: https://github.com/kmjy98-sketch/khulaw/tree/main/.agent/skills/file_ops_log
Command: npx skills add https://github.com/kmjy98-sketch/khulaw --skill file-ops-log-kmjy98-sketch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? File and folder moves, renames, and deletions often happen without any audit trail, making it impossible to trace where a file went or verify it was not corrupted. This Skill enforces a mandatory logging rule that records every file operation with timestamps, paths, sizes, and integrity hashes into master CSV, JSONL, and Markdown logs. ## Core Features & Use Cases - Automatic Operation Logging: Records move, rename, copy, and delete-to-trash operations as one row per operation in master.csv, master.jsonl, and master.md. - Integrity Verification: Computes SHA-256 hashes before and after a move and confirms they match, so silent corruption is detected immediately. - Safety Guardrails: Blocks operations on protected shared-drive paths and replaces deletion with moves to a dated _trash folder. - Use Case: While reorganizing a study-materials workspace, you rename and relocate dozens of folders; the helper script performs each move, verifies the hash, and appends a complete audit row you can review later. ## Quick Start Ask the assistant to move a folder to a new location and record the operation with its reason in the file operations log.

Frequently Asked Questions about file_ops_log

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

FAQPage Schema
How do I log file moves and renames automatically?▼

Run the helper script with the operation type, source path, destination path, and a reason. With the execute flag it performs the move, verifies SHA-256 hashes before and after, and appends one row to the master CSV, JSONL, and Markdown logs.

How can I verify a file was not corrupted during a move?▼

The helper computes a SHA-256 hash of the file before moving and again after moving, then compares them. A matching result is recorded in the verified field of the log row, confirming integrity.

Can I log a file operation after moving it manually?▼

Yes. If you already moved the file with mv or Move-Item, run the helper without the execute flag to record the operation only. If the destination exists, it still performs an integrity check automatically.

What happens instead of permanently deleting files?▼

Deletion is prohibited; files are moved to a dated _trash/YYYY-MM-DD folder and logged with the operation type delete-to-trash. This preserves recoverability while keeping the audit trail complete.

Are there paths that cannot be moved or renamed?▼

Yes. The shared-drive directory is strictly protected: moves, renames, and copies targeting it are blocked by policy, and the helper script itself refuses to operate on those paths.