macverify-reviewlisted
Install: claude install-skill ShanedixonGit/macverify
# macverify review
Run the read-only macOS audit, read the result, and turn it into a short ordered
list of fixes the user can actually act on. The audit changes nothing; you
propose, the user decides.
## What macverify is
A read-only inventory of a Mac. It never writes, never elevates (`sudo`, `su`,
`security` and `systemsetup` are refused by its own command runner), and never
opens a network connection. It reads sixteen domains: `toolchain`, `packages`,
`shell_env`, `hardware`, `storage`, `services`, `containers`, `network`,
`security`, `identity`, `secrets`, `permissions`, and the AI-assistant family
`claude_code`, `github_copilot`, `openai_codex`, `ai_assistants`.
It reads configuration, not file contents. **It cannot detect malware** - no
signatures, no hashes, no reputation lookups. Say so when you summarise, and
recommend a real scan alongside it (see "Always say this" below).
## Step 1 - locate or produce a report
If `macverify` is on `PATH`, run it from anywhere. If the user has a clone
instead, run `python3 -m macverify` from inside it.
```sh
macverify --quick-fixes --no-prompt
```
Reports land in `~/.macverify/reports/`, owner-only. A run takes 30-60 seconds.
`--no-prompt` matters here: run from a terminal without it, macverify asks where
to save and waits for an answer, which would stall an unattended run and could
put the reports somewhere other than the path below.
If a recent report already exists (`ls -t ~/.macverify/reports/audit_*.json | head -1`,
c