# Organize Project Maintenance Files

Project planning files and session logs can grow until they are hard to review. This skill checks common maintenance files and recommends cleanup, archiving, or splitting actions.

## Install

```bash
npx skillstore add chachamaru127/maintenance
```

## Metadata

- - Slug: chachamaru127-maintenance
- - Version: 1.0.0
- - Author: Chachamaru127
- - GitHub username: Chachamaru127
- - License: MIT
- - Repository: https://github.com/Chachamaru127/claude-code-harness/tree/main/skills/maintenance
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: medium
- - Risk factors: external\_commands, filesystem
- - Quality score: 71
- - Public page: https://skillstore.pages.dev/skills/chachamaru127-maintenance
- - Manifest: https://skillstore.pages.dev/api/skills/chachamaru127-maintenance/manifest

## Capabilities

- Checks Plans.md size and completed task counts against configured thresholds.
- Identifies completed tasks that may be old enough to archive.
- Reviews session-log.md size and suggests monthly archive splitting.
- Warns when CLAUDE.md is large and suggests moving nonessential content.
- Supports project-specific cleanup thresholds through a YAML configuration file.
- Provides status messages for clean, cleanup-needed, and cleanup-complete cases.

## Use Cases

- Archive completed planning tasks: Move older completed Plans.md items into an archive while keeping active work visible.
- Control session log growth: Review session-log.md size and split older entries into monthly archive files.
- Keep project guidance concise: Detect when CLAUDE.md is too large and recommend moving detailed notes into separate documents.

## Prompt Templates

### Check cleanup status

```
Review my project maintenance files and tell me whether cleanup is needed. Do not modify files yet.
```

### Preview archive candidates

```
Find completed Plans.md tasks that look ready for archive. Show the proposed moves and wait for approval.
```

### Organize session logs

```
Check .claude/memory/session-log.md and propose a monthly archive plan for old entries.
```

### Run a controlled cleanup

```
Perform project cleanup after showing a dry run, creating backups, and preserving all in-progress tasks.
```

## Limitations

- It relies on Bash-oriented examples and may need adjustment on different shells.
- It does not include a packaged standalone cleanup executable.
- It should not move in-progress tasks without explicit review.
- It does not perform network backup or external storage synchronization.

## Best Practices

- Run a dry review before allowing file edits or archive moves.
- Keep backups of planning and session files before cleanup.
- Confirm that in-progress tasks are excluded from archive actions.

## Anti Patterns

- Do not run cleanup across unrelated directories or repositories.
- Do not archive tasks only because a file is long.
- Do not treat generated recommendations as a substitute for human approval.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-28T20:07:16.694\+00:00
- - Summary: Static analysis reported many command-execution, filesystem, weak-crypto, and entropy findings. Review found no malicious payload, network access, credential handling, or prompt-injection text, but the skill intentionally allows Bash and file editing for project cleanup, so it should publish with a medium-risk warning.

## Stats

- - Views: 177
- - Downloads: 1
- - Favorites: 0
- - Popularity score: 0