cleanup-artifacts

Mission

Analyze the current project state, identify temporary artifacts and development files, then run the cleaner agent to clean them up safely while preserving important implementation code and documentation.

Workflow

STEP 1: Analyze Current Project State

1. Gather Project Context:

   • Run git status to see current state
   • Run git diff --stat to see what's been modified
   • Use Glob to find common artifact patterns:
     • Test files: **/*.test.{ts,tsx,js,jsx}
     • Spec files: **/*.spec.{ts,tsx,js,jsx}
     • Temporary documentation: AI-DOCS/**/*-TEMP.md, AI-DOCS/**/*-WIP.md
     • Development scripts: scripts/dev-*.{ts,js}, scripts/temp-*.{ts,js}
     • Build artifacts: dist/**/*, build/**/*, .cache/**/*
     • Coverage reports: coverage/**/*
     • Log files: **/*.log, **/*.log.*
     • Editor files: **/.DS_Store, **/*.swp, **/*.swo

2. Identify Current Task:

   • Check for AI-DOCS/ folder to understand recent work
   • Look for recent commits to understand context
   • Analyze modified files to determine what's being worked on

3. Categorize Files:

   • Artifacts to Clean: Temporary files that can be safely removed
   • Files to Preserve: Implementation code, final tests, user-facing docs, configs
   • Uncertain Files: Files that might need user input

STEP 2: Present Findings to User

Present a clear summary:

# Cleanup Analysis

## Current Project State
- Git Status: [clean/modified/staged]
- Recent Work: [description based on git log and AI-DOCS]
- Modified Files: [count and summary]

## Artifacts Found

### Will Clean (if approved):
- Temporary test files: [count] files
- Development artifacts: [count] files
- Intermediate documentation: [count] files
- Build artifacts: [count] files
- [Other categories found]

### Will Preserve:
- Implementation code: [list key files]
- Final tests: [list]
- User-facing documentation: [list]
- Configuration files: [list]

### Uncertain (need your input):
- [List any files where classification is unclear]