Housekeeping

Run deterministic fleet-wide audits and mechanical cleanups across repository clones.

8|1|Updated Jan 21, 2024
One-click install
npx skills add https://github.com/azigler/dotfiles --skill housekeeping-azigler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Housekeeping
Source: https://github.com/azigler/dotfiles/tree/main/agents/skills/housekeeping
Command: npx skills add https://github.com/azigler/dotfiles --skill housekeeping-azigler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Housekeeping prevents drift across the factory and every agent clone by enforcing mechanical cleanups and running deterministic fleet-wide audits of repo state, skills, beads, lint, services, and memory indexes.

Core Features & Use Cases

  • Mechanical cleanup + documentation refresh: delete deprecated code, update specs/architecture docs, refresh README/CLAUDE.md, and add deprecation markers without changing behavior.
  • Fleet-wide state audits: verify CLAUDE.md identity per agent, ensure skill-file consistency across global/canonical/factory copies, and check bead hygiene (including closing, syncing JSONL drift, and routing follow-ups into beads).
  • Deterministic quality gates: run import-dependency scans before deletions, regenerate derived architecture views from active decision beads, auto-fix formatting/lint via Biome, and validate systemd worker/dev-server health plus worktree cleanup and memory index correctness.

Quick Start

Run /housekeeping from the factory root to perform the fleet-wide hygiene pass, then confirm the exit criteria are all green.

Frequently Asked Questions about Housekeeping

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

FAQPage Schema
How do I prevent repository and agent clone drift across my fleet?▼

To prevent repository and agent clone drift, run fleet-wide housekeeping audits that enforce mechanical cleanups, verify CLAUDE.md identity per agent, and ensure byte-identical skill consistency across global, canonical, and factory copies.

What is the best way to safely remove deprecated code with dependency checks?▼

Safely removing deprecated code requires running grep-based import-dependency scans as deletion safety gates before changes, ensuring no active references remain, and then applying mechanical cleanup alongside spec and README alignment.

How do I sync bead hygiene and JSONL database drift across multiple clones?▼

Syncing bead hygiene and JSONL drift requires deterministic cross-clone audits that validate open-beads closing correctness, resolve JSONL and database synchronization issues, and route follow-up actions into active decision beads.

Does repository housekeeping verify systemd worker and dev-server health?▼

Repository housekeeping includes deterministic quality gates that validate systemd worker and dev-server health, check worktree cleanup, verify memory index correctness, and confirm all services are green before exiting.

Can I regenerate derived architecture docs from active decision beads?▼

Yes, you can optionally regenerate derived architecture documentation directly from active decision beads during the housekeeping pass, ensuring your specs and architecture views stay aligned with the latest decision records.