harden

You can audit Oracle configuration by scanning repositories with CLAUDE.md and a ψ directory to detect security gaps, governance violations, and hardening deficiencies. It checks for tracked secrets, .gitignore issues, and rule compliance.

Yes, scanning for hardening deficiencies requires git access, standard Unix tools, and read permissions on repository files. These permissions are needed to inspect tracked secrets and verify the ψ brain-folder structure.

The security audit scans for tracked secret files and common secret patterns, verifies essential .gitignore patterns, checks compliance with Golden Rules in CLAUDE.md, and audits the ψ brain-folder structure for required identity fields.

Yes, you can automatically fix missing .gitignore rules and non-compliant configurations using the optional auto-fix mode. This mode applies actionable fixes identified during the security and governance audit.

The best way to verify Golden Rules compliance is to run an audit that checks the rules defined in CLAUDE.md against the repository configuration. This detects governance violations and generates a summary report with actionable fixes.