Security Compliance Guard
When to use
- Before push/release to prevent secret or sensitive metadata leaks.
- When onboarding a repo to public Git hosting.
Read order
references/project-profile.md(or template if missing)references/secret-scan-policy.mdreferences/public-repo-safety-checklist.mdreferences/planning-framework-links.md
Workflow
- Run secret/sensitive pattern scan on tracked files.
- Verify local-only config files are ignored.
- Verify public-safe artifacts only are tracked.
- Emit PASS/FAIL/BLOCKED with evidence paths.
Required output
status(PASS|FAIL|BLOCKED)findingsevidencePathsnextAction
Commit rules
- Use the format
<type>: <한국어 요약>for every commit. - Allowed types:
feat,fix,refactor,docs,test,chore,perf,ci,build,revert. - Korean summary is mandatory on the first line.
Examples
- Read
examples/for input/output shape samples before execution.