Adaptive Review

This skill appears coherent: it only scans your git diff and routes review work to a smaller or larger reviewer depending on the signals. Before installing or running it, consider these points: - Data exposure: adaptive-review will send diffs to whichever model/endpoint it spawns (haiku/sonnet/opus or any configured local endpoint). If those are remote cloud models, your code (including secrets contained in diffs) will be transmitted to that provider. If your repo contains sensitive data, either use a local/self-hosted endpoint (SKILL-openclaw.md guidance) or avoid running deep reviews against cloud models. - Secret handling: the grep intentionally targets code files and excludes .md/.json/.yaml, which reduces false positives but may miss secrets in config files. If your secrets live in config files, adjust the scan or add pre-checks to mask/remove secrets before review. - Overrides: users can force depths (--fast/--medium/--deep). A fast review may miss architecture/security issues; the skill sensibly recommends upgrading when fast finds potential issues. - Test first: try the skill on a non-sensitive repository to verify how your platform performs subagent/model calls and to confirm which endpoints actually receive the diff payloads. - Endpoint/config hygiene: if you use the OpenClaw/local variant, ensure the endpoints you configure are trustworthy and that any API keys are rotated and scoped appropriately. If you want stricter safety: restrict the skill to local/self-hosted models only, extend the grep to include config files you use for secrets, or add a preflight that blocks reviews when known secret patterns are present.