brew-maintain
Skill1 starsChanged 7 months agoMITView on GitHub
Homebrew 日常维护助手。更新软件包、清理缓存、检查健康状态时使用。
- Deletes or force-pushes
- Installs packages
In this repository14 other files it gives its agents.
- cc-updatesSkill
- commit-helperSkill
- dev-consoleSkill
- explain-codeSkill
- init-modularSkill
- learnSkill
- plan-debateSkill
- port-managerSkill
- product-contextSkill
- projectSkill
- refactorSkill
- techdebtSkill
- ui-specSkill
- web-researcherSkill
The file
Files
Homebrew 日常维护助手
快速命令
完整维护流程(推荐每周执行)
brew update && brew outdated && brew upgrade && brew cleanup && brew doctor单独命令说明
| 命令 | 作用 |
brew update | 更新 Homebrew 自身和所有 formula 定义 |
brew outdated | 列出可升级的软件包 |
brew upgrade | 升级所有过期软件包 |
brew upgrade <pkg> | 升级指定软件包 |
brew cleanup | 清理旧版本和缓存 |
brew doctor | 检查系统健康状态 |
维护步骤
1. 更新 Homebrew
brew update获取最新的软件包定义。
2. 查看可升级软件包
brew outdated列出所有有新版本的软件包。
3. 预览升级(可选)
brew upgrade --dry-run查看将要执行的升级操作,不实际执行。
4. 执行升级
# 升级所有
brew upgrade
# 仅升级命令行工具
brew upgrade --formula
# 仅升级图形应用
brew upgrade --cask
# 强制升级自动更新的 cask
brew upgrade --greedy5. 清理旧版本
# 查看可清理空间
brew cleanup -n
# 执行清理
brew cleanup6. 健康检查
brew doctor检查并修复潜在问题。
版本管理
锁定软件包版本
# 防止某个软件包被升级
brew pin <package>
# 解除锁定
brew unpin <package>
# 查看已锁定的软件包
brew list --pinned查看软件包信息
# 查看软件包详情
brew info <package>
# 查看已安装的软件包
brew list
# 查看软件包依赖
brew deps <package>
# 查看依赖该软件包的其他包
brew uses --installed <package>空间管理
# 查看缓存占用
du -sh $(brew --cache)
# 查看 Cellar 占用
du -sh $(brew --cellar)
# 清理所有缓存(更彻底)
rm -rf $(brew --cache)故障排除
修复权限问题
sudo chown -R $(whoami) $(brew --prefix)/*重置 Homebrew
brew update-reset重新安装软件包
brew reinstall <package>自动更新控制
禁用自动更新
已在 shell 配置中设置:
export HOMEBREW_NO_AUTO_UPDATE=1临时启用自动更新
unset HOMEBREW_NO_AUTO_UPDATE && brew install <package>执行原则
- 先查看再操作:用
brew outdated和--dry-run预览 - 关键软件先锁定:对依赖特定版本的软件使用
brew pin - 定期清理:每次升级后运行
brew cleanup - 检查健康:遇到问题先运行
brew doctor
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

