Compliance & Security Auditor
This skill performs automated compliance audits on codebases using CLI tools (rg, find) to comprehensively scan for security, privacy, and architectural patterns.
Step-by-Step Guidance
- Determine the Audit Scope: Ask the user which framework(s) they want to audit against:
- LAUSD (California K-12)
- NJDPL (New Jersey K-12)
- AICPA SOC 2 (Common Criteria)
- Combined (All applicable frameworks simultaneously)
- Review Technical Signals: Read
./technical-signals.mdfor the exactrgcommands and code heuristics needed to identify passing/failing code across all frameworks. - Execute the Audit(s):
- For LAUSD: Read
./lausd-audit-instructions.mdand./lausd-security-manual.md - For NJDPL: Read
./nj-audit-instructions.md - For SOC 2: Read
./soc2-audit-instructions.md - For Combined: Execute all selected instruction sets sequentially.
- For LAUSD: Read
- Generate the Report: Generate the final output using the corresponding markdown template from the
./templates/directory. If performing a Combined Audit, use./templates/combined-audit-report.md.
General Audit Principles
- Use CLI Tools Heavily: Rely on
rgandfindrather than reading files line-by-line. - Be Highly Specific: Always quote the exact file name, line of code, and the specific policy/framework requirement it violates.