FILE-ORGANIZER-005 Monitoring Guidelines
Purpose​
Monitor the v4 directory structure for organization opportunities and maintain cleanliness.
Monitoring Schedule​
- Run health check weekly or when significant changes occur
- Review after major ADR updates or implementations
- Check after session exports accumulate
Health Check Script​
./scripts/directory-health-check.sh
Common Issues to Watch For​
1. Duplicate Files​
- Multiple versions of same content with different names
- Backup files that become outdated
- Test files that accumulate over time
2. Misplaced Files​
- Export files outside
.codi/session/conversations/ - Documentation in code directories
- Test data in production paths
3. Naming Inconsistencies​
- Multiple QA review versions (FINAL, UPDATED, etc.)
- Inconsistent version suffixes (-v2, -v3, etc.)
- Timestamp formats varying
4. Temporary Files​
- Editor swap files (.swp, ~)
- Build artifacts outside target/
- Temporary test files
Cleanup Actions​
Automated Cleanup​
Use cleanup-duplicates.sh for known patterns:
- Duplicate test conversation files
- Identical backup files
- Misplaced exports
Manual Review Needed​
- Multiple QA review versions (need content review)
- Outdated documentation (requires verification)
- Legacy files from old implementations
Best Practices​
-
Regular Health Checks
# Add to weekly routine
./scripts/directory-health-check.sh -
Immediate Action Triggers
- More than 100 test files
- Any duplicate production files
- Misplaced sensitive documents
-
Prevention
- Use consistent naming from the start
- Move exports immediately after creation
- Clean up backups after changes stabilize
Integration with CODI​
Log all cleanup activities:
.codi/bin/codi-log-as "FILE-ORGANIZER-005" "Running weekly health check" "HEALTH_CHECK"
.codi/bin/codi-log-as "FILE-ORGANIZER-005" "Found X issues, creating cleanup plan" "CLEANUP_PLAN"
Contact​
FILE-ORGANIZER-005 is an automated monitoring agent. For manual oversight, coordinate through CODI logs.