OpenParable
Skip to content
← Back to skills

Macprof

Testing & Quality
macprof

Macprof is an Agent Skill for testing & quality published in the Mic92/dotfiles repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Profile macOS processes (CPU hot spots, hangs, "what is X doing?"). Wraps sample/spindump/xctrace and prints a compact text summary or speedscope/flamegraph data.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Mic92/dotfiles/blob/HEAD/pkgs/macprof/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/macprof, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Default invocation prints a bounded text summary to stdout — paste it back.

# What is process X doing? (one process, wall-clock, 5s)
macprof sample <pid|name> 5 -o -

# Where is CPU time going system-wide? (true on-CPU, needs Xcode CL tools)
macprof xctrace 5 -o -
macprof xctrace 5 --attach <pid|name> -o -

# What is everything blocked on? (wall-clock, all procs, needs sudo)
macprof spindump 5 -o - --keep-idle

# Files for the user to open interactively
macprof xctrace 10 -o cpu.speedscope.json   # → drop on https://speedscope.app
macprof spindump 10                          # → cwd: .folded + .speedscope.json

Pick sampler by question:

questioncommand
process hung / spinning, why?sample <name>
what's burning CPU right now?xctrace
system slow, who's blocking whom?spindump

Flags: -o - stdout summary · -o x.json speedscope · -o x.folded flamegraph · --keep-idle include blocked threads · --keep-raw keep raw report.

Pair with heap <pid> (object counts) and lsof -p <pid> (open files/dirs) when memory, not CPU, is the symptom.