audit-safe-move

Audit SHA256-protected file movement in classification workflows.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/ElPoot/contabilidad --skill audit-safe-move
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-safe-move
Source: https://github.com/ElPoot/contabilidad/tree/main/.agents/skills/audit-safe-move
Command: npx skills add https://github.com/ElPoot/contabilidad --skill audit-safe-move

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents the accidental loss or corruption of fiscal documents by auditing that the atomic SHA256-based file movement protocol is followed end to end.

Core Features & Use Cases

  • Protocol integrity auditing: Verifies that original SHA256 is computed, the destination is created, the copy is made with metadata preservation, the copy SHA256 is rechecked, mismatches trigger rollback, and only then the original is deleted.
  • Call-site coverage for classification flow: Focuses specifically on the classification pipeline where file movement happens (classifier, ORS purge, receptor purge, and GUI call sites).
  • Actionable findings report: Produces a structured audit report that either confirms compliance ("SIN PROBLEMAS") or lists real issues with evidence and severity.

Quick Start

Ask an auditor to run the audit for the current codebase by checking the implementation of classify_record() and safe_move_file() and then generating the report listing any protocol deviations with exact line evidence.

Frequently Asked Questions about audit-safe-move

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

FAQPage Schema
How do I verify file integrity when moving invoices to prevent fiscal document loss?

To verify file integrity during invoice movement, compute the original SHA256 hash, create a metadata-preserving copy, recheck the copy's SHA256, roll back on mismatch, delete the original after verification, and register the hash in SQLite.

What is an atomic SHA256-protected file move protocol?

An atomic SHA256-protected file move protocol is a sequence that computes source hashes, performs a metadata-preserving copy, validates the destination hash, triggers rollback on mismatch, and only deletes the original after successful verification.

How do I audit safe file movement in a Python classification workflow?

You audit safe file movement in a classification workflow by checking the implementation of classify_record() and safe_move_file() call paths, verifying SHA256 checks, metadata preservation, rollback logic, and SQLite registration to generate a structured compliance report.

Does the file integrity audit cover GUI triggers and purge operations?

Yes, the file integrity audit covers GUI triggers that invoke safe_move_file() or classify_record(), as well as ORS purge and receptor purge operations, ensuring the entire classification pipeline follows the SHA256 verification protocol.

What happens when a SHA256 mismatch is detected during atomic file movement?

When a SHA256 mismatch is detected during atomic file movement, the protocol enforces a rollback of the copy operation and prevents deletion of the original file, ensuring the fiscal document remains intact and uncorrupted.

Can I use this audit for SQLite invoice handling systems with PermissionError handling?

Yes, this audit applies to SQLite invoice handling systems by verifying that original file hashes are registered in the database after movement and checking that PermissionError scenarios during file operations do not bypass the SHA256 verification protocol.