macos cleaner

Other Community

Skill notes

Entry router

Choose the narrowest path that can answer the request: User signal · Route Apple Content Caching, AssetCacheManagerUtil, CacheUsed, ActualCacheUsed, iCloud cache, or “Caching needs more space” · Read references/apple_content_caching.md completely before probing or proposing commands Docker, OrbStack, images, containers, or volumes · Read references/docker_analysis.md; inspect every object and never use prune-family commands

Safety and authorization contract

Separate observation from mutation. Complete a read-only diagnosis first. Do not delete, stop a service, edit settings, install or upgrade tools, or run a cleanup preview that may mutate state during that phase. Confirm the exact target. On a remote Mac, record the current host identity before any other work. Never infer the machine from an IP, old PID, directory name, or prior report. Plan before asking. Before any state change, list every command, what it changes, expected physical space reclaimed, impact, recoverability, and postconditions. Then stop if the user requested a plan-only phase.

Phase contract

Use this state machine for every cleanup: Observe — read-only. Capture identity, disk baseline, the suspected subsystem's status and configuration, physical allocation, and critical-service health. 1b. Authorize stateful inspection when unavoidable. If deeper evidence requires creating a temporary container, pulling an image, mounting a volume, or writing a snapshot, first finish the metadata-only observation, list the exact inspection commands and their side effects, and obtain separate approval. Inspection approval is not cleanup approval.

Establish the baseline

At minimum, capture: Use df -k for calculations and df -h for the human-readable report. Treat an extension, label, or old report as a hint until the live command confirms it. Establish the success target before an unknown-source scan. Copy a user-supplied free-space or capacity target exactly. If the user supplied none, report the current values and ask for a target in GiB, capacity percentage, or both; do not invent one. A named-suspect diagnosis may continue without a cleanup target, but the ordered unknown-source scan cannot claim a stop condition until the target is explicit.

Follow the named suspect before broad scans

Query the subsystem's own status and settings. Measure physical allocation with a bounded du on the exact data path only when permissions and user scope allow it. Distinguish logical content size, sparse-file apparent size, purgeable space, and physically allocated bytes. For a suspected growing log, record exact file sizes at two or more timestamps. One large file or one recent mtime does not prove sustained growth.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@daymade · no license declared
Token usage
Moderate
Setup complexity
Manual integration
External API key
Not required
Operating systems
macOS · Linux · Windows · Docker
Runtime requirements
Docker
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: read-only diagnosis

Phase 1: read-only diagnosis

02
Phase 2: report and stop at the gate

Report observed values rather than inferred properties. Use `references/report_templates.md` for the long-form layout and include these fields for every proposed action: Field · Required content Current state · Timestamp, target identity, disk used/free/capacity, and subsystem status Evidence · The command and observed value; state whether the number is logical or physical Exact command · The command that would change state, with the exact target or object ID

03
Phase 3: execute the confirmed plan

Immediately before the first state-changing command: Reconfirm the target identity and current disk state. Re-query the objects or subsystem status; cleanup plans expire when live state changes. Recheck protected-service health. Compare the approved commands with the commands about to run. Any difference requires new approval.

04
Phase 4: verify and observe

Verification must cover all clauses of the approved plan: Re-read `df -k` and `df -h`; calculate reclaimed space from before/after readings rather than from the deletion tool's claim. Re-query the cleaned subsystem's activation, configuration, and physical usage. Re-resolve each protected service's PID, listeners, launch mechanism, and health probe. A healthy disk does not prove the service survived.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.