Mesteriis Secrets And Config Review
Review configuration without exposing secret values.
Workflow
- Inspect config keys, file metadata, templates, and redacted examples first.
- Avoid reading secret values unless the user explicitly scopes break-glass handling and it is safe.
- Check logs, docs, tests, CI, Docker files, and sample env files for leakage.
- Verify defaults, required variables, permissions, and error behavior.
- Report risks and minimal mitigations.
Output
- config surfaces reviewed
- secret exposure risks
- unsafe defaults
- logging/documentation risks
- remediation
- validation gaps
Rules
- Never print secret values.
- Do not commit or document credentials.
- Prefer key names, metadata, and redacted evidence.