mac-audit

Audit macOS development environments for drift, security issues, and cleanup readiness.

3|1|Updated Feb 12, 2026

Search Tags:#security #audit #reporting #macos #drift #dev-environment #brew

Ready to run

npx skills add https://github.com/edfenton/claude-skills --skill mac-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mac-audit
Source: https://github.com/edfenton/claude-skills/tree/main/shared/mac-audit
Command: npx skills add https://github.com/edfenton/claude-skills --skill mac-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit macOS development environments for drift, security issues, and cleanup readiness to keep projects reproducible and compliant.

Core Features & Use Cases

Detect brew drift, orphaned packages, and version mismatches
Produce a concise, markdown-formatted health report with PASS/WARN/FAIL indicators
Quick-start guidance for quarterly audits or after major environment changes

Quick Start

Run the mac-audit tool to generate a quarterly health report for your macOS development environment.

Frequently Asked Questions about mac-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I audit my macOS development environment for drift and security issues?▼

Use a script-driven macOS audit workflow to detect brew drift, orphaned packages, and version mismatches. It executes inline Bash commands to evaluate your toolchain and outputs a concise, markdown-formatted health report with PASS/WARN/FAIL indicators.

What is brew drift and how do I detect orphaned packages on macOS?▼

Brew drift occurs when installed Homebrew packages diverge from a baseline. Detect orphaned packages and version mismatches by running a macOS environment audit that references your BREWFILE to check configuration consistency and compliance.

When should I run a macOS toolchain audit for my development team?▼

Run a macOS toolchain audit quarterly or after major environment updates to maintain project reproducibility and compliance. Regular checks prevent accumulated drift and ensure team development environments stay aligned.

Does the macOS environment audit require a BREWFILE or AUDIT.md configuration?▼

Yes, the macOS audit workflow references a BREWFILE for package baseline configuration and an AUDIT.md file for audit settings. These files guide the script-driven checks and define the expected development environment state.

What is the best way to generate a health report for my macOS dev environment?▼

Generate a macOS health report by running a script-driven audit that outputs a markdown-formatted summary with PASS, WARN, and FAIL indicators. This approach evaluates drift, security, and cleanup readiness in a single self-contained workflow.

What are the limitations of using inline Bash commands for macOS environment audits?▼

Using inline Bash commands for macOS audits limits the workflow to environments where Bash is available and properly configured. The audit scope is also constrained to script-detectable drift and security issues, relying on BREWFILE and AUDIT.md configuration accuracy.