Bonsai

Hygiene

• Commented-out code that should be removed or restored
• File ordering per project conventions
• TODO/FIXME/HACK comments
• Unnecessary blank lines or inconsistent formatting

Pruning

• Dead or broken symlinks (use find -xtype l to detect)
• Package lists: detect duplicates or entries no longer needed
• Scripts that duplicate existing tools or each other
• Unused aliases, functions, or config blocks
• Version manager tools no longer used

Upgrades

• Config format changes from tool updates (breaking changes in new versions)
• Package lists: renamed or deprecated packages
• Tool versions: flag significantly outdated entries

Output Format

Report findings as a numbered list. Each item must include:

1. File — path relative to repository root
2. Finding — what was found and why it matters
3. Proposed change — the specific edit, or "remove" / "no action needed"

Guidelines

• Read every file individually. Bulk reading causes misreads.
• Read before suggesting. Never propose changes to files you have not read.
• Scope changes narrowly. A bonsai session should produce a small, reviewable diff.
• Explain the "why" for each change, not just the "what".