macos-scripts ⚡

Turn scattered shell commands into structured workflows.

👉 View case study: mcamner.github.io/macos-scripts/case.html

Stop memorizing commands. Start running workflows.

---

🚀 Quick start

Option 1 — Install (recommended)

curl -fsSL \
  https://raw.githubusercontent.com/MCamner/macos-scripts/main/install.sh \
  | bash

Option 2 — Clone

git clone https://github.com/MCamner/macos-scripts.git
cd macos-scripts
./install.sh

---

⚡ First run

mqlaunch doctor

This will:

• verify your environment
• check required dependencies
• validate your setup
• highlight issues with clear fixes

---

🚦 Then explore

mqlaunch

• browse workflows via the interactive menu
• or run commands directly (perf, system, dev, tools)

---

⚡ One command instead of many

Instead of:

top
df -h
ps aux | sort -nrk 3 | head
./tools/scripts/system-check.sh

Run:

mqlaunch perf

---

🎯 What this solves

Most environments don't lack tools — they lack structure.

This project turns:

useful chaos → usable system

---

🧠 Core idea

One command → structured workflows → repeatable execution

• single entrypoint: mqlaunch
• organized workflows (Dev, System, Performance, Git, Release, Tools)
• works as interactive menu and direct CLI
• built-in AI for questions, code generation, and error fixes

---

🧰 Common commands

mqlaunch                         # interactive menu
mqlaunch perf                    # performance overview
mqlaunch system check            # system health
mqlaunch dev                     # dev workflows
mqlaunch git                     # git menu
mqlaunch release                 # release menu
mqlaunch ask "your question"     # AI repo assistant
mqlaunch fix "error or task"     # AI generates copy-paste shell commands
mqlaunch atlas                   # AI REPL session
mqlaunch doctor                  # environment check
mqlaunch selftest                # smoke tests + shell lint
mqlaunch demo                    # guided demo

---

🤖 AI assistant

Ask questions about the repo directly in the terminal:

mqlaunch ask "how does command routing work?"
mqlaunch ask "what does doctor.sh check?"

Start an interactive session with Atlas — a senior systems engineer embedded in mqlaunch:

mqlaunch atlas

atlas> why is my push being blocked?
atlas> explain the release flow
atlas> exit

Atlas answers inline without opening a browser.

---

🔧 Fix and generate code

Get copy-paste ready shell commands for errors and tasks:

mqlaunch fix "ERROR: CHANGELOG does not contain version 0.1.9"
mqlaunch fix "write a function that checks if a port is in use"
mqlaunch fix "add option 13 'View stash' to the git menu"

Output is always runnable — cat heredocs, sed, mkdir — no theory:

# Add changelog section for 0.1.9
cat >> CHANGELOG.md << 'EOF'
## [0.1.9] - 2026-05-07
### Changed
* ...
EOF

Copy, paste, run. Uses repo context from the vector store.

---

🚢 Release workflow

Auto Release handles the full release cycle in one flow:

mqlaunch release
# → select option 11: Auto Release

Steps:

1. Auto-generate changelog section from commits since last tag
2. Dry run — validates VERSION, README badge, and CHANGELOG
3. Live release — bumps version, tags, updates files
4. Git push + push tags
5. Create GitHub release

Run the release check before every push:

mqlaunch release-check

---

🏷️ Nickname

Set a name that appears in every menu header:

mqlaunch nickname-set "your name"

Stored in ~/.mqlaunch_nickname.

---

🔎 Performance scan

mq scan

Ranks CPU and memory offenders, highlights repeat offenders, and gives practical recommendations for what to close or restart.

---

🩺 Health check

mqlaunch doctor

• checks required tools (git, brew, node, python, jq)
• validates repo state (branch, dirty tree, required files)
• evaluates workflow readiness (Git, Release, Dev, System)
• highlights issues and gives actionable recommendations

---

🧪 Selftest

mqlaunch selftest

Runs launcher smoke checks, v1 compatibility checks, and shell lint for supported bash/sh scripts.

---

🎬 Demo

mqlaunch demo

---

🖼️ Screenshots

Main Menu

Performance Menu

Release Flow

---

🧱 Project structure

macos-scripts/
├── bin/               # CLI entrypoints
├── terminal/          # menus, launchers, themes, AI prompts
├── tools/             # scripts and utilities
├── system/            # macOS helpers
├── automation/        # workflows
└── ui/                # terminal UI

---

⚖️ Design principles

• keep it simple
• structure > more tools
• optimize for real usage
• make workflows repeatable
• reduce cognitive load

---

🎬 Case Study

See how macos-scripts is designed as a structured CLI system:

👉 mcamner.github.io/macos-scripts/case.html

---

📈 Real use case

Instead of remembering 5–10 system commands during troubleshooting:

mqlaunch system check

→ full system overview in one step

---

🔭 Roadmap

• workflow validation / health checks
• plugin-style extensions
• remote execution support
• improved onboarding

---

🤝 Contributing

PRs welcome. If you have ideas for workflows or improvements — open an issue.

---

📄 License

MIT