aops-cli-fileman

Manages filesystem snapshots, diffs, restores, and cleanup through the aops CLI Fileman domain.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/eeemzs/aops --skill aops-cli-fileman-eeemzs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aops-cli-fileman
Source: https://github.com/eeemzs/aops/tree/main/assets/skills/aops-cli-fileman
Command: npx skills add https://github.com/eeemzs/aops --skill aops-cli-fileman-eeemzs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents working on projects need a reliable way to track directories, capture immutable snapshots of file state, compare versions, and recover files without manually copying folders or pasting large file contents into memory or documents. ## Core Features & Use Cases - Target Tracking and Snapshots: Track a directory root, capture baseline and checkpoint snapshots, and list or inspect snapshot history. - Diff, Restore, Copy, and Zip: Compare snapshots chronologically, restore full trees or single files with dry-run safety, and export snapshot trees as directories or zip archives for handoff. - Cleanup and Pointer Discipline: Clean stale Fileman state through the hosted graph and reference Fileman ids instead of embedding file bodies in PM, Docman, or memory. - Use Case: Before a risky refactor, an agent tracks the project directory, creates a labeled snapshot, and later diffs or restores the tree with --dry-run followed by --apply --confirm if the refactor goes wrong. ## Quick Start Ask your agent to track a project directory with aops-cli file target track and create a labeled baseline snapshot of its current state.

Frequently Asked Questions about aops-cli-fileman

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

FAQPage Schema
How do I create a snapshot of a directory with aops-cli?▼

Track the directory first with aops-cli file target track --root-path <dir> --apply, then run aops-cli file snapshot create --target-id <id> --apply. Read the resulting ids from result.data.targetId and result.data.snapshotId in the JSON output.

How do I restore files from a snapshot safely?▼

Run aops-cli file snapshot restore --snapshot-id <id> --dry-run first to preview effects, then rerun with --apply --confirm, optionally adding --backup-before-restore. Single-file recovery uses aops-cli file file restore with the same dry-run pattern.

Can I track a single file instead of a directory?▼

No, file target track requires a directory root and rejects single files with target_path_not_directory. Track the parent directory instead, then operate on the file with aops-cli file file history, get, diff, or restore using its relative path.

How do I diff two snapshots in aops Fileman?▼

Use aops-cli file snapshot diff --from-snapshot-id <older> --to-snapshot-id <newer> for a chronological addition-style diff. The --target-id form lets Fileman pick the pair and direction, which may produce surprising results.

Why should I avoid deleting snapshot files manually?▼

Manual deletion of snapshot storage can break hosted graph consistency. Use aops-cli file clean --target-id <id> --dry-run --preview first, then --apply --confirm, optionally with --missing-only to remove stale targets.