tidy-hermes-workspace-hygiene

Enforce file routing and git-aware safety checks for Hermes workspace changes.

35|2|Updated May 26, 2026
One-click install
npx skills add https://github.com/sene1337/hermes-proficiencies --skill tidy-hermes-workspace-hygiene
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tidy-hermes-workspace-hygiene
Source: https://github.com/sene1337/hermes-proficiencies/tree/main/skills/hermes-proficiencies/tidy-hermes-workspace-hygiene
Command: npx skills add https://github.com/sene1337/hermes-proficiencies --skill tidy-hermes-workspace-hygiene

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill prevents an agent from scattering files, making risky or destructive workspace changes, and leaving behind artifacts that are hard to audit or roll back later.

Core Features & Use Cases

  • Action-triggered workspace safety: Automatically loads before file-affecting actions like create/edit/move/delete/sync/publish so Hermes routes work deliberately.
  • Git-aware verification and rollback discipline: Uses git as the safety net, checks status/diffs where relevant, and avoids unsafely relying on “undo later.”
  • Mode-based handling for protected and destructive cases: Applies stricter rules for protected knowledge bases, skill source/runtime hygiene, publishing safety, and bulk/destructive operations.

Quick Start

When you ask Hermes to update or generate any durable workspace file, install and use tidy-hermes-workspace-hygiene so it chooses correct destinations, avoids orphans, and includes verification evidence.

Frequently Asked Questions about tidy-hermes-workspace-hygiene

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

FAQPage Schema
How do I prevent an AI agent from making destructive file changes in my workspace?

To prevent destructive file changes, you need workspace hygiene enforcement that applies mode-based escalation rules and explicit approval gates before an agent can move, delete, or overwrite durable files.

What is workspace hygiene for AI file routing and why is it needed?

Workspace hygiene for AI file routing is the discipline of enforcing correct file destinations and avoiding orphan artifacts. It is needed to ensure agent-created files remain auditable and easy to roll back using git.

How do I enforce git safety checks before an agent syncs or publishes files?

You enforce git safety checks by requiring an agent to verify git status and diffs before syncing or publishing, ensuring it relies on actual repository state rather than assuming it can undo changes later.

Can I require explicit approval before an agent modifies a protected knowledge base?

Yes, you can require explicit approval gates for protected knowledge base interactions. This ensures the agent applies stricter handling rules and pauses for authorization before modifying any protected runtime or source files.

What is the best way to audit where an agent created or moved workspace files?

The best way to audit agent file operations is to use evidence-oriented reporting. This approach requires the agent to log touched paths and verification checks for every create, edit, move, or delete action it executes.

Do I need git to manage AI agent workspace changes and rollbacks?

Git is highly recommended for managing AI agent workspace changes. It serves as the safety net by providing verifiable diffs and status checks, preventing unsafe reliance on manual undo procedures after bulk operations.