/wbClean — Live Demo ()
What /wbClean would actually do on wb-labs right now. The candidate targets and likely findings below reflect the live workspace.
1. Live target
| Field | Live value |
|---|---|
| Most-touched code package this session | None — current session is documentation work |
| Most-likely-to-have-debris package | core2/packages/wbc-ui2-cdn/ (per memory: cache-loader still referenced post-restructure, untested apps may have stale logging) |
| Memory-safe target | core2/packages/wb-core/ (active package, tests in place) |
| Documentation cleanup | frontEnd/wbc-ui/core2/apps/wb-flow/flow.wbc-ui.com/ — but /wbClean is for code, not docs. Refuse. |
| Generated-file zones | dist/, dist-dev/, node_modules/ — always skipped |
The interesting case is the second row: cleanup on wbc-ui2-cdn/ is constrained by the parked tech debt. The agent will clean within-file debris (orphan imports, console.logs) but will NOT remove anything that would interact with the dist-folder mismatch.
2. What each input form would resolve to today
| Input | Live resolution |
|---|---|
/wbClean core2/packages/wb-core/src/ | Full directory pass. Likely small findings. |
/wbClean core2/packages/wbc-ui2-cdn/ | Allowed but cautious: would clean within-file debris while NOT touching anything related to the parked dist mismatch (e.g., would not "clean up" the unused dist/ reference in package.json — that's the parked decision). |
/wbClean frontEnd/wbc-ui/core2/apps/wb-flow/flow.wbc-ui.com/ | Refuse — documentation, not code. |
/wbClean core2/packages/wbc-ui2-cdn/vite.config.js | Cleans within-file debris. The unused cacheLoader import (per memory) would be a finding. |
/wbClean "the WBC stuff" | Refuse — free-text. |
/wbClean core2/ | Permitted but large; would walk all packages. Would refuse to act on parked-package internals beyond surface debris. |
3. Per-input behavior, applied live
| Input shape | Live behavior |
|---|---|
| Single file | Standard cleanup pass. |
| Directory | Walks; reports per-file. |
| Cross-package glob | Same; possibly larger report. |
| Parked-tech-debt package | Memory-aware: cleans within-file debris only. Refuses anything that touches the parked decision surface. |
| Documentation target | Refuse with suggestion to use a different tool. |
4. Pipelines
/wbClean core2/packages/wb-core/src/> /wbClean core2/packages/wb-core/src/💠 Pipeline Cleanup pass on wb-core (the natural target)
💠 Pipeline Memory-aware cleanup of wbc-ui2-cdn
💠 Pipeline Refuse cleanup on docs
💠 Pipeline Orphan file confirmation
A hypothetical wb-core scenario where a .bak file accumulated:
5. What would refuse today
| Trigger | Live response |
|---|---|
/wbClean (no target) | Halt. |
/wbClean "the WBC code" | Halt — free-text. |
/wbClean frontEnd/wbc-ui/core2/packages/wb-flow/templates/ | Refuse — documentation. |
/wbClean core2/packages/wbc-ui2-cdn/package.json (asking to clean the parked-mismatch field) | Refuse — memory says parked. Suggests architectural conversation. |
/wbClean core2/packages/wb-core/tests/ | Skip with notice — test-file cleanup is /wbWork against a test-improvement row. |
/wbClean --profile="aggressive" | Halt — /wbClean has no flags. |
/wbClean directory pass that would auto-revert all changes due to test failure | Auto-revert all edits in the affected files. Reports which file's tests regressed. |
The pattern: /wbClean is debris removal with strong scope discipline. Fixed checklist, no flags, behavior-preserving by definition. Memory-aware enough to skip parked items even when they look like cleanup candidates. Refuses documentation, refuses free-text, refuses to touch tests. The healthy state is "0 findings" — when /wbClean consistently finds debris, the underlying signal is about commit hygiene, not about the command.