maintenance_skill

This skill helps you organize and clean project files, archive old logs, and reduce bloat by following automated cleanup references.
  • Shell

212

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill chachamaru127/claude-code-harness --skill maintenance

  • SKILL.md1.3 KB

Overview

This skill performs file maintenance and cleanup to keep a codebase and workspace tidy. It focuses on organizing files, removing temporary or large artifacts, archiving session logs and Plans.md, and reducing file bloat. Do not use this skill for implementation, code review, new feature development, or deployment tasks.

How this skill works

On request, the skill classifies the user's intent to confirm a cleanup or archival action. It reads the relevant reference instructions for automatic cleanup and follows them to identify candidate files for deletion, compression, or relocation. The skill then proposes a safe plan (files to remove, archive, or reorganize) and can execute the plan after explicit user approval.

When to use it

  • You want to remove temporary build artifacts, caches, or large generated files.
  • You need to archive or tidy Plans.md, session logs, and other process records.
  • You notice repository or workspace file bloat and want a targeted cleanup.
  • You want to reorganize scattered files into clear folders or an archive.
  • You need a repeatable cleanup routine applied to a project workspace.

Best practices

  • Run the skill only when cleanup is the intent; do not invoke for coding, reviews, or deployments.
  • Review the proposed plan before execution to avoid accidental data loss.
  • Back up critical files (Plans.md, session logs, config) before deletion or compression.
  • Prefer archiving (zip/tar) over permanent deletion for important historical files.
  • Limit automated deletion to well-known temporary patterns (node_modules/.cache, build/, tmp/).

Example use cases

  • Archive all session logs older than 90 days into an archive directory and remove originals.
  • Detect and remove large generated assets from the workspace to recover disk space.
  • Consolidate scattered Plans.md and related notes into a single docs/plan-archive folder.
  • Run an automatic cleanup pass to remove build caches and temporary files before packaging.
  • Compress and relocate infrequently used logs to a storage location to reduce repo size.

FAQ

No. The skill targets temporary, generated, or clearly identified archival candidates. It always presents a plan and requires explicit approval before destructive actions.

Can I undo an automated cleanup?

If you archive instead of delete, you can restore files from the archive. For permanent deletions, restore depends on your backup or VCS history—create backups before running destructive steps.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational