home / skills / chachamaru127 / claude-code-harness / maintenance

maintenance skill

safe

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

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

Review the files below or copy the command above to add this skill to your agents.

Files (2)

SKILL.md

1.3 KB

---
name: maintenance
description: "ファイル整理とクリーンアップ。散らかった部屋をピカピカに。Use when user mentions cleanup, archive, file bloat, or organizing Plans.md/session logs. Do NOT load for: implementation work, reviews, new feature development, or deployment."
description-en: "File cleanup and organization. Messy room made spotless. Use when user mentions cleanup, archive, file bloat, or organizing Plans.md/session logs. Do NOT load for: implementation work, reviews, new feature development, or deployment."
description-ja: "ファイル整理とクリーンアップ。散らかった部屋をピカピカに。Use when user mentions cleanup, archive, file bloat, or organizing Plans.md/session logs. Do NOT load for: implementation work, reviews, new feature development, or deployment."
allowed-tools: ["Read", "Write", "Edit", "Bash"]
argument-hint: "[cleanup|archive]"
---

# Maintenance Skills

ファイルのメンテナンス・クリーンアップを担当するスキル群です。

## 機能詳細

| 機能 | 詳細 |
|------|------|
| **自動クリーンアップ** | See [references/auto-cleanup.md](references/auto-cleanup.md) |

## 実行手順

1. ユーザーのリクエストを分類
2. 上記の「機能詳細」から適切な参照ファイルを読む
3. その内容に従って実行

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

Will this skill delete important source files?

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.