drift-audit

Audits Hermes agent sessions for undocumented environment changes and commits them to homelab docs.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/timchap/dot-hermes --skill drift-audit-timchap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: drift-audit
Source: https://github.com/timchap/dot-hermes/tree/main/skills/devops/drift-audit
Command: npx skills add https://github.com/timchap/dot-hermes --skill drift-audit-timchap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Environment changes made during AI agent sessions (software installs, systemd units, config edits, cron jobs) often go undocumented and unpersisted, causing configuration drift between the live system and its homelab documentation or Ansible playbooks. ## Core Features & Use Cases - Session Review: Scrolls through recent Hermes sessions using session_search to detect installs, systemd changes, network changes, and Hermes-specific modifications. - Drift Detection & Persistence: Checks each change against ~/homelab/docs/ and ~/homelab/ansible/, writes documentation updates, and commits with clear messages. - Git Safety Handling: Verifies remotes before pushing, avoids git add -A pitfalls in ~/.hermes/, and reports drift found, actions taken, and items left unchanged. - Use Case: Run as a scheduled cron job to answer "what changed since last audit?" and keep homelab docs and Ansible playbooks in sync with the actual system state. ## Quick Start Ask the agent to run a drift audit reviewing all sessions since the last audit and commit any undocumented environment changes to the homelab repo.

Frequently Asked Questions about drift-audit

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

FAQPage Schema
How do I audit AI agent sessions for undocumented server changes?▼

Use session_search to review recent sessions for package installs, systemd changes, config edits, and git commits, then compare findings against your homelab docs. Document each untracked change and commit it to the homelab git repository.

How to detect configuration drift in a homelab environment?▼

Configuration drift is detected by reviewing session history for environment-modifying actions like apt installs, systemctl changes, and file writes, then checking whether each change exists in ~/homelab/docs/ or Ansible playbooks. Unmatched changes are drift.

Why does git push fail with no configured push destination in a homelab repo?▼

This error occurs when the repository has no remote origin configured. Check with git remote -v, and either add a remote with git remote add origin <url> or commit locally only and note the missing remote in the audit report.

Why does git add -A stage thousands of files in the ~/.hermes/ directory?▼

The ~/.hermes/ .gitignore misses directories like bin/, lsp/, webui/, and pastes/, so git add -A can stage thousands of runtime artifacts including node_modules. Stage only specific changed files and verify with git status --short before committing.

When should environment changes not be persisted to Ansible?▼

Skip Ansible when the ~/homelab/ansible/ directory is empty or missing, and for user-level changes like npm installs or user systemd units unless explicitly requested. Document those changes in ~/homelab/docs/ instead.