HIG Doctor audit

Use HIG Doctor findings as review evidence, not certification.

Audit workflow

1. Confirm the target repository or directory. Keep the scan within that scope.
2. Run npx -y hig-doctor@2.0.3 <target> --json for machine-readable findings.
3. Report the detected frameworks, severity counts, rule IDs, locations, and material analysis limits.
4. Use hig_explain_finding or the relevant bundled HIG skill when a finding needs its cited guidance and context.
5. Before editing, distinguish mechanical fixes from changes that require product, design, accessibility, or platform judgment.
6. If the user authorized remediation, preserve justified suppressions and rerun the audit plus the repository's relevant checks.

Gates and baselines