Intelligent workspace cleanup to prevent over-committing temporary files

[carmandale]

Problem: Claude Code hooks currently enforce clean workspace by committing everything, including temporary files, logs, and potentially sensitive data. This leads to messy commits and poor git hygiene.

Current Behavior:

• Hook requires clean workspace before new work
• Claude commits all changes indiscriminately to satisfy hook
• Results in commits with .log files, temporary files, node_modules, etc.
• User feedback: "feels messy and over-committing"

Needed Solution:

• Intelligent analysis of workspace changes
• Distinguish valuable changes from temporary files
• Smart cleanup suggestions vs blind committing
• Protection against committing secrets/sensitive data
• Maintain workflow enforcement while improving git hygiene

Impact: Critical for maintaining professional development standards and preventing security issues from accidental commits of sensitive data.

[carmandale]

Current Status: Spec completed, implementation not started

• ✅ Complete specification exists in @.agent-os/specs/2025-07-30-intelligent-workspace-cleanup-#11/
• ❌ No implementation has begun
• ❌ All 5 major tasks (48 subtasks) remain incomplete

Priority: High - This addresses a critical user experience issue with 'messy commits' and prevents accidental commits of sensitive data.

Next Step: Someone needs to begin Task 1.1 (Write tests for file categorization logic) to start implementation.

[carmandale]

Still needed: add cleanup rules and ignore patterns; propose a guard that flags large/binary/temp files in staged changes and suggests .gitignore updates before commit. Will add to pre-commit/CI.